This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gac
Recipients gac
Date 2013-01-10.12:41:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357821708.32.0.469925509105.issue16914@psf.upfronthosting.co.za>
In-reply-to
Content
I had cause to use smtplib to help me pinpoint why some outgoing mail was failing, but found that while it offered verbose logging (via debuglevel 1) this was without timestamps, making it difficult to make my case to the server operator that it was a server-side delay causing the issue. I've changed smtplib.py to add a second debugging level which includes timestamps down to microsecond granularity so that the debug log produced can pinpoint when a server isn't responding promptly.

debuglevel 1 is unchanged, so anyone depending on the output from this being in a particular format won't be affected (either by setting debuglevel to "1" or "true"), but if debuglevel 2 is used explicitly then the standard output is preceded by a timestamp.
History
Date User Action Args
2013-01-10 12:41:48gacsetrecipients: + gac
2013-01-10 12:41:48gacsetmessageid: <1357821708.32.0.469925509105.issue16914@psf.upfronthosting.co.za>
2013-01-10 12:41:47gaclinkissue16914 messages
2013-01-10 12:41:46gaccreate