-
-
Notifications
You must be signed in to change notification settings - Fork 818
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EHLO after AUTH causes send failure with 5.7.0 even though authentication succeeded #162
Comments
Can you please report this bug to Strato? Clients are supposed to send EHLO after authenticating. The reason the RFC says SHOULD and not MUST is because it depends on whether or not the client uses extensions. If the client doesn't use extensions, then obviously it doesn't need to re-fetch them. Otherwise it needs to. |
I tried, but they don't give a **** about standard compliance and they're big enough to get away with it 😞 . They don't even provide E-Mail support for non-customers... |
I've committed a different workaround. I'd rather not introduce public APIs to work around broken servers. |
Thank you 👍 |
smtp.dm.aliyun.com has the same problem. |
I've released MailKit 1.4.1 with a fix for this to nuget.org |
@jstedfast Can you please point me to RFC? I have found only https://tools.ietf.org/html/rfc4954 which states that there should be additional EHLO only after TLS negotiation. (ref https://bitbucket.org/analogic/mailserver/issues/183/mailkit-cant-authenticate-in-posteio) |
It doesn't say anything about TLS negotiation, it says after any security layer has been obtained. SASL stands for Simple Authentication and Security Layer. |
That said, rfc4616 does state: |
Thanks! |
Thank you |
FWIW, MailKit 1.14.1 fixes this. |
I've found a problem with an E-Mail provider (Strato) that causes a 5.7.0 error after a successful authentication (2.7.0) due to the sent EHLO after the authentication.
The text was updated successfully, but these errors were encountered: