Phil Randal wrote:
> Oliver Fromme wrote:
> > That's true. The problem you described can happen if the
> > "autowhite" value is shorter than the "timeout" value.
> > I've set both to 5d and didn't have any problems.
> >
> > The documentation should mention that the "autowhite"
> > setting should be at least as long as the "timeout"
> > setting (or longer, of course), and the default values
> > should obey that.
>
> Computers are cleverer than mere mortals, so let milter-greylist do that
> consistency checking for us.
I hate programs that try to be cleverer than me. There
are already too many of those.
> Milter-greylist should use max(specified_autowhite,timeout) as the
> autowhite value, put a warning message into the log, and continue.
No. It should use exactly the values I tell it to use.
Producing a warning message is OK, of course. That's
exactly what milter-greylist's -c option is good for.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
"C++ is the only current language making COBOL look good."
-- Bertrand MeyerMessage
Re: [milter-greylist] FYI: Murphy's law of autowhitelist
2006-11-13 by Oliver Fromme
Attachments
- No local attachments were found for this message.