

o local_header_rewrite_clients= Restart postfix service postfix restart Testing o receive_override_options=no_header_body_checks,no_unknown_recipient_checks o smtpd_data_restrictions=reject_unauth_pipelining o smtpd_recipient_restrictions=permit_mynetworks,reject o smtpd_client_restrictions=permit_mynetworks,reject o receive_override_options=no_header_body_checksĪdd following towards end: smtp-amavis unix - n - 2 smtp Mail::SpamAssassin::Conf SpamAssassin configuration files. We need to tell postfix to use amavis content-filters during mail processing.įind line containing: pickup fifo n - 60 1 pickupĪdd 2-lines below it so it looks like: pickup fifo n - 60 1 pickup SpamAssassin is an intelligent email filter which uses a diverse range of tests to identify. To finalize changes: service amavis restart Postfix configĬonfiguring amavis alone won’t work. If you are getting too many false positives, you may change $sa_tag_level_deflt to a positive value.įor lookup_sql_dsn, please make sure your mysql database details matches one that is used by postfix & dovecot.
#SPAMASSASSIN CONFIGURE UPDATE#
Note: Adding custom configurations in these files can be overwritten by Plesk update and other actions related to these files. $sql_select_policy = 'SELECT domain FROM domain WHERE IN (%k)' For more information on advanced SpamAssassin configuration, refer to the Advanced Administration Guide, Spam Protection for Linux, and SpamAssassin documentation. # We need to provide list of domains for which filtering need to be = ( # Prevent spams from automatically rejected by mail-server Set filtering preference:Īdd following: $sa_spam_subject_tag = undef Also note that these checks delays mail delivery (generally by few seconds). ClamAV consumes considerable CPU resources. If your server has less spare CPU power, you may leave virus-checking disabled. \%bypass_spam_checks, \$bypass_spam_checks_re) Enable virus & spam checking: vim /etc/amavis/conf.d/15-content_filter_mode Amavis Configurationīy default, amavis comes with all kind of checks disabled! Might sound strange but we need to enable everything. So we need to configure amavis only to spam & virus filtering implemented. It uses spamassassin for spam-testing and clamav for virus-testing.

Please note that amavis itself doesn’t do any kind of spam-checking or virus-checking.
#SPAMASSASSIN CONFIGURE INSTALL#
Installing packages amavis, clamav, spamassassin apt-get install amavisd-new spamassassin clamav clamav-daemon arj zoo nomarch cpio lzop cabextract apt-listchanges libauthen-sasl-perl libdbi-perl libmail-dkim-perl p7zip rpm unrar-free libsnmp-perl Spam filtering setup using spamassassin.To check your rule syntax for errors, run the command line version with the – lint option. You will also want to run the following command before restarting the service to ensure there are no errors: Rules placed here get applied no matter what user invokes SpamAssassin. On startup, the service will detect any *.cf file found in /etc/mail/spamassassin/. And your choice of place depends on how your copy of SpamAssassin is set up, and what you want the rules to do: /etc/mail/spamassassin/local.cf is the place of choice for site-wide application.


As a result, each message scores a number of points. To identify spam messages, SpamAssassin performs a number of different tests on contents and subject line of each message. The following websites can provide a bit more in-depth on what rules can be added to the configuration: To achieve the desired level of spam protection, Plesk lets you configure a number of SpamAssassin settings, namely: Spam filter sensitivity. Inside this file, you will want to add the options you wish to use. The file name can be anything you wish to use. Configuration files can be located in the following directory: /etc/mail/spamassassin/ You can edit the local.cf, however, we do not recommend editing this file at cPanel. You will want to create a custom configuration file for the change. Apache SpamAssassin does allow the ability to customize how the server processes spam emails.
