Hello,
We've been upgrading some of our servers to cPanel v11 recently and it seems there's a lot of differing opinions about what functionality changes the new version brings to SpamAssassin, can anyone tell me what, if any, functionality changes have occurred as a result of the new ACL style SpamAssassin?
I've heard many different stories both specific and vague, from per domain subject rewrites not functioning, to directives in the user_prefs file being ignored, to spamassassin simply not filtering as much spam out as it had in the past. But I'm not sure which of these are just a result of the new style spamassassin and which are actual problems. For the time being we've continued to use the old transport based spamassassin as that seems to stop the complaints but as mentioned numerous times this is inefficient and we also have a lot of mail volume on our servers which causes the transport-based spamd process to hit its "max children" limit at times which causes transport filter timeouts in exim and ultimately a backlogged mail queue. So if anyone can point out what changes have come about due to the new acl based spamassassin and what functionality should remain the same... it would be greatly appreciated.
Onto courier-imap now, we've often had problems with the POP and IMAP daemons hitting the maxdaemons limit set for them. This never seemed to be a problem on mbox style servers where I'm not sure there was any limit at all... does anyone have any advice on dealing with this or what maxdaemons and maxperip can be safely set to in the courier-imap service config files?
Thanks!
We've been upgrading some of our servers to cPanel v11 recently and it seems there's a lot of differing opinions about what functionality changes the new version brings to SpamAssassin, can anyone tell me what, if any, functionality changes have occurred as a result of the new ACL style SpamAssassin?
I've heard many different stories both specific and vague, from per domain subject rewrites not functioning, to directives in the user_prefs file being ignored, to spamassassin simply not filtering as much spam out as it had in the past. But I'm not sure which of these are just a result of the new style spamassassin and which are actual problems. For the time being we've continued to use the old transport based spamassassin as that seems to stop the complaints but as mentioned numerous times this is inefficient and we also have a lot of mail volume on our servers which causes the transport-based spamd process to hit its "max children" limit at times which causes transport filter timeouts in exim and ultimately a backlogged mail queue. So if anyone can point out what changes have come about due to the new acl based spamassassin and what functionality should remain the same... it would be greatly appreciated.
Onto courier-imap now, we've often had problems with the POP and IMAP daemons hitting the maxdaemons limit set for them. This never seemed to be a problem on mbox style servers where I'm not sure there was any limit at all... does anyone have any advice on dealing with this or what maxdaemons and maxperip can be safely set to in the courier-imap service config files?
Thanks!