On Mon, 23 Jun 2008, Zbigniew Szalbot wrote: > Jun 21 20:02:43 relay postfix/cleanup[39722]: warning: milter > inet:127.0.0.1:4445: can't read SMFIC_BODYEOB reply packet header: Unknown > error: 0 > Jun 21 20:02:43 relay dkim-filter[783]: terminated with signal 11, restarting > Jun 21 20:02:43 relay dkim-filter[39913]: Sendmail DKIM Filter v2.6.0 > starting (args: -l -p inet:[EMAIL PROTECTED] -u mailnull -P > /var/run/milterdkim/pid -x /usr/local/etc/mail/dkim-filter.conf) > > Unfortunately, I no longer have this message. Is there a configuration > setting that would let me know about service restart (by email for example)? > It would make it easier to check for offending message. Thanks!
This is a known problem. I've looked into it with the help of some other list participants, but so far I don't have a solution. Oddly, it only appears on systems where Postfix is the MTA in use. The forensic data I've been shown suggests that something is closing the socket that connects the filter to the MTA improperly, but it's very hard to determine where or how that's happening. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
