The address:port of your message handling system's smtp server(s). Secondary servers possible, will try the next if the first doesn't respond.
If only the port is entered, or the keyword __INBOUND__:port is used, then the connection will be established to the same IP where the connection was received. This is usefull when you have several IPs with different domains/profiles in your MTA.
Examples: "127.0.0.1:125", "127.0.0.1:125|127.0.0.5:125", "10.0.1.3", "10.0.1.3:1025", "__INBOUND__:125", "125", etc.

On what port should ASSP accept smtp connections? Normally 25. You can supply an interface:port to limit connections.

Listen for incoming SMTP requests on a second port. For those who cannot use SMTP Port 25 outside of their ISP Network, or as a dedicated port for VPN purposes. You can supply an interface:port to limit connections. For example: 2525 or 127.0.0.2:325

Port to connect to when connections arrive on the second Listen Port. If blank all incoming mail will go to the main SMTP Destination, the main use is to allow remote / travelling users to make authenticated connections, and therefore inject their mail at the SPF-correct point in the network. eg 127.0.0.1:587

Handle AUTH before MAIL From on the submit port for MTAs which fail to enforce the requirement. Requires "Another Listen Port" and "SMTP Auth Destination". Otherwise does nothing.

Port to connect to when >Email Interface< mails are send. If blank all internal mail will go to the main SMTP Destination. eg "10.0.1.3:1025", "1025", etc.

If the smtp destination sends $MaxErrors 501s, 502s, 503s... the connection is dropped.

The maximum number of SMTP sessions (connections) to handle concurrently.
This can help if the server is overloading. 32 simultaneous connections is typically enough. no entry or zero = no limit.

The maximum number of SMTP sessions (connections) to handle per IP address concurrently. Limit this to prevent DOS attacks, 5 simultaneous connections is typically enough. no entry or zero = no limit. Also note that the ISP & accept all mail addresses are excluded from limiting.

The maximum number of SMTP connections to handle per IP in a timeframe. Limit this to prevent DOS attacks, 5 connections is typically enough. No entry or zero = no limit. Also note that the ISP & accept all mail addresses are excluded from limiting.

If the connection counter per IP reach the maximum in this timeframe the IP will be denied connection. 60 seconds is default.

The connection counter will be reset after this time. 3600 seconds is default. If you prefer to let the PenaltyBox handle this, set expiration to same value as duration.

The maximum time the connection will be allowed to be idle.
120 seconds is default. No entry or zero = no limit.

---

If an incoming email that's not local or whitelisted matches this Perl regular expression it will be considered spam by the Bayesian filter.
May match text from the body or header of the email. For example: penis|virgin|X-Priority: 1

If an email matches this Perl regular expression it will be considered redlisted. The redlist is a list of addresses that cannot contribute to the whitelist, and who are not considered local, even if their mail is from a local computer. For example, if someone goes on a vacation and turns on their email's autoresponder, put them on the redlist until they return. Then as they reply to every spam they receive they won't corrupt your non-spam collection or whitelist: \[autoreply\]
Redlisted adresses will not be added to the whitelist. Redlisted messages will not be stored in the SPAM/NOTSPAM-collection.As usual (marked by *) this field accepts a list separated by | or a specified file 'file:files/redre.txt' .

SMTP error message to reject spam. For example:554 5.7.1 Mail appears to be unsolicited -- send error reports to postmaster@yourdomain.com

Mail to any of these users at are always spam and will contribute to the spam-collection unless from someone on the whitelist;
@domain.com makes the whole domain a spam domain. A username without domain will register across all local domains.

ASSP will try to deliver mails to all Collect Addresses to this address.
For example: collect@mydomain.com

Indivudal Adresses & Domains from which you always want to reject mail, they only send you spam. Note this matches the end of the address, so if you don't want to match subdomains then include the @. Note that buy.com would also match spambuy.com but .buy.com won't match buy.com. abc@def.com will match abc@def.com but won't match bbc@def.com.For example: @spam.net|.pics.com|seller@bayer.com

