1/31/2024 0 Comments Test spamassassin![]() In order to efficiently integrate Postfix and spamassassin, we will need to create a dedicated user and group to run the spam filter daemon: # useradd spamd -s /bin/false -d /var/log/spamassassin Once you’ve saved those changes, enable and start the spam filter service, and then update the spam rules: /etc/init.d/spamassassin restartįor more configuration options, you may want to refer to the documentation by running perldoc Mail::SpamAssassin::Conf Setting required_score to a value somewhere between 8.0 and 10.0 is recommended for a large system serving many (~100s) email accounts. ![]() The lesser the number, the more sensitive the filter becomes. To set the aggressivity of the spam filter, required_score must be followed by an integer or decimal number. If it is set to 1, the message will be deleted. When report_safe is set to 0 (recommended value), incoming spam is only modified by modifying the email headers as per rewrite_header. The main configuration file is /etc/mail/spamassassin/local.cf, and we should make sure the following options are available (add them if they are not present or uncomment if necessary): local.cf If it finds, according to its definition rules and configuration, that an incoming message is spam, it will rewrite the subject line to clearly identify it as such. ![]() In the process of receiving email, spamassassin will stand between the outside world and the email services running on your server itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |