Milter-greylist

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

No idea?

On 12 janv. 2015, at 07:42, Patrick Proniewski wrote:

> 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

Patrick Proniewski patpro@... [milter-greylist]
<milter-greylist@yahoogroups.com> wrote:

> No idea?

It seems nobody had the same problem, which is kind of weird. 

Data is sent to stat file when a message is accepted, I use that
intensively. Perhaps you will add to add a few printf in the sources and
run milter-greylist in foreground, to check if the stat code path is
actually used when a message is accepted.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

On 22 janv. 2015, at 06:20, manu@... [milter-greylist] <milter-greylist@yahoogroups.com> wrote:

> It seems nobody had the same problem, which is kind of weird. 
> 
> Data is sent to stat file when a message is accepted, I use that
> intensively. Perhaps you will add to add a few printf in the sources and
> run milter-greylist in foreground, to check if the stat code path is
> actually used when a message is accepted.



Not exactly something I can do, as I don't code (ie. I would just break everything and get no result). I'll try ktrace/dtrace instead, more my style ;).

patpro

patpro@... [milter-greylist] <milter-greylist@yahoogroups.com>
wrote:

> Not exactly something I can do, as I don't code 

That is an excellent way to start: add a line:
printf("I am here\n");

rebuild, and run in the forground.
-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...