Testing spam detectionįor testing we can use a sample spam email that comes with SpamAssassin. Finally the milter_mail_macros setting defines several variables that rspamd expects for better spam detection. rspamd then runs its checks and tells Postfix whether the email should pass or get rejected. The non_smtpd_milters setting is optional – it makes Postfix have all emails checked that originate from the system itself. The smtpd_milters setting defines that connection for emails that came into the system from the internet via the SMTP protocol. Postfix will now connect to rspamd that is listening to TCP port 11332 on localhost (127.0.0.1) and pass the email over that connection. Run these commands on the shell: postconf smtpd_milters=inet:127.0.0.1:11332 Let’s tell Postfix to send all incoming email through rspamd. The higher the score – the more likely the email should be considered unsolicited. rspamd runs a lot of checks on the email and computes a total score. Every time an email enters ryour system, Postfix will send it to rspamd to have its content checked. It listens to connections from Postfix using the milter (= mail f ilter) protocol. Rspamd is a permanent process that runs on your mail server. However I have found a piece of software that is more versatile, scales better and is still easy to integrate: rspamd. rspamd has a (maybe biased) comparison on their home page. In previous editions of this guide I used and recommended SpamAssassin. But before you go live let’s do something about the insane amount of spam. You have a perfectly working mail server by now.
0 Comments
Leave a Reply. |