Talk:SpamAssassin

From Wikipedia, the free encyclopedia

- Changed "Generally regarded" to "regarded by some" to hopefully lose the Peacock. --Ebrockway (talk) 05:23, 27 February 2008 (UTC)

- Added external link citation for "generally regarded" assertion which shows that SpamAssassin received 69% of the vote in the Linux New Media Awards 2006. I also added an External Link to the webpage that references the PDF file of the magazine cite. -- PiPhD 18:10, 14 January 2007 (UTC)

- Added additonal explanation to the second paragraph having to do with user-defined "text-matching." -- PiPhD 18:46, 14 January 2007 (UTC)

The introduction was a little wishy washy so I added direct and clear terms like Baysian filter, since that is what it uses apparently, and took out checksum. I think checksum would be included in the Baysian filter term, if it belongs anywhere, since I think it the wrong term to begin with. Checksum is usually done when comparing directly *two files* for changes, like CRC / CRC32 checks or even MD5 et al is used for this purpose.

Perhaps I am wrong though, anyone have any comments? Also good to see you all here, I can't believe no one has discussed anything yet in here :). --ShaunMacPherson 15:37, 22 Sep 2004 (UTC)

It's "Bayesian". And spamassassin really does use checksums to fight spam by comparing spams against checksums held by spam collections. silsor 15:43, Sep 22, 2004 (UTC)

The introduction doesn't need countless buzzwords, it needs to be as clear and as concise as possible. --Joy [shallot] 16:12, 22 Sep 2004 (UTC)

Also it is no longer licensed under the GPL, and to say that old versions were is a misrepresentation since they were also licensed under the Artistic license, according to the article. silsor 17:52, Sep 22, 2004 (UTC)

How do you begin to use spamassassin where the headers are appearing on messages already?... for users of EMACS RMAIL Regrettably, the question did not get answered at the spamassassin wiki sufficiently. oo-- dWs dsaklad@zurich.csail.mit.edu 18:15, 10 Jun 2005 (UTC)

You mean where SpamAssassin's headers are already there, due to another site already having checked it? If they're interfering with your filtering setup, you could rewrite the X-Spam-* headers (e.g., to X-Old-Spam-Whatever). Here's a quick 'n dirty procmail rule to do it (edit: this needs to go before you run the message through SpamAssassin):

:0 Hf

|awk -vd=1 '/^$/ {d=0;} d{gsub(/^X-Spam/, "X-Old-Spam");} {print;}'

By the way (this is why I hit the talk page in the first place :-)), it's also possible to roll your own spamassassin filter with Mail::SpamAssassin; spamassassin(1) is basically a wrapper around it. I've actually had to do this a few times for custom maildrops, e.g. virtusers, but this functionality wasn't mentioned in the article. --Jack (Cuervo) 30 June 2005 11:58 (UTC)

[edit] proposed link

there's this free software that incorporates spamassassin's engine, it's a freeware, should we put it into external resources? mailingcheck.com —Preceding unsigned comment added by 84.223.15.91 (talk) 15:57, 18 April 2008 (UTC)

I clarified the link to make it easier for humans. But External Resources seems unlikely to be the suitable place. If you look at the other software which incorporates SA they're references to more wiki pages. I'd say that would be the way to reference the product, if at all - a quick Google suggests the software isn't really notable enough to qualify for a reference. Caomhin (talk) 10:29, 19 April 2008 (UTC)