I am having the same problem, this is NOT a DNSSTUFF issue, it is in fact a problem that MagicSpam does not follow the correct RFC!!! MagicSpam is sending a SMTP Banner / Greeting that does not conform to the standards. It should be 220 mail.whateverdomain.com Instead MagicSpam is sending 220 Spam p...

Many remote servers are rejecting mail from our domain when running MagicSpam because the SMTP banner is displayed as: 220 Spam Protection provided by MagicSpam www.magicspam.com ESMTP and thus does not contain our domain name in the banner. This is triggering spam rules on servers that match the ad...

Since installing MagicSpam alot of remote email servers are now rejecting mail that we are sending out with the following error:

550 A valid sender header is required in message (email@address.com)

I have replaced the actual email address for protection.

Why would this be?

Hi, I have just installed the MagicSpam module and it seems to be running, however on inspecting the maillog file I see the following line crop up a few times: May 19 18:19:09 mail magicspam[31005]: [/var/cache/bms/incoming/23.bz2]: current bz file is corrupt. Removed. What is it and how can I fix it?