On Mon, Jul 08, 2002 at 11:13:16AM -0500, Kip Turk wrote: | On Mon, 8 Jul 2002, Bart Schaefer wrote: | | > Hmm, here's a thought. Each SA rule could (optionally) be assigned a | > "category" (porn, UCE, MLM, fraud, etc.). SA could then tally up a | > "category score" as well as a basic spam score, and the subject tag could | > be selected using the category that scores highest.
This sounds good. You're talking about adding it to the report,
right? Or perhaps a separate X-Spam-Categories: header.
| God no, please. It was hard enough getting our customers to put the
| single filter rule for ******SPAM****** in their e-mail clients. Having
| to go back and add umpteen million more defeats the purpose of the
| subject tag.
The subject should be short and sweet. I like "***SA:_HITS_***"
because it is short, and tells me how bad the message is in one shot
(and allows for lexical sorting on "score").
| I don't think OE and the other GUI clients are case sensitive by
| default, so switching to ******spam****** should be safe.
If they are, just use a local rule to switch it back.
| Anything further is going to affect thousands of non-technical users
| who just want the crap out of their mailbox and thought they were
| all done with the hard part. Although, if SpamAssassin as an entity
| had to make the change to avoid legal issues,
| I'd probably just add a global procmail rule to rewrite it back
| within my organization and save our support crew a ton of headaches.
Nah, just set subject_tag appropriately in local.cf. Then SA will put
the desired tag in the subject.
-D
--
A Microsoft Certified System Engineer is to information technology as a
McDonalds Certified Food Specialist is to the culinary arts.
Michael Bacarella commenting on the limited value of certification.
http://dman.ddts.net/~dman/
msg07174/pgp00000.pgp
Description: PGP signature
