Return Home
Overview
<attach>
<body>
<body>
<clientip>
<comment>
<configuration>
<copy>
<delay>
<dnslookup>
<domainquery>
<email>
<expression>
<expressions>
<file>
<filter>
<filters>
<header>
<header>
<helo>
<http>
<imap>
<index>
<inputpath>
<ipquery>
<log>
<mailfrom>
<maxbuffer>
<maxlines>
<message>
<modifysource>
<multiplerecipients>
<option>
<parser>
<path>
<quickresult>
<rcptto>
<result>
<results>
<return>
<rule>
<rules>
<scope>
<select>
<smtpextendedstatuscode>
<smtpstatuscode>
<target_filter>
<target_index>
<test>
<title>
Boolean type
Macros
Regular Expressions
Node: ipquery
<ipquery enabled="yes" query="{ip_d}.{ip_c}.{ip_b}.{ip_a}.multi.surbl.org"
onlookup="[script]" />
Performs a DNS lookup using the specified
query. The result (the D component of the returned IP address) is made available
in the variable "query_result". The script provided in the onlookup attribute is
executed when the query returns a result.
All IP addresses found in the email parts specified using the <scope> attribute are tested.
Attributes:
enabled
yes
no
query
Specify the DNS query using these available macros:
{ip} full IP address (a.b.c.d)
{ip_a} 1st component of IP address
{ip_b} 2nd component of IP address
{ip_c} 3rd component of IP address
{ip_d} 4th component of IP address
onlookup
[script]
Notes
Only queries returning an IP address are supported. If the query returns a host name, it will be processed as if it failed to return anything.
Be aware when using RBL's identifying dynamic/dialup IP addresses that you should not include the header within the scope being tested since it will contain IP addresses for the entire path the email took, including the sending users IP address, which most likely would be a dynamic/dialup IP address.
Revision History:
- Requires v2.3.7 or higher