SpamAssassin - User Configurable

Just wanted to announce that we've completed our setup for per mailbox SpamAssassin with user prefs.

To enable/disable SpamAssassin and setup your prefs, you'll need to visit http://mail.yourdomain.com Click on the "SpamAssassin" link and you'll be prompted for your username and password. This is just your mailbox username and password (Same that you use to POP/SMTP your mail).

Once in, if SA isn't enabled, you'll be presented with a link. Click the link to enable SpamAssassin. You will then see the Preferences menu. Here you can set your score, whitelists, languages, etc.

CURRENTLY, only mail4 supports this new feature, and we will be adding it to the other mail servers on Monday. This will give us a chance to ensure its 100% before we deploy it across all the servers.

[Brangwyn]

Nice work there Matt

[jmbeach]

yes, very cool - and thank you for not using mail1 as the testing ground

[Brangwyn]

Just a thought, is a couple of days going to be enough to really make sure it's working 100% ? maybe a week or even more would be better considering people are probably on holiday etc, I suspect over the next 2-3 days about all you'll get testing it is a few resellers which may not be enough of a sampling to make sure its all hunky dory.

[bootNumlock]

Brangwyn, you take all the fun out of it--i say let's do it on all servers right now... it's a new year, let's take chances right off the gun!

Hope you all had a happy a safe new year's celebration and wish all a great and prosperous 2004!!!

We had been testing it on our own mail servers and it seemed to work fine there, so we went to mail4 as it has the least amount of load. If it works out there then we move on the the reset of the servers..

Once we get this in place then we are going to see if we can make an option to delete mail and not just just tag it. I my self like the delete option as I hate downloading all that spam to just delete it.. So far we have see SA do very well on what it makes as spam about 98% to 99% right if not better..

I think this will help a lot of the users that did not want SA and also help the users that did want it.. Now if we can just find a fast way to delete it with out puttin the load on the server though the top of the rack.. LoL

[Brangwyn]

We had been testing it on our own mail servers and it seemed to work fine there, so we went to mail4 as it has the least amount of load. If it works out there then we move on the the reset of the servers..

umm yeah, my point is last time though something was tested internally (and I seem to recall it was actually the original SA implementation) it all turned to custard once put on the live machines, as you say mail4 is low volume, combine that with the fact that many people are away for the holidays I really don't think it's going to get the stress test it probably needs.

Letting it go for a bit longer than 2 days testing certainly won't do any harm will it ?

[jtaugher]

Are there any options to enable it for the whole domain -- not on a per user level?

I'm not the one coding the beast but there will probably not be such an option. Domain-wide access depends on the H-Sphere database and is available only through the CP box and SA is not supported by H-Sphere. Access to individual mail accounts is easily arranged since the authentication data for them are stored on the servers themselves.

[jtaugher]

So what must be done exactly to the configuration on a per-user level to make the same functionality as had before?

And I mean *EXACTLY THE SAME* -- I know that my junk-mail filter isn't working like it used to, and I can only imagine what the question will be from my clients on Monday morning. So I'd like to configure each of their email boxes so that they continue to get the same functionality they had before this change was made without any *advance* warning or announcement.

[dlrmartin]

I agree, will be a hard work for us instruct clients or config each mailbox of each domain.

BTW at least if domain level is unavailable, in order to reduce dramatic *visibles* changes to webmail end users I think that previous page for SA is unnecesary.
Is It possible to add SA as a link to @mail homepage, such as "change password"

[dpyers]

I seem to be getting email - flagged as spam - that I believe were previously deleted. Is it possible to use two value variables - one to flag as spam, and one to delete the message?

e.g. "flag as spam if it scores over 5, delete the message if it scores over 10"

BTW... I had a couple of emails from a listserv come in today that were sent last Wednesday. They were flagged as spam. Most likely it is a listserv problem, but it's possible they were hung up in SA. A useful feature would be to timestamp the SA scoring in the email.

if you just enable SA, then it will use the default settings.
Default score is 6.0, Default tag is [SPAM] ... Defaults haven't changed from what they were before.

Originally Posted by dpyers

I seem to be getting email - flagged as spam - that I believe were previously deleted. Is it possible to use two value variables - one to flag as spam, and one to delete the message?

We haven't deleted mail for months now...

We probably wont implement the "2-tier" score since this would require:
1) a command similar to what we used before that killed the machine with high load
2) rewriting spam assassin

Neither of which is gonna happen...

Originally Posted by dpyers

BTW... I had a couple of emails from a listserv come in today that were sent last Wednesday. They were flagged as spam. Most likely it is a listserv problem, but it's possible they were hung up in SA. A useful feature would be to timestamp the SA scoring in the email.

Our server's done hold mail for more than 24 hours, which is plenty sufficient and allows them to clear out the bad bounces (autorespond to spammers mainly). SA takes approximately.... 0.1 seconds to process a message (I think 0.1 is just the lowest number it will show). So, my guess would be its your list serve. Qmai ltags the headers of when it receives and delivers messages, check those.