Other advocates hold the position that "my system, my responsibility, your system, your responsibility", implying that an administrator would need a heads-up he would get from letting his relay pass on spam.Integrating SpamAssassin into Postfix using spamd Therefore, one rarely sees a hijacked relay, or a spammer himself, generate a bounce, which solves the problem. The advocates of this approach points out that spammers have no interest in generating bounces, as that would only cut into their own spamming bandwidth and make them less efficient. That's the main reason why some consider this approach harmful. If a relay under a spammer's control generate a bounce message based on your rejection, that bounce may go to an innocent third-party, which would be bad. Spammers often take over relays to obscure the true source of the spams. If you are to use this, your primary and secondary MX should have identical configurations with respect to rejecting spam. You can't, for example, have your secondary MX accept a message and then have your primary reject it. For one thing, you can't accept a message and then bounce it, that would be wrong. Therefore, it is very important that your system doesn't generate a bounce. This means that if there is a bounce generated, it will go to this address, which can be randomly generated, or worse, an innocent third party. The problem is, spammers (and viruses) routinely forge the from address on the envelope. It is controversial whether rejecting at SMTP time is such a good idea. This is meant to give a taste of what is involved in getting it working. However, note that any errors can result in loss of valid e-mail, so make sure you have read and understand the official documentation before you use it. User=debian-spamd argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f $ We have to add the spamassassin service by adding: The spamc binary passes the email to spamd (daemonized SA) and then back to the mail queue.Īdd to your smtp/smtps and submission service: SA will be used as a content filter for the postfix 'smtp' (and submission) binary. You will need these packages (and resulting dependencies): postfix spamassassin spamc It is assumed that postfix is installed and configured properly. This tutorial will show you how to integrate SA into postfix to scan your emails for spam. Setup Postfix with SA 3.4.2 (Buster) as a Content Filter Spamc - Client for SpamAssassin spam filtering daemonĪs SpamAssassin is a targetting a moving target, it is wise to keep it quite up-to-date, as spammers adapt to the filters to get their spew through. Spamassassin - Perl-based spam filter using text analysis The Debian distribution contains the following main SpamAssassin packages: The 68-byte GTUBE string used for this is as follows: XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X The premise of this is simple send an email with the GTUBE string as its body to your mail server from an external mail address and SpamAssassin should automatically mark it as spam. The official SpamAssassin homepage is at Īfter having set up SpamAssassin one can easily test if it is indeed working properly by using GTUBE (Generic Test for Unsolicited Bulk Email) (SpamAssassin wiki page on this: ). It has a wide range of features, uses DNSBL tests, heuristics, Bayesian classification and other concepts to tell your spam from ham. SpamAssassin is an extensible email filter which is used to identify spam. ToDo: This page needs to be brought up to date. Translation(s): English - Italiano - Português Brasileiro - Русский
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |