Hello Manu et al, Today I've caught a crash of milter-greylist, here are some details. The last entries in log were: Aug 12 16:16:23 ucs milter-greylist: [ID 471652 mail.debug] Incoming connection from host 'tcp-daemon.imap.ucs.domain.ru' Aug 12 16:16:23 ucs milter-greylist: [ID 447650 mail.error] unexpected AF The "host name" is a Messaging Server queue name with the trailing name of the local MTA host. This string is not resolvable to an IP address via DNS or local /etc/hosts (as of yet, at least). The "unexpected AF" leads me (in source) to 380:p0f.c function p0f_lookup() - here it tries to interpret priv->priv_addr, gets to default (not AF_INET nor AF_INET6) and falls out. I am not sure if these two clues are hard-linked, or if the queue handler does not set some macros that are present during a live SMTP dialog with a remote host. Still, I wonder if "localaddr" should come into play as a fallback here as well? My workaround for now would be to disable p0f in config, and later to disable milter-greylist for internal server processing - can't find where it gets called here, and have more urgent quests now... Ideas welcome, though... Thanks, //Jim Klimov
Message
Crash in p0f handler
2013-08-12 by Jim Klimov
Attachments
- No local attachments were found for this message.