Lena wrote: > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > > http://bugs.exim.org/show_bug.cgi?id=893 > Summary: Not enough info in DSN ('retry timeout exceeded') > Product: Exim > Version: 4.68 > Platform: All > OS/Version: All > Status: NEW > Severity: wishlist > Priority: low > Component: Delivery in general > AssignedTo: [email protected] > ReportedBy: [email protected] > CC: [email protected] > > > I haven't access to the log of my ISP's relay (Exim 4.68). All I get from it > is > DSN ("Subject: Mail delivery failed: returning message to sender"). Sometimes > it says: "retry timeout exceeded". But why the message was deferred? An > example > of the log excerpt from another bug report: > > mainlog:2007-02-06 11:15:09 1HEVjT-0003wA-NJ > inbound.hughes.net.cust.securehostedemail.com [64.97.131.1] Connection timed > out > mainlog:2007-02-06 11:15:09 1HEVjT-0003wA-NJ == [email protected] R=lookuphost > T=remote_smtp defer (110): Connection timed out > mainlog:2007-02-06 11:15:09 1HEVjT-0003wA-NJ ** [email protected]: retry timeout > exceeded > > The DSN should include the for example "Connection timed out" from the last > retry attempt in addition to the "retry timeout exceeded". > >
AFAIK, these are events that *may* be more widely separated in time and causality than the same-second timestamp (above), ergo perhaps a 'non-trivial' exercise to associate. grep '1HEVjT-0003wA-NJ' ~/exim/mainlog .. clearly associates the history, even if other entries were to be interspersed, does it not? JM2CW Bill Hacker -- ## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
