Hello, At 03:46 23-06-2008, Zbigniew Szalbot wrote: > From time to time dkim seems to restart itself because it chokes on > some messages. > >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)
This looks like the same problem which Jukka reported some time back. It's not a dkim-milter problem as such. It may be something in the milter library or in the Postfix implementation. Murray posted an analysis of the problem. I don't recall the exact details. The issue has not be resolved yet. >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! No but as you can see above, a message is logged when the milter is restarted. During testing, we established that it was not a particular message causing the problem. There was a patch posted for the milter library to gather more information about the sequence of events that leads to this condition. Regards, -sm ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
