SPAM Lover/No Processing
From ASSPSMTP
On This Page |
How It Works
Details
SPAM Lover/No Processing FAQs
SPAM Lover/No Processing Configuration
based upon version 1.3.5(9.18)
- Suppress Spam Subject and Tag to Spam-Lover-Messages (spamSubjectSL)
- If set spamSubject and spamTag gets NOT prepended to the subject of the Spam-Lover-Message.
- All Spam-Lover* (spamLovers)
- Messages to Spam-Lovers are processed and filtered by ASSP, but get tagged with spamSubject and not blocked. When a Spam-Lover is not the sole recipient of a message, the message is processed normally, and if it is found to be spam, it will not be delivered to the Spam-Lover. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). Wildcards are supported (fribo*@domain.com). Default: postmaster|abuse.
- For example: fribo*@thisdomain.com|jhanna|@sillyguys.org
- Regular Expression to Identify Spam-Lover* (SpamLoversRe)
- If an message matches this regular expression it will be considered a Spam-Lover message.
- Bayesian Spam-Lover* (baysSpamLovers)
- Regular Expression to Identify Bayesian Spam-Lover* (baysSpamLoversRe)
- If an message matches this regular expression it will be considered a Bayesian Spam-Lover message.
- For example: passwor|news
- Do not store Bayesian Spam-Lover in SpamDB (baysSpamLoversRed)
- Mail to Bayesian Spam-Lover will not be stored in Spam/Notspam folder.
- Blacklisted Domains Spam-Lover* (blSpamLovers)
- Bomb Spam-Lover* (bombSpamLovers)
- HELO Blacklisted Spam-Lover* (hlSpamLovers)
- Valid/Invalid Helo* (hiSpamLovers)
- Bad Attachment Spam-Lover* (atSpamLovers)
- SPF Failures Spam-Lover* (spfSpamLovers)
- DNSBL Failures Spam-Lover* (rblSpamLovers)
- URIBL Failures Spam-Lover* (uriblSpamLovers)
- Not SRS Signed Bounces Spam-Lover * (srsSpamLovers)
- No Delaying Spam-Lover* (delaySpamLovers)
- Invalid Sender Spam-Lover* (isSpamLovers)
- Missing MX Spam-Lover* (mxaSpamLovers)
- Invalid/Missing PTR Spam-Lover* (ptrSpamLovers)
- Penalty Box Blocking Spam-Lover * (pbSpamLovers)
- All Spam-Haters* (spamHaters)
- Spam-Haters are used to override Spam-Lovers. Example: If you have set your entire domain as a Spam-Lover(s), but there are still some addresses you still wish to block spam for. If you add those addresses to the Spam-Haters field allows messages to only those addresses to be blocked while still allowing the messages to the other Spam-Lovers pass through. The message will only be blocked if all recipients are Spam-Haters. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). Wildcards are supported (fribo*@domain.com).
- For example: *fribo@thisdomain.com|jhanna|@sillyguys.org
- Bayesian Spam-Hater* (baysSpamHaters)
- DNSBL Failures Spam-Hater* (rblSpamHaters)
- HELO Blacklisted Spam-Hater** (hlSpamHaters)
- Switch Spam-Lover to Message Scoring (switchSpamLoverToScoring)
- Put the filter automatically in "Message Scoring Mode" when Message Mode is set (instead of stopping spam processing altogether).
- No Processing Addresses* (noProcessing)
- Mail solely to or from any of these addresses are proxied without processing. Like a more efficient version of Spam-Lovers & redlist combined. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). Wildcards are supported (fribo*@domain.com).
- No Processing Domains* (noProcessingDomains)
- Domains from which you want to receive all mail and proxy without processing. 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.
- For example: sourceforge.net|@google.com|.buy.com
- No Processing IPs* (noProcessingIPs)
- Mail from any of these IP's will pass through without processing.
- For example: 127.0.0.1|10.|169.254.|172.16.|192.168.
- Regular Expression to Identify No Processing Mail* (npRe)
- If an message matches this Perl regular expression it will pass through without processing.
- For example: 169\.254\.122\.|172\.16\.|\[autoreply\].
- Message Size Limit (npSize)
- ASSP will let pass incoming messages larger than this SIZE (in bytes) without any processing. Empty or 0 disables the feature.
- Process Only These Addresses* (processOnlyAddresses)
- Mail solely to or from any of these addresses will be processed by ASSP. All others will be proxied without processing. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). Wildcards are supported (fribo*@domain.com).
- Note that if an address matches both the NoProcessing and the OnlyTheseProcessing lists, the NoProcessing rules take precedence.
- Enable Process Only Addresses (poTestMode)
These icons link to social bookmarking sites where readers can share and discover new web pages.
