Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-13 23:57 UTC

Message

wrong delay handling at ACL change

2016-12-18 by Marcus Schopen

Hi,

my standard greylist delay is 15 minutes (ACL name = GL_STD). For hosts 
which are listed on one blacklist, I set a longer delay of 12 hours (ACL 
name = GL_DNSBL). A few days ago a host was greylisted with a longer 
delay, because at first connect its IP was listed on spamcop RBL (= ACL 
GL_DNSBL). After two hours the host was removed from the spamcop list, 
but the greylisting delay didn't change to the standard greylisting 
delay of 15 minutes, but the host had to overcome the full time of 12 
hours delay to its end (GL_DNSBL). I set log ACLs in the greylist.conf 
to see which ALCs were hit after the IP was removed from the blacklist. 
It was die ACL for the standard greylist delay of 15 minutes (GL_STD). 
In my understanding this is wrong. If the short delay ALC GL_STD is hit, 
but the database keeps a longer delay, the delay should be reduced at 
least to the delay time of the shorter delay. But what happens in to 
opposite case? A short delay is hit and counting down. Within this 
timeslot the host is hit by a longer delay ACL? Not sure how to solve 
this case?

Ciao!
Marcus

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.