Well, you've challenged me here to look at your dialogs in Magic Spam in a new way. I've been referring to the Limiters as OUTBOUND and INBOUND. You're referring to them as IP and AUTHENTICATED USER. Clearly, the Inbound Rate Limiter only has exceptions based on IP address, and just as clearly the O...

The response to my email and screen shot noted that the limiter threshold shown was very high. Yes, it was. We wanted that sender listed in our exception list to leap over the constraints of the prior settings one way or another. We'll bring it back down when we can get the Outbound Rate Limiter Exc...

Thank you for your kind reply. Hmmm. Perhaps the problem is that there IS NO /etc/magicspam/control/rl_whitelist.list file located in that or any other directory under magicspam. I have rl.db, rl.block, rl.count and rl.flag. The rate exception entry IS contained in /etc/magicspam/ra_whitelist.list. ...

We set the outbound rate at the default levels Magic Spam provided. We then made an exception for a specific user that emails a newsletter to a large group weekly on the WHM Per-User Rate Limiter Whitelist, a list of local addresses that are excluded from outbound rate limit restrictions The user di...

You are correct. We had made some other tweaks to Exim Server at the same time, and located the false alarm there.

I note that as far back as 2008 you were enthusiastic about the implementation of wildcards in a future release of Magic Spam. Here we are 5 years later and I have a pesky problem with *.RU and *.ME spam. It would be wonderful if we could just conclude for some customers that we're not interested in...

I've installed MagicSpam WHM in Unix and am using the default settings.

I note that Port 27, which is a custom Exim port for SMTP is not working and won't restart.

Is Magic Spam doing anything here?