Spamassasin Question

[Dos_Box]

If Geoff, or anyone who knows Spamassasin is looking at this Then please answer ASAP.

 

Can SA meet the following points?

 

•Must be capable of only filtering mail from selected domains. I.E. Its default configuration will be to allow all mail through and we add the mail domain to be filtered afterwards.

•It should be capable of tagging mail as spam and forwarding it to a ‘parking’ account. It can then be released from this account should it prove to be a false positive. I.E. A mail addressed to [email protected] would be renamed to [email protected] .

•It should have a web or terminal interface so as to be operated by the web team so as to be able to add addresses to blacklists.

•Should be capable of working in-line with our current mail server so as to filter mail as a separate physical server then pass the mail traffic onto our existing mail server.

•It must be capable of existing with our AV solution (Trend AV) on the ‘in-line’ server.

 

This is quite urgent. Can anyone help?

[Geoff]

Must be capable of only filtering mail from selected domains. I.E. Its default configuration will be to allow all mail through and we add the mail domain to be filtered afterwards.

 

The standard black/white/greylisting functionality should be sufficent. Your not doing anything wierd here, just backwards. I suspect the human in this process will be the limiting factor in its effectiveness. You might want to reconsider this approach.

 

It should be capable of tagging mail as spam and forwarding it to a ‘parking’ account. It can then be released from this account should it prove to be a false positive. I.E. A mail addressed to anyteacher @ school.lancsngfl.ac.uk would be renamed to spam.anyteacher @ school.lancsngfl.ac.uk

 

Spam Assassin can certainly redirect mail it determines to be spam to a specifc account. What you do with it afterwards is your own business. If you wish to reinject it into the smtp server for normal delivery you will have to consult your mail server documentation on how to do it.

 

It should have a web or terminal interface so as to be operated by the web team so as to be able to add addresses to blacklists

 

The blacklists are text files. I'm sure the web team can cook up something. Or just use your favorite *nix text editor. You might want to use RCS on them too incase someone screws up.

 

I vaguely recall SpamAssassin will support MySQL aswell if you compile it in. I'm sure the webteam can attack things from that angle if they prefer.

 

Should be capable of working in-line with our current mail server so as to filter mail as a separate physical server then pass the mail traffic onto our existing mail server.

 

It must be capable of existing with our AV solution (Trend AV) on the ‘in-line’ server.

 

Have a look at Amavisd-new. Its what I'm using here. Also, if you wish to use Sophos aswell (I know you have it) you might want to plug it in using Sophie.

[Dos_Box]

Cheers Geoff. We have to allow all mail through initially as it is against the law to inhibit mail that is not infected with a damaging payload without the schools permission. Once they have sign to agree to have their mail scanned then they will be added to the list.

 

As regards to Sophos, we don't have a mail scanner licence (V. expensive) but we have one for Trend AV which does a stirling job. We are just going to move it off the mail server and ontot he spam box.

[Geoff]

As regards to Sophos, we don't have a mail scanner licence (V. expensive) but we have one for Trend AV which does a stirling job. We are just going to move it off the mail server and ontot he spam box.

 

Should I have a licensce then? because thats what I'm using it for...

 

You might want to plug in ClamAV too.