> -----Original Message----- > From: Ken Dawber [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 25, 2006 10:12 AM > To: users@spamassassin.apache.org > Subject: SpammAssassin on WHM/Cpanel > > > I have a reseller shared hosting account under WHM/Cpanel software. (In > other words I’m not a systems admin) The Cpanel is a control panel for > web hosting. The implementation includes Spamassassin (SA) From what I > have seen on shared hosting, Cpanel is probably the most heavily used > domain hosting control panel and consequently the way a large proportion > of standard SA users obtain access to SA. > > There seems to be some problems either in Cpanel or SA in the places > where I have used it. > > As implemented, the various parameters for SA can only be set from the > Cpanel control panel. Only the administrator of the domain has access to > this. > > While the individual email users do get their own email control panel, > it does not contain any ability to turn on and set up the SA parameters. > Since each actual email user is likely to have a different email client > which they may or may not want to integrate with SA and different needs > in terms of spam elimination versus ensuring no email is inadvertently > missed, the setup should be done by the email user, not the domain > administrator.
I don't know anything about the programming internals of Cpanel, but I do have several Cpanel admin (website) accounts. So, generally speaking... Cpanel uses a very very basic implementation of SA. It is best not to even use it IMO. It is nearly worthless. It does not have most tests enabled that the full SA does, when setup correctly. It also does not use bayes. What you see in Cpanel for SA is what you get. Remember, with Cpanel you are sharing a SINGLE server with many other websites in a shared hosting environment. That is why Cpanel has to set it up so generic. It would be best to put a real SA server in front of your Cpanel inbound email server. Set it up the way you want it for your domain. The SA server can be at a different location, and use Postfix transport map to send the SA filtered email back to the Cpanel server for delivery. Disable Cpanel SA implementation all together. (that is how I run it)
