You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect that when an SSL/TLS connection is used instead of STARTTLS (and auth_require_tls is true), AUTH is provided to the client. Currently, we are setting auth_require_tls is false to circumvent this issue.
The text was updated successfully, but these errors were encountered:
Sadly, I don't think* there's an efficient way for SMTP to detect if it's being wrapped externally in an SSL/TLS context.
For the time being I think the easiest workaround is to add a note to the documentation w.r.t. needing to set auth_require_tls=False when using implicit SSL/TLS.
I may change my mind, though. Let me refresh my understanding of the code first ... it's been quite awhile 😅
@FinnStutzenstein in fact not only was AUTH not present in response, but was also explicitly rejected when attempted without feature checking.
But hopefully it will be merged and fixed soon.
When using implicit SSL/TLS (so no STARTTLS), the
self._tls_protocol
will never be set. This results inAUTH
not being present in the EHLO response (given thatauth_require_tls
is true): https://github.com/aio-libs/aiosmtpd/blob/master/aiosmtpd/smtp.py#L833I would expect that when an SSL/TLS connection is used instead of STARTTLS (and
auth_require_tls
is true),AUTH
is provided to the client. Currently, we are settingauth_require_tls
is false to circumvent this issue.The text was updated successfully, but these errors were encountered: