Re: SpammAssassin on WHM/Cpanel

2006-06-25 Thread SM

At 07:11 25-06-2006, Ken Dawber wrote:
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


This is the first time I see someone saying that. :)

1) Is there some way for the server system administrator who is 
using WHM/CPanel to change the default configuration so that SA 
setup is on the Webmail control panel rather than the Cpanel 
interface? If so, what do I have to tell the system admin to do?


That should be possible if the system admin writes the code to do that.

2) Assuming there is no easy way to do this, is the problem in the 
way cpanel is implemented or in the way SA is implemented.


The restrictions are in CPanel.

3) I notice mention of the need to feed spam  ham to SA. The cpanel 
interface doesn't seem to have any interface for the email user to 
tell it what was identified as spam was ham or that what was 
specified as ham was in fact spam. Should there be such an interface 
or is there one already that I just haven't understood.


SpamAssassin does not come with an interface.  The interface you 
see is implemented by CPanel.  If you have ssh access, you can use sa-learn.


Regards,
-sm 



RE: SpammAssassin on WHM/Cpanel

2006-06-25 Thread Greg Allen

 -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)