ConfigServer Community Forum

Here's an update.

cPanel 11.46.0 (build 9) with SpamAssassin 3.4.0. Wasn't that version supposed to fix at least some of that excessive spam problem?

It doesn't.

Suggestions?

Peace,
Gene

Consider yourself lucky. The ones I've tried, where they have negative reputations, are just a handful.

Peace,
Gene

Just an update with the spam received on September 8. While one of the IP numbers has a poor reputation, only one message came from that number. So this is a moving target, and trying to block ranges is mostly a waste of time.

Peace,
Gene

Yes, spam, but only five messages are listed in the report. So this is going to be a moving target.

At least, since all these problems have first been reported, the amount of uncaught spam is lower — still not quite there, but improved.

Peace,
Gene

OK, I have gone through all the IP numbers sending uncaught spam in the last day or so. Only this IP was listed as having a bad rating. So it's blocked. Thanks.

At least it's progress — but I still suspect the IP numbers will continue to vary.

Peace,
Gene

So, to use one example of spam that I'm happy to post publicly, if the IP number is 103.252.96.99, you remove the "99" from it and add /24? I'm a little light on this stuff, so explain carefully. Also, I would presume IP numbers are sometimes spoofed, and spammers would use a wide range in...

One more thing: It appears that cPanel won't update SpamAssassin till some time this fall, even though the current version reportedly isn't getting rules updates:

http://features.cpanel.net/responses/up ... ssin-340_2

Peace,
Gene

They take their time. So that means you'll update anything that needs to be updated when/if they update?

Peace,
Gene

One more thing: Sarah: Are you folks going to upgrade to newer SpamAssassin versions in the near future? Wouldn't that improve protection? Specifically: 2014-02-11: SpamAssassin 3.4.0 has been released adding native support for IPv6, improved DNS Blocklist technology and support for massively-scalab...

What I see on the group is that the spammers are playing tricks with headers that are bypassing SpamAssassin, so it's up to the developers to devise workarounds for this. It has actually gotten a bit better as of today.

Peace,
Gene