[issue8245] email examples don't actually work (SMTP.connect is not called)

Sandro Tosi added the comment: This has already been fixed in issue11883 changing the SMTP constructor call. -- nosy: +sandro.tosi resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> Call connect() before sending an email with smtplib versions:

[issue8245] email examples don't actually work (SMTP.connect is not called)

Changes by Georg Brandl : -- assignee: georg.brandl -> asmodai nosy: +asmodai ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8245] email examples don't actually work (SMTP.connect is not called)

Jason R. Coombs added the comment: Matt, I hope you don't mind, but I added you as nosy on this issue as it relates to a change you suggested. -- nosy: +matt ___ Python tracker

[issue8245] email examples don't actually work (SMTP.connect is not called)

Jason R. Coombs added the comment: According to issue4239#msg75355, the connect call is not required, but I believe he is mistaken. The connect call is required unless the s object is constructed with host/port parameters, in which case the call to connect (without any parameters) will result

[issue8245] email examples don't actually work (SMTP.connect is not called)

Jason R. Coombs added the comment: It appears in r71882, the change was made in deference to issue4239. -- ___ Python tracker ___ ___

[issue8245] email examples don't actually work (SMTP.connect is not called)

New submission from Jason R. Coombs : Documentation for Python 2.6.5 and 3.1.2 both describe using the smtplib as so: s = smtplib.SMTP() s.sendmail(me, [you], msg.as_string()) s.quit() However, this sample usage is incorrect and doesn't work in practice, because s.connect() is neve