I got an interesting spam: it was PGP signed.
Yep, spammers are finding out that software such as spamassassin give negative points (no spam) to such messages.
Of course, the checking of the PGP signature gave me an invalid result, but SpamAssassin don't know that.
The spam was caught by bogofilter, a bayesian filter.
And here we go! Several levels of anti-spam. There's been a tiny amount of false positives with bogofilter. I pratically miss one or two spams a day, in a universe of almost 200 spams.
This is a better ratio than when I used spamassassin alone. (SpamAssassin is deactivated now, so that I can see how effective bogofilter is by itself...)
BTW, I haven't tried the bayesian feature of spamassassin... It should give a similar result to bogofilter.
I'm really thinking on how to implement such tools at clients of mine in a way that they won't poison themselves and start missing messages.
bogofilter (Score:1)
Re:bogofilter (Score:2)
On the flip side, bogofilter is a personal filter, so it's not going to perform that well on larger installations, which kind of breaks the point of being so much faster, doesn't it?
Re:bogofilter (Score:1)
Re:bogofilter (Score:2)
See my talk on this at the spam conference.
Re:bogofilter (Score:1)
Re:bogofilter (Score:3, Informative)
Re:bogofilter (Score:1)
Being a Bayesian filter, it assumes there's a clear line between spam and non-spam. The more people you put in the same filter, the fuzzier that line may get. It's attempting to emulate your personal in-your-head filter.
Re:bogofilter (Score:1)
Re:bogofilter (Score:1)
Hence the phrase "personal filter". :)
Re:bogofilter (Score:1)
BTW, it is also important to reduce server load if you try implementing some automated way to handle spam.
I've been thinking about writing something that will be run from an alias such as $USER-spam and $USER-ham (it will have to check the origin of the message: only the user himself can send messages to these addresses) and will classify the message as one of those using the user's database. Then, procmail or some other thing can compare messag
-- Godoy.
Re:bogofilter (Score:2)
invalid signatures (Score:1)
[which has its own problems]
---ict / Spoon
Black List/White List (Score:2)
Eventually, I suspect that most email software will implement blacklist/whitelist technologies. If a domain/user is on your blacklist, they get discarded. Period. If they are on your whitelist, they get accepted. If they are on neither, any email received will receive an "auto-reply" saying "please respond with an email message requesting that you be added to my white list". Spammers will thus be forced to respond to millions of "whitelist" requests. (the auto response could also simply be informing th
Re:Black List/White List (Score:1)
They demand the answer you talked about. It will, certainly, remove some spammers that use invalid addresses.
On the other hand, the easiness is not that great. See: I'm subscribed to several mailing lists; I see a post from John Doe asking something silly about XYZ's software; I'm in a good mood (this is very important to answer a silly question); I send John Doe an answer and his mail server demands another message from me. I'm sorry, John, I'm not in a good mood anym
-- Godoy.
Re:Black List/White List (Score:2)
I agree that Bayesian filters are a great way to go, but I still think that blacklist/whitelist systems can work.
There are a couple of potential ways to get around the issue you mentioned. If you have a mailing list on your whitelist, than any email that is sent to or CC'd to the mailing list could make it past a whitelist. Of course, that also requires that whoever manages the mailing list take the time to manage the spam. I'm only on "members only" lists and that takes care of the problem quite nicel
Re:Black List/White List (Score:1)
I receive a lot of computer related spam. I suppose they can use messages from the same place where they harvested my email or
-- Godoy.