Search Advanced…. New posts. Search forums. Thread starter serg Start date Jun 17, Tags rbl spam spamassassin. JavaScript is disabled.
For a better experience, please enable JavaScript in your browser before proceeding. Hey there! None of my personal machines have the Ah, that would cause other issues. I would comment out that line, and then add the Google public resolvers to ensure things continue to work properly on the machine: Code:.
I've tried that and have restarted spamd. But still have no scores from RBLs: Code:. Content analysis details: I don't believe that's normal - could you create a ticket with our support team so we can do some additional troubleshooting directly on the affected system?
If you are able to do that, please post the ticket number here so I can follow along and keep the thread updated. Sure, Ticket ID: Thank you very much!
Thanks for that! DNS Blocklists are a common form of network-accessible database used in spam detection. The latter usage is incorrect; see RBL. Note that it's extremely important to compare false positive rates nonspam messages marked as spam , as well as spam hit-rates, when evaluating any anti-spam system, include DNS blocklists.
For example, a blocklist that returned a match for every single mail would 'catch all the spam', but would also mark every nonspam mail too.
Some of the above pages omit this information, so take with a pinch of salt. Q: My queries to a DNS-blocklist were blocked. What does this mean? If you were directed to this link from a rule description, then you have a DNS-Blocklist that is purposefully blocking your queries. Resolving the block might be as simple as using your own non-forwarding caching nameserver to avoid being lumped together with other users queries; setting up your own mirror of the DNS-blocklist; or paying to use the blocklist.
The choice is up to the DNS-Blocklist administrator. SpamAssassin supports the "free for some" model since it works for the majority of SpamAssassin installations. However, we do not support methodologies that purposefully return wrong answers and those DNS-Blocklists will be disabled by default. It says "Support for these is built-in" but I can't believe that all free BL's is called each time a mail is beeing checked.
There must be a way to configure which to use. A: You're right. The headers checked for whitelist addresses are as follows: if Resent-From is set, use that; otherwise check all addresses taken from the following set of headers:.
This string is matched against the reverse DNS lookup used during the handover from the internet to your internal network's mail exchangers. It can either be the full hostname, or the domain component of that hostname. In other words, if the host that connected to your MX had an IP address that mapped to 'sendinghost.
For simple cases, it will be, but for a complex network, or running with DNS checks off or with -L , you may get better results by setting that parameter. The headers checked for whitelist addresses are as follows: if Resent-To or Resent-Cc are set, use those; otherwise check all addresses taken from the following set of headers:.
They will be converted to square brackets. The lines will still be properly folded marked as continuing though. Here are some examples these are the defaults, note that Checker-Version can not be changed or removed :. Note that X-Spam-Checker-Version is not removable because the version information is needed by mail administrators and developers to debug problems.
Without at least one header, it might not even be possible to determine that SpamAssassin is running. This setting may be required for safety reasons on certain broken mail clients that automatically load attachments without any action by the user. This setting may also make it somewhat more difficult to extract or view the original message.
If this option is set to 0, incoming spam is only modified by adding some X-Spam- headers and no changes will be made to the body. In addition, a header named X-Spam-Report will be added to spam. If you receive lots of spam in foreign languages, and never get any non-spam in these languages, this may help. If it is not specified, but less than 4 octets are specified with a trailing dot, that's considered a mask to allow all addresses in the remaining octets.
If a network or host address is prefaced by a! If you're running with DNS checks enabled, SpamAssassin includes code to infer your trusted networks on the fly, so this may not be necessary. Thanks to Scott Banister and Andrew Flury for the inspiration for this algorithm. This inference works as follows:. This value is used when checking 'dial-up' or dynamic IP address blocklists, in order to detect direct-to-MX spamming.
SpamAssassin's network rules are run in parallel. This can cause overhead in terms of the number of file descriptors required; it is recommended that the minimum limit on file descriptors be raised to at least for safety. See the documentation for the Mail::SpamAssassin::Plugin::AutoLearnThreshold plugin module for details on how Bayes auto-learning is implemented by default.
Spam messages from certain senders may contain many words that frequently occur in ham. For example, one might read messages from a preferred bookstore but also get unwanted spam messages from other bookstores. If the unwanted messages are learned as spam then any messages discussing books, including the preferred bookstore and antiquarian messages would be in danger of being marked as spam. The addresses of the annoying bookstores would be listed. Assuming they were halfway legitimate and didn't send you mail through myriad affiliates.
Those who have pieces of spam in legitimate messages or otherwise receive ham messages containing potentially spammy words might fear that some spam messages might be in danger of being marked as ham.
The addresses of the spam mailing lists, correspondents, etc. If this options is set the BayesStore::SQL module will override the set username with the value given. This could be useful for implementing global or group bayes databases. This will be quite a bit faster, but may risk file corruption if the files are ever accessed by multiple clients at once, and one or more of them is accessing them through an NFS filesystem.
By default, SpamAssassin will choose either nfssafe or win32 depending on the platform in use. SpamAssassin will attempt to use these, if some heuristics such as the header placement in the message, or the absence of fetchmail signatures appear to indicate that they are safe to use. However, it may choose the wrong headers in some mailserver configurations.
More discussion of this can be found in bug in the SpamAssassin BugZilla.
0コメント