Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] Strange delay times

2018-11-11 by Jayson Smith

Hi,

I assume what's happening is that Milter-Greylist is logging how long 
the message was actually delayed, based on not only the rule you have 
set up, but also how long it took for the remote server to retry. I 
assume if the remote server waited exactly thirty seconds from the first 
tempfail to retry from the same IP, the message would be accepted, and 
delayed for thirty seconds just like you have set up. But the remote 
server almost certainly waited longer, possibly much longer, so 
Milter-Greylist is just logging how long the message sat in the remote 
server's outgoing mail queue before it tried again.

Jayson

On 11/11/2018 2:46 PM, David Woodfall dave@... 
[milter-greylist] wrote:
>
> Right, I assumed that is the case, but I still don't see why
> Milter-Greylist is using a delay other than what I set it to.
>
> On Sunday 11 November 2018 14:37,
> Jayson Smith <milter-greylist@yahoogroups.com> put forth the proposition:
> > 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.
> > >
> > >
> >
> >
>
> --
>
> "MacDonald has the gift on compressing the largest amount of words into
> the smallest amount of thoughts."
> -- Winston Churchill
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.