Put anything here to identify messages which should only be checked for content. For example: mailaddresses of people who are forwarding from other accounts to their mailbox on your server. These addresses will bypass PB, Sender Validation, Griplist, IP Limiting, Delaying, SPF, RBL & SRS checks.

Check this to disable the Griplist upload when rebuildspamdb runs. The Griplist contains IPs and their value between 0 and 1, lower is less spammy, higher is more spammy. This value is called the grip value.

Set this checkbox if don't use the Griplist or want to download it manually.

Adds a line to the email header "X-Assp-Spam-Prob: 0.0123" Probs range from 0 to +1 where > 0.6 = spam.

Adds a line to the email header "X-Assp-Intended-For: user@domain" .

Check this box if you don't want your X-Assp-Spam-Prob header on external mail
Note this means mail from local users to local users will also be missing the header.

Adds a line to the email header "X-Assp-Spam: YES" if the message is spam.

Adds a line to the email header e.g. "X-SMSMSE-SCL: 9" if the message is spam.

Adds a line to the email header "X-Assp-Spam-Reason: " explaining why the message is spam.
 

---

ASSP will try to deliver mails adressed to all postmasters of your local domains to this address.
For example: postmaster@mydomain.com

ASSP will try to deliver mails to all abuse adresses of your local domains to this address.
For example: abuse@mydomain.com

Port to connect to when CCallSpam/Ham< mails are send. If blank all mails will go to the main SMTP Destination. eg "10.0.1.3:1025", "1025", etc.

If set spamSubject gets prepended to the subject of the CC-email.
 

The check which caused the spam detection will be prepended to the subject of the email. For example: [RBL]

ASSP will try to deliver a copy of all spam email to this address.
For example: spammaster@mydomain.com

If set CC-all-Spam will work for selected recipients only .
Accepts specific addresses (user@domain.com), user parts (user) or entire local domains (@domain.com).

Restricts CC all Spam to these recipients. Accepts specific addresses (user@domain.com), user parts (user) or entire local domains (@domain.com).
 

CC all Spam to these recipients regardless of collection mode. Mode 6 (discard) is ignored. Accepts specific addresses (user@domain.com), user parts (user) or entire local domains (@domain.com).
 

If you put an email address in this box ASSP will try to forward a copy of all notspam email for selected recipients to this address. The literal USERNAME is replaced by the user part of the recipient, the literal DOMAIN is replaced by the domain part of the recipient. For example: archiv@mydomain.com, USERNAME@mybackup.domain, catchallforthis@DOMAIN

 

CC HAM to these recipients. Accepts specific addresses (user@domain.com), user parts (user) or entire local domains #(@domain.com).

---

Spamlover addresses have messages processed by ASSP but they are not blocked. Spam addressed entirely to spam lovers is not blocked. Mail addressed to both spam lovers and non spam lovers IS blocked. Accepts specific addresses (user@domain.com), addresses at local domains (user), or entire local domains (@domain.com). Separate entries with pipes: |. Default: postmaster|abuse.
For example: jhanna@thisdomain.com|fhanna|@sillyguys.org

 

 

 

This includes Valid/Invalid Helo

 

 

 

 

 

 

 

 

 

If set spamSubject gets NOT prepended to the subject of the Spam-Lover-email.
 

---

Mail solely to or from any of these addresses are ignored by ASSP.
Like a more efficient version of spamLovers & redlist combined. Valid entry types are as per spamlovers: full address, username only, or entire @domain.

Mail from any of these IPs are ignored by ASSP.
For example: 127.0.0.1|10.|169.254.|172.16.|192.168. As usual (marked by *) this field accepts a list separated by | or a specified 'file:files/ipnp.txt' .

If an email header matches this Perl regular expression it will pass through unprocessed. For example: 169\.254\.122\.|172\.16\.|\[autoreply\].

Incoming messages larger than this SIZE (in bytes) are ignored by ASSP. Empty or 0 disables the feature (not recommended). Default is: 200000.

