Amavis Troubleshooting

Greylisting must be disabled on the recipient domain before running these tests.

Spam Filter Testing

To test the spam filter, it is necessary to send a Gtube test spam email using the command below (Replacing emailonserver@example.com with a real email account on the server). If the Anti-spam is working correctly you will see it listed in the maillog and in Warden log under Warden -> Logs -> Message Log. While testing, note that Gtube test email gives +1000 scores to spam. So, even if a mailbox is in the whitelist, mail still be detected as spam because whitelisted email gets -100 scores.

Disable Greylisting

If greylisting is enabled then you must disable it on the recipient domain before running these tests.

/usr/local/psa/bin/grey_listing --update-domain example.com -status off

Centos / RHEL / CloudLinux

echo "XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X" | mail -S smtp=localhost -r sender@example.com -s "Spam test example" emailonserver@example.com

Debian / Ubuntu

apt-get install s-nail
echo "XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X" | s-nail -S smtp=localhost -r sender@example.com -s "Spam test example" emailonserver@example.com

Restarting Amavis

Centos / RHEL / CloudLinux

// restart amavis
systemctl restart amavisd

// amavis log file
tail -f /var/log/maillog  

// amavisd-milter restart 
systemctl restart amavisd-milter

// amavisd-milter log file
tail -f /var/log/maillog 

Debian / Ubuntu

// restart amavis
systemctl restart amavis

// amavis log file
tail -f /var/log/maillog 

// amavisd-milter restart 
systemctl restart amavisd-milter

// amavisd-milter log file
tail -f /var/log/maillog