On 21/08/2012 2:34 PM, Lindsay Haisley wrote: > Sam, et al, > > Here's a situation that happened recently. I posted to a popular > mailing list and courieresmtp logged the following. > > Aug 19 20:12:06 shakti courieresmtp: > id=000000000027586D.0000000050318EDD.00006F31,from=<fmouse-mail...@fmp.com>,addr=<mailman-us...@python.org>: > 450-4.3.2 Service currently unavailable > Aug 19 20:12:06 shakti courieresmtp: > id=000000000027586D.0000000050318EDD.00006F31,from=<fmouse-mail...@fmp.com>,addr=<mailman-us...@python.org>: > 450 4.3.2 Contact your postmaster/admin for assistance. Please provide the > following information in your problem report: time (A... > Aug 19 20:12:06 shakti courieresmtp: > id=000000000027586D.0000000050318EDD.00006F31,from=<fmouse-mail...@fmp.com>,addr=<mailman-us...@python.org>,status: > deferred > > The connecting server at python.org returned a temporary error. > Apparently Courier queued this email for redelivery, and the MUA > (Evolution) noted the failure and apparently left the problem email in > my Outbox. A minute later, the MUA tried again, successfully: > > Aug 19 20:13:10 shakti courieresmtp: > id=00000000002758BD.0000000050318F21.00006FAC,from=<fmouse-mail...@fmp.com>,addr=<mailman-us...@python.org>: > 250 2.0.0 Ok: queued as 3X0cTL2xBFzQM6 > Aug 19 20:13:10 shakti courieresmtp: > id=00000000002758BD.0000000050318F21.00006FAC,from=<fmouse-mail...@fmp.com>,addr=<mailman-us...@python.org>,size=4147,success: > delivered: mail.python.org [82.94.164.166] > Aug 19 20:13:10 shakti courieresmtp: > id=00000000002758BD.0000000050318F21.00006FAC,from=<fmouse-mail...@fmp.com>,addr=<mailman-us...@python.org>,size=4147,status: > success > > Note the different Message ID. > > Five minutes later, Courier tried, again successfully, to deliver _its_ > queued copy of the message. Note that the Message ID is identical to > that of the original deferred post. > > Aug 19 20:17:08 shakti courieresmtp: > id=000000000027586D.0000000050318EDD.00006F31,from=<fmouse-mail...@fmp.com>,addr=<mailman-us...@python.org>: > 250 2.0.0 Ok: queued as 3X0cYw1CRlzQ6g > Aug 19 20:17:08 shakti courieresmtp: > id=000000000027586D.0000000050318EDD.00006F31,from=<fmouse-mail...@fmp.com>,addr=<mailman-us...@python.org>,size=4147,success: > delivered: mail.python.org [82.94.164.166] > Aug 19 20:17:08 shakti courieresmtp: > id=000000000027586D.0000000050318EDD.00006F31,from=<fmouse-mail...@fmp.com>,addr=<mailman-us...@python.org>,size=4147,status: > success > > The end result was that although I only posted once, two copies of my > post were delivered to the list, and to all list subscribers. > > I've had some discussion with two of the primary developers of the > Mailman list server package, Mark Sapiro and Brad Knowles. Mark replied > as follows below. "shakti" is running Courier 0.64.0: > > <snip> > > My question is this. If a receiving SMTP server returns a temporary > failure, what should Courier's response be? Should it assume that the > requesting MUA will queue the post and retry, or should it return > success to the MUA and retry from its own queue. Neither alternative > seems to be satisfactory. Is the MUA at fault here for queuing the > message and retrying? This doesn't seem logical. > > What's the fix? > Hi Lindsay,
Courier has done the right thing with a 450 error - it's tried again. Evolution should have received the notification that the message has been successfully received by 'shatki' and therefore moved it off to the Sent Items instead of leaving it in the Outbox. I'm running Debian Sid on my SMTP server, and it's got Courier 0.68.2-1, which suggests that 0.64.0 is rather out of date, and there might have been a bug in it which caused it to both pass back the 450 error to the MUA as well as re-queuing it for another delivery attempt - Sam would be able to confirm if that's the case. Either way, I would suggest you look at upgrading from 0.64.0 to a more recent release and see if the problem persists. Regards, Tim Lyth ------------------------------------------------------------------------------ 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