Mail solely to or from any of these addresses will be processed by ASSP. All others will be ignored by ASSP. Valid entry types are as per spamlovers: full address, username only, or entire @domain.
Note that if an address matches both the No Processing and the Process Only lists, the No Processing rules take precedence.

 

---

If an incoming email matches this Perl regular expression it will be considered whitelisted.
For example: Secret Ham Password|307\D{0,3}730\D{0,3}4[12]\d\d
For help writing regular expressions click here. Note that flags are "si" and the header as well as body is scanned.
Some things you might include here are your office phone number or street address, spam rarely includes these details. As usual (marked by *) this field accepts a list separated by | or a filename specified this way: 'file:files/whitere.txt' .

They contribute to the whitelist and to notspam. For example: 127.0.0.1|10.|169.254.|172.16.|192.168.

Domains from which you want to receive all mail. Your ISP, domain registration, mail list servers, stock broker, or other key business partners might be good candidates. Note this matches the end of the address, so if you don't want to match subdomains then include the @. Note that buy.com would also match spambuy.com but .buy.com won't match buy.com. DO NOT put your local domains on this list. For example: sourceforge.net|@google.com|.buy.com

RWL: Real-time white list. These are lists of IP addresses that have somehow been verified to be from a known good host. Senders that pass RWL validation will pass IP-based filters. This requires an installed Net::DNS module in PERL.

Domain Names of RWLs to use separated by "|". Defaults are...
query.bondedsender.org|exemptions.ahbl.org|iadb.isipp.com|hul.habeas.com

A reply is affirmative or negative reply from a RWL. The RWL module will wait for this number of replies (negative or positive) from the RWLs listed under Service Provider for up to the Maximum Time below. This number should be equal to or less than the number of RWL Service Providers listed to allow for randomly unavailable RWLs

A hit is an affirmative response from a RWL. The RWL module will check all of the RWLs listed under Service Provider, and flag the email with a RWL pass flag if equal to or more than this number of RWLs return a postive whitelisted response. This number should be less than or equal to Maximum Replies above and greater than 0

This sets the maximum time to spend on each message performing RWL checks

Add X-Assp-Received-RWL header to header of all emails processed by RWL.

Enter IP addresses that you don't want to be RWL validated, separated by pipes (|). For example: 127.0.0.1|192.168.

This is the number of days an address will be kept on the whitelist without any email to/from this address.

Check this if you don't want Bayesian filtering and want to reject all mail from anyone not whitelisted.
 

Check this if you're using Whitelist-Only and don't care to save mail to build the Bayesian database.

Normal operation includes addresses in the FROM, SENDER, REPLY-TO, ERRORS-TO, or LIST-* header fields.
This allows nearly all list email to be whitelisted. Check this option to disable this.

Normal operation allows all local, authenticated, or whitelisted users to add to the whitelist.
Check this box to not allow whitelisted users to add to the whitelist.

Check this box to prevent *sender* with remote domain from being added to the whitelisted. (eg. redirected messages).

Save a copy of the white list every this many seconds.
Note: the current timeout must expire before the new setting is loaded, or you can restart.
 

---

Check local domains against an LDAP database.
Note: Checking this requires filling in LDAP DomainFilter in The LDAP section.
This requires an installed NET::LDAP module in PERL.

Check local domains against this adresses. Separate addresses with |. Include all subdomains.
For example: put.YourDomains.com|here.org

Enter any addresses that are your ISP or backup MX servers, separated by pipes (|).
These addresses will (necessarily) bypass Griplist, IP Limiting, Delaying, Penalty Box, SPF, RBL & SRS checks. For example: 127.0.0.1|10. You can use here the same file which is used for delay-exceptions: 'file:nodelay.txt'

It is recommended that for ISP & Secondary MX servers to bypass their Griplist values
For eg. 0.5 (Completely GReyIP). If left blank then the Griplist "X" value is used.
Note: value should be greater than 0 and less than 1, where 0 = never spam & 1 = always spam

Relaying is allowed for these IPs. They contribute also to the whitelist.
For example: 127.0.0.1|10.|169.254.|172.16.|192.168.

