J Thomas Hancock wrote:
I apologize for the questions, but this is how my Boss wants things
done and who am I to argue with him. I figure he will listen to me
better if I have a creditable source, the SpamAssassin mailing list,
backing me up versus me by myself.
Part 1:
My boss is convinced that SpamAssassin can delete an email if it
crosses a certain hit threshold. Everything I have read states that
SpamAssassin can only add a flag to the message (be it a subject
rewrite, something in the header, ect) and that the MTA, postfix in
our case, rejects the message based on that flag. So am I correct in
stating that SpamAssassin can not delete a message?
Correct.
Part 2:
My last question to this list was how to able to flag the message for
deleting if the required_hits exceeds 15, for argument sake, and
rewrite the subject header if the required_hits exceeds 10. I was told
SpamAssassin could not do that. I looked into using MailScanner, but
the PHB did not like that solution since it took too much
customization to read the users preferences from a MySQL table. We
came up with 2 ugly solutions.
The first solution is to run two instances of SpamAssassin. Instance
one runs the required_hits for deleting the message and the second
instance runs the scan for rewriting the subject. Each instance of
SpamAssassin can run on a different port/IP address. Does anyone here
have any experience with such a configuration?
The second solution would be to set postfix to reject a message if the
header contains “Spam Score 15”, “Spam Score 16”, “Spam Score 17” ect.
Ugly, I know.
What are the thoughts of the members of this list? Does anyone have
any other suggestions besides MailScanner and our two solutions?
Thank you for your assistance.
Tom Hancock
amavis-new can do this nicely. You can set a "tag" level which allows
subject re-writing and a "kill" level above which the email can be
either deleted outright or quarantined (either to a seperate mailbox or
folder on the server).
