[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sylpheed
Subject:    [sylpheed:28126] Re: help on filtering
From:       "Randy.Dunlap" <rdunlap () xenotime ! net>
Date:       2006-06-28 20:07:27
Message-ID: 20060628130727.22f4c6fb.rdunlap () xenotime ! net
[Download RAW message or body]

On Wed, 28 Jun 2006 21:23:49 +0200 Stefaan A Eeckels wrote:

> On Wed, 28 Jun 2006 08:50:13 -0700
> "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> 
> > Are there any aids to see why sylpheed filtering places certain
> > messages into their destination folders?  I have about 200 filter
> > rules.  Most of them attempt to put spam into "killfile".
> > However, sometimes I see good messages in "killfile" also
> > and I'd like to determine why they are being placed there.
> 
> I second the endorsement of bogofilter, which has worked very well for
> me for years (I use it to filter all incoming mail before it hits the
> various inboxes) and has consistently outperformed costly commercial
> offerings such as Barracuda. 

Yes, I'm trying it out now.

and consolidating some of the sylpheed filter rules.

Thanks for all the feedback.

> It works so well that a SPAM that gets through becomes a talking
> point :)
> 
> You should also not try to filter all spam mail, but write rules to
> filter all the ham - that's on the whole rather easier to do than
> anticipating spammer and scammer creativity. OK, they might forge a
> source address and get through if you deal with large organisations or
> if most of your correspondents use free addresses (in this case you
> really should install bogofilter as it handles this with consummate
> ease), but on the whole, it's safe to dump whatever is not ham in a
> "Suspected SPAM" folder and look at it when required.

---
~Randy

[prev in list] [next in list] [prev in thread] [next in thread]