Like Accept All Mail, but this is a file that contains a list of ip addresses (one per line) for whom you want to relay mail.
This is an ABSOLUTE path, not relative to base. For example: /usr/local/assp/relayhosts

Do not check relaying based on localDomains. Let the mailserver do it.

Envelope sender addresses treated as bounce origins. Null sender (<>) is always included.
Accepts specific addresses (postmaster@domain.com), usernames (mailer-daemon), or entire domains (@bounces.domain.com)
Separate entries with pipes: |. For example: postmaster|mailer-daemon

Enter the DB database filename of your POP before SMTP implementation with records stored for dotted-quad IP addresses
For example: /etc/mail/popip.db If it's got something else, you'll need to edit the PopB4SMTP subroutine.

If set Merak 7.5.2 is supported.

Your isp's mail relayhost (smarthost). For example: mail.isp.com:25
If you run Exchange/Notes and you want assp to update the nonspam database and the whitelist, then enter your isp's smtp relay host here. Blank means no relayhost. Only required if clients don't deliver through SMTP, or when SRS is enabled.

Tell your mail server to connect to this port as its smarthost / relayhost. For example: 225
Note that you'll want to keep the relayPort protected from external access by your firewall.
You can supply an interface:port to limit connections.

SMTP error message to deny relaying.

If you want to be able to send mail to local users without a domain name then put the default local domain here.
Blank disables this feature. For example: mydomain.com
 

---

Like Local Domains, but OBSOLET! Please use ->localDomains.

If activated, each local address is checked to conform with the email format defined in RFC 822.
This requires an installed Email::Valid module in PERL.

If set IPs from "Accept all Mail" will be tested for valid local adresses.

Check local addresses against an LDAP database before accepting the message.
Note: Checking this requires filling in the other LDAP parameters below.
This requires an installed NET::LDAP module in PERL.

These email addresses are the list of your local adresses. You can list specific addresses (user@mydomain.com),
addresses at any local domain (user), or entire local domains (@mydomain.com). Separate entries with pipes: |.
For example: jhanna@thisdomain.com|fhanna|@sillyguys.org or place them in a plain ASCII file one address per line.

Consider Remote Sender with Valid Local Addresses as NOT spoofed. This will not allow relaying, but will skip delaying. Bayesian will not block but mark only.

These local addresses accept mail only from local domains.

RFC 3598 describes subaddressing with a Separation Character. Everything between Separation Character and @ is ignored (including Separation Character). For example: user@domain.com will allow user+subadress@domain.com. For Example = '+'

SMTP reply for invalid Users. Default: '550 5.1.1 User unknown: EMAILADDRESS'
The literal EMAILADDRESS (case sensitive) is replaced by the fully qualified SMTP recipient (e.g. thisuser@yourcompany.com).
 

---

   [DELUXE]
The Penalty Box blocks mail based on the IP and the history of this IP. The history is written to a Black Box by scoring events like "is PenaltyTrap Address". The scoring values can be set below. If the score per specified time interval surpasses the threshold the mail is rejected (and the IP is marked for blocking). These IPs continue to get score values up to the Extreme Threshold. After that the IP is denied the connection in a very early stage. The White Box stores IPs which should not be put into the Black Box. The White Box is always activated and works in a similar way for IPs as the Whitelist works for addresses. Is an address in the whitelist or whitedomain, the IP goes into the White Box.
Entries in Don't do penalties for these IPs or ISP/Secondary MX Servers will prevent from penalties. You may run it for some time with option 2 to fill White Box and Black Box.
0 = deactivate, 1 = activate, 2 = no blocking - scoring and logging only

If this option is selected, the PB scores for all checks in one message are combined to determine if the email should be considered as Spam. This allows you to assign different weights to individual checks so that not one check will automatically cause an incoming email to be considered as spam, but rather the combination of any failed checks. The checks must be set to modus 3 (score only). If the combined score is greater than Threshold Combined Scores per Message, the mail will be blocked.

  [DELUXE] [CUSTOM]
PB will block messages whose score exceeds this threshold during the message. For example: 50

