Milter-greylist

In the source, I see:

        #define GLDELAY       1800    /* 1800 seconds = 30 minutes */

In my config file, there is only one delay statement:

        racl greylist list "grey users" delay 30m autowhite 3d

In emails, I see:

        X-Greylist: Delayed for 00:26:40 by milter-greylist-4.2.3
        X-Greylist: Delayed for 00:21:04 by milter-greylist-4.2.3
        etc.

Why?

--- In milter-greylist@yahoogroups.com, "philippeake" <philip@...> In emails, I see:
> 
>         X-Greylist: Delayed for 00:26:40 by milter-greylist-4.2.3
>         X-Greylist: Delayed for 00:21:04 by milter-greylist-4.2.3
>         etc.
> 
> Why?

That is the same tuple trying to send the email after getting a 30-mins delay with greylist. They get a 30 mins delay default. If they try to send the same email after 3 mins 20 secs, they will get: X-Greylist: Delayed for 00:26:40

--- In milter-greylist@yahoogroups.com, "d d" <x55k@...> wrote:
>
> --- In milter-greylist@yahoogroups.com, "philippeake" <philip@> In emails, I see:
> > 
> >         X-Greylist: Delayed for 00:26:40 by milter-greylist-4.2.3
> >         X-Greylist: Delayed for 00:21:04 by milter-greylist-4.2.3
> >         etc.
> > 
> > Why?
> 
> That is the same tuple trying to send the email after getting a 30-mins delay with greylist. They get a 30 mins delay default. If they try to send the same email after 3 mins 20 secs, they will get: X-Greylist: Delayed for 00:26:40
>

I think you are misunderstanding - those lines that you quote above are in the delivered email.

I read them to be saying that "This email was delayed for 00:26:40".
No email should be delivered with anything less than 30 miutes.

These are not logfile entries, they are email headers.

philippeake wrote:
 > --- In milter-greylist@yahoogroups.com, "d d" <x55k@...> wrote:
 > > 
 > > --- In milter-greylist@yahoogroups.com, "philippeake" <philip@> In emails, I see:
 > > > 
 > > >         X-Greylist: Delayed for 00:26:40 by milter-greylist-4.2.3
 > > >         X-Greylist: Delayed for 00:21:04 by milter-greylist-4.2.3
 > > >         etc.
 > > > 
 > > > Why?
 > > 
 > > That is the same tuple trying to send the email after getting a 30-mins delay with greylist. They get a 30 mins delay default. If they try to send the same email after 3 mins 20 secs, they will get: X-Greylist: Delayed for 00:26:40
 > > 
 > 
 > I think you are misunderstanding - those lines that you quote above are in the delivered email.

I think you are misunderstanding.  :-)

 > I read them to be saying that "This email was delayed for 00:26:40".
 > No email should be delivered with anything less than 30 miutes.

That's not entirely true.

If a tuple is inserted into the greylist and another message
with the same tuple arrives ten minutes later, then that
second message could be delayed by as few as 20 minutes.

Of course, the exact delays depend on the retry intervals of
the sending MTA.

 > These are not logfile entries, they are email headers.

AFAIK those are the same.

Best regards
   Oliver

PS:  By the way, I think 30 minutes is rather long as a
default greylist delay for _all_ messages.  Using 10 or
even only 5 minutes will catch almost as much spam while
being less annoying for the recipients of legal mail.

Of course, you might chose to use longer delays depending
on blacklists and similar, but that's a different matter.

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Gesch\ufffdftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M\ufffdn-
chen, HRB 125758,  Gesch\ufffdftsf\ufffdhrer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"Perl will consistently give you what you want,
unless what you want is consistency."
        -- Larry Wall

On Fri, Oct 16, 2009 at 05:34:09PM +0200, Oliver Fromme wrote:
>
> If a tuple is inserted into the greylist and another message
> with the same tuple arrives ten minutes later, then that
> second message could be delayed by as few as 20 minutes.

There is no way for milter-greylist to distinguish two different
messages with an identical ip-from-rcpt combination.

In that particular situation, one message will generate the greylist
tuple while the other will count as a retry.  As soon as the greylisting
period has expired, one message will generate an autowhite tuple while
the other will get a pass.

The behaviour reported by OP is probably a bug and not even a weird one
since I often get ``X-Greylist: Delayed for 00:00:00 (...)'' for dacl
delayed mails.



   Petar Bogdanovic