Bug#398224: Re: This is a design flaw

[Dominic Hargreaves]

[adding CC to current package maintainer]

On Mon, Feb 07, 2011 at 07:42:05PM +0100, Andreas Metzler wrote:

> Howwever I have grown quite strongly oppoesed to add special
> (disabled by default) greylisting code to the default configuration.
> Judging from reading exim-users there seem to be two widely different
> approaches to greylisting:

Hmm, okay. I guess with the choice of multiple implementations you don't
want to be stuck in between them.
 
> #1 run it very early (after rcpt verification) since it is cheap on the
>    recipient side
> #2 run it late, only for suspicious senders (i.e. after DATA, for high
>    spam-scores)
> 
> Also at least for #2 people often do away with the daemon and use
> exim's sqlite lookup http://wiki.exim.org/SimpleGreylisting
> 
> There are multiple daemons available, most requiring different setups.
> (Me personally I am using postgrey.) 

So it's possible that greylistd doesn't provide any real benefit if it's
possible to implement similar things without any extra code. It sounds like
I should spend a bit of time looking at the various options before committing
time to significant updates to greylistd.

Thanks for the prompt reply.

Dominic.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)