Enter IP addresses that you don't want to be penalized. You can use here the same file which is used for delay-exceptions: 'file:nodelay.txt'

Adds a line to the email header "X-Assp-PB-Score: " showing the score.

The directory/file with the penaltybox database files. You can delete entries, but do not add entries. Use Whitelisted IPs for whitelisting of IPs and Deny SMTP Connections From these IPs for blacklisting

Mail to any of these users will be rejected by Penalty Box. Whitelist will be ignored. Nothing will be stored in the Spam Collection.
@domain.com makes the whole domain a spam domain. A username without domain will register across all local domains.

ASSP will try to deliver mails to all Trap Addresses to this address.
For example: trap@mydomain.com

Perform the IP address checks of the sending host based on the /24 subnet rather than on the specific IP.

If set SMTP reply for Penalty Deny. eg: '554 5.7.1 Error, send your mail to helpdesk@yourdomain.com to ensure delivery'.

IP's will be rejected if their score exceeds the threshold during this interval (minutes).

PB will block IPs whose score exceeds this threshold during the Penalty Interval.

Successful ASSP checks will increase the internal score per IP. If you set the score higher, the threshold will be reached earlier. For example: 50

Penalties will expire after this number of minutes. If set to Zero the Penalty DB (black) will be deleted and start from scratch.

If set PB will deny SMTP-connections from IPs whose score meet or exceed this level. For example: 150

Enable Denying for whitelisted addresses.

Enable Denying for addresses on the noProcessing list.

Extreme Penalties will expire after this number of days. For example: 7

The White Box is always activated. The White Box works in a similar way for IPs as the Whitelist works for addresses - but it is not a whitelist: Bayesian check will be done. WhiteBox Entries will expire after this number of days. For example: 30

IP's in Black Box which surpassed the extreme level will be regularly stored to this file - if defined. It can be used, to fill savely the denysmtpfile over time. For example: file:pb/exportextreme.txt

Manually maintained list of IPs which should be denied access.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

---

Use the list of blacklisted-helo hosts built by rebuildspamdb.
You probably want to set the HELO blacklist usage to >log only< in the initial training phase for ASSP.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

Block remote servers that claim to come from our Local Domain/Local Host.
0 = deactivate, 1 = activate, 2 = log only, 3 = do nothing but add to the penalty box score (and add scoring-header)..

Include all IP addresses and hostnames for your machine here, separated with |. For example: 11.22.33.44|mx.YourDomains.com|here.org

Disable "Block Forged Helo's" for whitelisted addresses. That check is considered a sure bet, but you may decide here to let whitelisted addresses pass.

Disable "Block Forged Helo's" for addresses on the noProcessing list. That check is considered a sure bet, but you may decide here to let NP-listed addresses pass.

HELO / EHLO greetings on this list will be excluded from the HELO checks. For example: host123.isp.com|host456.isp.com

If activated, the HELO is checked against the expression below. If the Regular Expression matches, the HELO is validated as being ok. Meaning it *wont* be blocked.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

Validate Format HELO will check incoming HELOs according to rfc1123.
For example: ^(([a-z\d][a-z\d\-]*)?[a-z\d]\.)+[a-z]{2,6}$

If activated, the HELO is checked against the expression below. If the Regular Expression matches, the HELO is invalidated as being bad. Meaning it *will* be blocked.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

Invalidate Format HELO will check incoming HELOs for this.
For example: ^\d+\.\d+\.\d+\.\d+$|^[^\.]+\.?$,
You may try a sharper one:
\d+\.\d+\.\d+\.\d+$|^[^\.]+\.?$|\d{1,3}(\.|-|x)\d{1,3}(\.|-|x)\d{1,3}|dynamic|ddns|dns\.org$

[DELUXE]
If activated, each remote sender address with a local domain is checked against the Local Addresses File and/or LDAP.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

If activated, each remote sender address with a local domain is blocked.

  [DELUXE]
If activated, each sender IP is checked for a PTR record. This requires an installed Net::DNS module in PERL.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

  [DELUXE]
