Per-domain filtering using Bogofilter
David Relson
relson at osagesoftware.com
Tue Aug 26 02:40:54 CEST 2003
On Mon, 25 Aug 2003 17:26:57 +0200
"Noor Dawod" <noor at comrax.com> wrote:
> |
> | Calling bogofilter from a shell script is going to be a little
> slower,| but not by much. On most modern systems, a frequently
> executed program| would be cached in memory so there's very little
> slowdown due to disk| reads. Try it. You'd be surprised at how fast it
> really is.|
>
> I guess you have a point there..
>
> |
> | hmm. Sounds like you're using qmail, which means you'll need to exec
> | several programs in order to filter and deliver the mail anyway.
> |
>
> I'm using Postfix, but that's not the matter. A simple shell that do
> (bogofilter -p | sendmail -i "$@") is enough to wrap Postfix's normal
> SMTP traffic, but it's harder to do a per-domain filtering.
>
> |
> | I strongly disagree with adding this feature when a shell
> | script can do the job just as well.
> |
>
> As you like... but I think it's a good and demanding idea.
>
> Noor
Noor,
Bogofilter looks for directory $HOME/.bogofilter and files bogofilter.cf
and wordlist.db in it. With postfix (and procmail), HOME is defined for
you. With this in place, everything needed for bogofilter to operate on
a "per user" basis is present. If you can map a domain to a userid,
everything you need is there.
David
More information about the bogofilter-dev
mailing list