Re: Spam filtering on the lists
On Fri, 2002-04-05 at 10:13, Jean-Marc V. Liotier wrote: (Re: *SPAM* ()XX XX XX...) According to these headers contained in the message received from the list, SpamAssassin has correctly tagged it as Spam. So why was it forwarded anyway? Because it might not be spam, but only a false hit ?? Because blocking mail by the list could be considered some kind of sensorship ?? BTW, because you used multiple X's in 3 different words, your mail also scored 1.896 points for 'Uses words and phrases which indicate porn (3)'. This is not very much (and is compensated by using a In-Reply-To: header worth -5.029 points, so I did receive your message, but you get the idea :) I use spamassassin on my home and work mailservers (when I receive this message back from the mailinglist I know it has been checked 4 times by various spamassassins) and I really like it, but even spamassassin is not perfect enough to use it to really block mail. -- Tot ziens, Bart-Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Spam filtering on the lists
On Fri, 5 Apr 2002 15:09, Bart-Jan Vrielink wrote: According to these headers contained in the message received from the list, SpamAssassin has correctly tagged it as Spam. So why was it forwarded anyway? Because it might not be spam, but only a false hit ?? Because blocking mail by the list could be considered some kind of sensorship ?? Isn't sensorship the point of a spam sensor? hehe What's wrong with bouncing the message and asking the user to fix it before sending it again? -- If you send email to me or to a mailing list that I use which has 4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Spam filtering on the lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 05 April 2002 6:48 am, Russell Coker wrote: On Fri, 5 Apr 2002 15:09, Bart-Jan Vrielink wrote: According to these headers contained in the message received from the list, SpamAssassin has correctly tagged it as Spam. So why was it forwarded anyway? Because it might not be spam, but only a false hit ?? Because blocking mail by the list could be considered some kind of sensorship ?? Isn't sensorship the point of a spam sensor? hehe What's wrong with bouncing the message and asking the user to fix it before sending it again? I like the way it is, because it clearly marks what is (probably) spam, and all I have to do is put 1 rule in my mailer that moves everything with a subject containing **SPAM** to the trash. However, it relieves the burden on the mailist admins to clear out the inbox, and lets through messages that are legit but would otherwise get bounced (like the XXX example). Basically, this is the coolest approach I've seen a list take so far. Mad props to whoever came up with the idea! - -- D.A.Bishop -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8rcNfEHLN/FXAbC0RAjIKAKDu9CACY/Z6DHAcUKmg2tMQm/bEzwCfSrLL f/YY/SQ491ZCPLu8UTDVvFQ= =hgdW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
