#17471: Add ability to use smtplib.SMTP_SSL connection when sending email
-----------------------------+--------------------------------------
Reporter: dje | Owner: nobody
Type: Bug | Status: new
Component: Core (Mail) | Version: 1.3
Severity: Normal | Resolution:
Keywords: smtp | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by dje):
* cc: dj.facebook@… (added)
* has_patch: 1 => 0
* type: New feature => Bug
Comment:
So I've spent a while reading through the RFC specs on TLSv1 and
discussing with the developers of a few of the providers I was having
issues with and it turns out that this is actually a *bug* and not a new
feature. TLSv1 has two operational modes: explicit and implicit when
forming the connection/handshake. Django incorrectly assumes that all TLS
connections are explicit connections. Explicit connections use STARTTLS
and are generally accepted on port 587. Implicit connections (which may
also fall back to SSL) are typically made over port 465 and should not use
the STARTTLS command.
I'm changing this back to a bug as it is a misinterpretation of the spec
and only half implemented.
--
Ticket URL: <https://code.djangoproject.com/ticket/17471#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
