Milter-greylist

Hi,

Just because you tell Milter-Greylist to delay for thirty seconds, that 
doesn't mean the remote server is going to try again that soon. The 
remote server isn't paying any attention to the tempfail message more 
than likely, so it will try again whenever it sees fit. If the message 
is coming from a domain with multiple Email sending IP addresses, it 
will probably immediately try sending from several more, get a tempfail 
each time, then wait a while and send from one which has by now had its 
greylist delay expire, so the message will be accepted and that 
particular IP address whitelisted.

Hope this helps,

Jayson

On 11/11/2018 2:13 PM, David Woodfall dave@... 
[milter-greylist] wrote:
>
> Hello
>
> I have set greylisting as default with a short delay time:
>
> racl greylist default delay 30s autowhite 60d
>
> But I sometimes see in the logs that it's delaying for much longer:
>
> 2018/11/11 16:50:39 xxxx.org [1.2.3.4]
> address@domain -> me@mine
> accept (ACL 86) Delayed for 00:48:56 by milter-greylist-4.6.2
> (hostname [5.6.7.8]); Sun, 11 Nov 2018 16:50:39 +0000 (GMT)
>
> The email headers show the same thing.
>
> That rule is the only one that has any delay set in it and I have no
> global delay setting (not sure how to use one anyway). Other than
> that I have "broken mta", "local", and "domains" lists whitelisted
> above the greylist rule.
>
> Whenever I test it by sending myself mail it works as expected.
>
> Any idea what may be causing the wrong delays?
>
> TIA
>
> Dave
> --
>
> Nine megs for the secretaries fair,
> Seven megs for the hackers scarce,
> Five megs for the grads in smoky lairs,
> Three megs for system source;
>
> One disk to rule them all,
> One disk to bind them,
> One disk to hold the files
> And in the darkness grind 'em.
>
>