Send another EHLO after starting TLS, as suggested by RFC 2487.

I might argue this is a bug in smtplib; RFC 2487 says that the client
"MUST discard any knowledge obtained from the server, such as the list
of SMTP service extensions, which was not obtained from the TLS
negotiation itself"
 - Legacy-Id: 958

Author: fenner

ietf/utils/mail.py

@@ -45,6 +45,9 @@ def send_smtp(msg):
 	    (retval, retmsg) = server.starttls()
 	    if retval != 220:
 		raise ImproperlyConfigured('password configured but tls failed: %d %s' % ( retval, retmsg ))
+	    # Send a new EHLO, since without TLS the server might not
+	    # advertise the AUTH capability.
+	    server.ehlo()
 	    server.login(settings.EMAIL_HOST_USER, settings.EMAIL_HOST_PASSWORD)
 	server.sendmail(frm, to, msg.as_string())
 	# note: should pay attention to the return code, as it may