On 02/06/2018 03:48 AM, Sebastian Hagedorn wrote: > > Is it possible that the OutgoingRunner was done with transmitting the > message and had already removed the queue file, but that the connection > hadn't yet been closed?
Only if something went very wrong in SMTPDirect.process() which would have had to return to OutgoingRunner before the .bak would be removed. As I read the code in SMTPDirect.process(), delivery is in a try: ... finally: and the connection is closed in the finally: clause. > Now I wonder the MTA had already closed the connection and Mailman for > some reason didn't notice. Because the Runner was stuck longer than any > timeout on the MTA would permit. But I failed to check that. Should it > hapen again I will have a look on the MTA end. You should be able to see the connect and all that follows in the MTA logs to see if the MTA closed the connection. Anyway, if it did do that while the runner was waiting for response, that should raise socket.error which would be caught and handled. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
