Yahoo Groups archive

Milter-greylist

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

Message

integration with postfix: trouble with log/reporting

2015-01-12 by Patrick Proniewski

Hello,

I'm using milter-greylist for some time now. It runs on 3 FreeBSD 9.x servers with Amavisd-new as a before queue content filter (ie. Postfix in Proxy).
This setting prevent milter-greylist from accessing headers and content of email messages. Hence, it can't add the X-Greylist header when the message is passing through.

I need to get some info about the way milter-greylist is delaying messages. Unfortunately I'm unable to retrieve this info.

My configuration is looking like this:

-------------------
pidfile "/var/run/milter-greylist.pid"
socket "/var/milter-greylist/milter-greylist.sock" 660 
dumpfile "/var/milter-greylist/greylist.db" 600
dumpfreq 1
user "mailnull:mail"
geoipdb "/usr/local/share/GeoIP/GeoIP.dat"
stat ">>/var/milter-greylist/greylist.log" \
     "%T{%Y/%m/%d %T} %d [%i] %r -> %f %S (ACL %A) %Xc %Xe %Xm %Xh\n"

verbose
quiet

list "my network" addr { ... }
list "broken mta" addr { ... }
list "whitelist domain" domain { ... }
list "grey users" rcpt { ... }

racl whitelist list "my network"
racl whitelist list "broken mta"
racl whitelist list "whitelist domain"

racl greylist default delay 2m autowhite 15d
-------------------

First time a new message comes in, I have proper notification in logs (postfix logs, milter-greylist logs, debug.log thanks to "verbose", and special "stat" log file):
"bypassing greylist", "autowhitelisted for another 360:00:00", "delayed for 00:02:00", and so on.

But when the message comes back later and is accepted, milter-greylist fails logging any info. It's just mute, and I don't know how long the message was really delayed.

Any idea?
thanks,

patpro

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.