Hi Jukka, At 03:21 17-01-2008, Jukka Salmi wrote: >Yesterday I saw the problem again, but the order of events was slightly >different: > >- A remote MTA (sf.net) connects to my MTA (mx1). > >- The same remote MTA (sf.net) opens a second connection to mx1 and > tries to deliver a message with the same message id as in the first > (still open) connection.
That shouldn't be a problem as the message-id is considered as a just a string by the milter. >- After 5 minutes (which is my Postfix milter_content_timeout setting) > both connections are rejected: > > postfix/cleanup[6973]: warning: milter inet:localhost:1026: > can't read SMFIC_BODYEOB reply packet header: > Operation timed out Would > postfix/cleanup[6973]: CDE4C24C7D: milter-reject: > END-OF-MESSAGE from [...]: 4.7.1 Service unavailable - [...] > >- Some minutes later another remote MTA (cloud9.net) connects to mx1. > The message is rejected imediately: > > postfix/cleanup[14447]: warning: milter inet:localhost:1026: > can't read SMFIC_BODYEOB reply packet header: Undefined error: 0 Can you enable logging of milter events? Regards, -sm ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