If activated - and Reversed Lookup is activated and found a record -, the PTR-FQDN record is checked against the Regex. This requires an installed Net::DNS module in PERL.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

Validate Format PTR will check PTR records for this.
For example: ^\d+\.\d+\.\d+\.\d+$|^[^\.]+\.?$ or file:files/invalidptr.txt

  [DELUXE]
If activated, each sender address is checked for a valid MX/A record. This requires an installed Email::Valid module in PERL.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

SMTP error message to reject invalid senders. The literal REASON is replaced by (missing MX,missing PTR,invalid Helo,invalid user) depending on the check.
 

---

Enable Greylisting as described at Greylisting-whitepaper.
It's a new method of blocking significant amounts of spam at the mailserver level, but without resorting to heavyweight statistical analysis or other heuristical approaches.

Enable Delaying for whitelisted users also.

Enable Delaying for spamlovers also.

Add X-Assp-Delayed header to header of all delayed or whitelisted emails.

Enter the number of minutes for which delivery, related with new 'triplet' (IP address of the sending
host + mail from + rcpt to), is refused with a temporary failure. Default is 5 minutes.

Enter the number of hours to wait for delivery attempts related with recognised 'triplet'; delivery is accepted
immediately and the 'tuplet' (IP address of the sending host + sender's domain) is whitelisted. Default is 28 hours.

Enter the number of days for which whitelisted 'tuplet' is considered valid. Default is 36 days.

Perform the IP address checks of the sending host based on the /24 subnet it is at rather than the specific IP.
This feature may be useful for legitimate mail systems that shuffle messages among SMTP clients between retransmissions.

Some mailing lists (such as Ezmlm) try to track bounces to individual mails, rather than just individual recipients,
which creates a variation on the VERP method where each email has it's own unique envelope sender. Since the automatic
whitelisting that is built into Delaying depends on the envelope addresses for subsequent emails being the same,
the delay filter will attempt to normalize the unique sender addresses, when this option is checked.

If a whitelisted 'tuplet' is ever associated with spam, viri, failed rbl, spf etc, it is deleted from the whitelist.
This renews the temporary embargo for subsequent mail involving the tuplet.

Delete outdated entries from triplets and whitelisted tuplets databases every this many seconds.
Note: the current timeout must expire before the new setting is loaded, or you can restart. Defaults to 1 hour.

Enter IP addresses that you don't want to be delayed, separated by pipes (|). There are misbehaving MTAs that will not be able to get a legitimate email through a Greylisting server because they do not try again later. An INCOMPLETE list of such mailers is available at cvs.puremagic.com/viewcvs/Greylisting/schema/whitelist_ip.txt.
When using mentioned list remember to add trailing dots in IP addresses which specify subnets (eg. 192.168 -> 192.168. ).
For example: 127.0.0.1|192.168.

SMTP reply message to refuse delayed mail. Default: 451 4.7.1 Please try again later
 

---

Enable Sender Policy Framework Validation as described at spf.pobox.com.
This requires an installed Mail::SPF::Query module in PERL.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

Enable Sender Policy Framework Validation for whitelisted users also.

Enable Sender Policy Framework Validation for nonprocessed messages also.

Add Received-SPF header to header of all emails processed by SPF.

SMTP reply for SPF failed messages. Default: '554 5.7.1 failed SPF: SPFRESULT'
The literal SPFRESULT (case sensitive) is replaced by the actual result.

If the sending domain does not publish its own SPF Records a local policy can be defined.
The default is v=spf1 a/24 mx/24 ptr ~all

Intentionally fail SPF softfail status responses

Intentionally fail SPF neutral status responses

Enables verbose debugging of SPF queries within the Mail::SPF::Query module.
 

---

Enable Sender Rewriting Scheme as described at spf.pobox.com/srs.html.
This requires an installed Mail::SRS module in PERL.
You should use SRS if your message handling system forwards email for domains with published spf records.
Note that you have to setup the outgoing path (Relay Host & Port) to let ASSP see and rewrite your outgoing traffic.

SPF requires the SMTP client IP to match the envelope sender (return-path). When a message is forwarded through
an intermediate server, that intermediate server may need to rewrite the return-path to remain SPF compliant.
For example: thisdomain.com

A key for the cryptographic algorithms -- Must be at least 5 characters long.

Enter the maximum number of days for which a timestamp is considered valid. Default is 21 days.

The number of bytes of base64 encoded data to use for the cryptographic hash.
More is better, but makes for longer addresses which might exceed the 64 character length suggested by RFC2821.
This defaults to 4, which gives 4 x 6 = 24 bits of cryptographic information, which means that a spammer will have
to make 2^24 attempts to guarantee forging an SRS address.

Bounce messages that fail reverse SRS validation (but not a valid SMTP probes)
will receive a 554 5.7.5 [Bounce address not SRS signed] SMTP error code.

Enter IP addresses that you don't want to validate bounces from, separated by pipes (|). For example: 127.0.0.1|192.168.
 

---

This requires an installed Net::DNS module in PERL. Senders that fail RBL validation will receive RBLError SMTP error code. Note: no error is sent if RBL is in test mode.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

Enter IP addresses that you don't want to be RBL validated, separated by pipes (|). For example: 127.0.0.1|192.168.

Enable RBL for whitelisted users also

Add X-Assp-Received-RBL header to header of all emails processed by RBL.

SMTP reply for RBL failed messages. Default: '554 5.7.1 Blacklisted by RBLLISTED'
The literal RBLLISTED (case sensitive) is replaced by the actual serviceproviders(s).

Domain Names of RBLs to use separated by "|". Defaults are...
zen.spamhaus.org|list.dsbl.org|dul.dnsbl.sorbs.net
You may try a more expanded list:
zen.spamhaus.org|bl.spamcop.net|list.dsbl.org|dul.dnsbl.sorbs.net|blackholes.five-ten-sg.com
and increase Maxreplies accordingly to 5, Maxhits should then be set to 2.

A reply is affirmative or negative reply from a RBL.
The RBL module will wait for this number of replies (negative or positive) from the RBLs listed under Service Provider for up to the Maximum Time below.
This number should be equal to or less than the number of RBL Service Providers listed to allow for randomly unavailable RBLs

A hit is an affirmative response from a RBL.
The RBL module will check all of the RBLs listed under Service Provider,
and flag the email with a RBL failure flag if at least this number of RBLS return a positive blacklisted response.
This number should be less than or equal to Maximum Replies above and greater than 0.
If the number of hits is greater or equal Maximum Hits, the email is flagged failed.
If the number of hits is greater 0 and less Maximum Hits, the email is flagged neutral

This sets the maximimum time in seconds to spend on each message performing RBL checks.

This sets the RBL socket read timeout in seconds.

If set, ASSP will remember RBL Hits and block the failed IPs as early as possible.This is done if RBLFailLog >= 6 (discard) RBL Testmode or RBL Spamlover will also disable this!

If set, ASSP will remember RBL Hits and block the failed IPs as early as possible even if RBLFailLog IS NOT >= 6 (discard). RBL Testmode or RBL Spamlover will be ignored.

IP's in cache will be removed after this interval(hours).
 

---

[DELUXE]
Enable URI Blocklist. Messages that fail URIBL validation will receive URIBLError SMTP error code. This requires an installed Net::DNS module in PERL.
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

Domain Names of URIBLs to use separated by "|". Defaults are: multi.surbl.org

List of country code TLDs used to determine the base domain of the uri.

[DELUXE]
0 = deactivate, 1 = activate, 2 = log only, 3 = score only.

Messages with more than this number of URIs in the body will receive URIBLPolicyError SMTP error code.
This prevents DOS attacks, enter 0 to disable feature (not recommended).

Messages with more than this number of unique domain URIs in the body will receive URIBLPolicyError SMTP error code.
This prevents DOS attacks, enter 0 to disable feature (not recommended).

When enabled, messages with obfuscated URIs of types [integer/octal/hex IP, other things!] in the body will receive URIBLPolicyError SMTP error code.