On Thu 23/Aug/2012 07:05:27 +0200 Lindsay Haisley wrote: > On Wed, 2012-08-22 at 20:08 -0400, Sam Varshavchik wrote: >> So, with the sender doesn't really have a way of knowing what happened, the >> sender will rightfully assume – and it would be the correct choice – that >> it failed, and will try again later. >> >> If this is a one-off situation, then I would also write it off as a one-off; >> >> although it would be very unusual to have this happen on a LAN. > > The connection between the MUA and the MTA isn't via a LAN, even though > it's between interfaces with RFC1918 addresses. They're connected via a > VPN with Time Warner between them. Courier truncated the log entry for > the 450 error so I don't know why _that_ SMTP session failed, and it > didn't send a DSN/NDR to me with the full text of the error. So all of > this may remain a mystery.
Why that transaction failed is a curiosity, but not what you're after. You should search the courier logs of that day for the failed message id, 000000000027586D.0000000050318EDD.00006F31. Courier must have logged that it received the message from the MUA, on Sun, 19 Aug 2012 20:11:57. As Sam said, the network error must have happened then. The truncated 450 error was logged nine seconds later, at 20:12:06. HTH -- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
