#13142: Add support for SSL connections in core.mail.backends.smtp
---------------------------------+--------------------------------------
     Reporter:  serg.partizan@…  |                    Owner:  jwmayfield
         Type:  New feature      |                   Status:  assigned
    Component:  Core (Mail)      |                  Version:  master
     Severity:  Normal           |               Resolution:
     Keywords:                   |             Triage Stage:  Accepted
    Has patch:  1                |      Needs documentation:  1
  Needs tests:  1                |  Patch needs improvement:  1
Easy pickings:  1                |                    UI/UX:  0
---------------------------------+--------------------------------------
Changes (by jwmayfield):

 * cc: jason@… (added)


Comment:

 https://github.com/django/django/pull/347

 Fixed #13142 -- Added support for SSL connections in
 core.mail.backends.smtp

 Note: SVN-based patch originally provided by serg.partizan / partizan and
 Wojciech Banaś in Trac (refer to
 https://code.djangoproject.com/ticket/13142).  (Patch didn't apply cleanly
 for me.)

 This commit includes the work done by those previous, with the following
 changes:

 * If use_ssl is True, or settings.EMAIL_USE_SSL is True, but the current
 Python version is less than 2.6, use_ssl is not internally changed to
 False. Nor does the SMTP backend code raise an exception. We don't need
 to, because Django 1.5 is dropping support for Python prior to 2.6.

 * This update provides the ability to configure the keyfile and certfile
 to use with SMTP_SSL.

 * Documentation is updated to specify that this feature is new in 1.5.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/13142#comment:15>
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 https://groups.google.com/groups/opt_out.


Reply via email to