| Summary: | Request: AUTH LOGIN support | ||
|---|---|---|---|
| Product: | [Applications] trojita | Reporter: | Nicolás Sirolli <nmsirolli> |
| Component: | SMTP | Assignee: | Trojita default assignee <trojita-bugs> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | git | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Bug Depends on: | 321376 | ||
| Bug Blocks: | |||
|
Description
Nicolás Sirolli
2013-06-19 15:44:55 UTC
Sorry for confusion. It seems that "AUTH LOGIN" is a non-standard mechanism which was never standardized -- it certainly is not listed at [1]. I have yet to see an SMTP server which supports AUTH=LOGIN, but does not support AUTH=PLAIN. One common source of troubles is that the cleartext authentication mechanisms like PLAIN and LOGIN are often only enabled after the client has issued STARTTLS, or connected via SSL/TLS. Are you sure this is not the situation you're hitting? Sorry for a late reply. I'm closing this because I believe that support for AUTH LOGIN is in fact not required. Please reopen this report if you disagree. [1] http://www.iana.org/assignments/sasl-mechanisms "Another plaintext mechanism is LOGIN. It's typically used only by SMTP servers to let Outlook clients perform SMTP authentication. Note that LOGIN mechanism is not the same as IMAP's LOGIN command. The LOGIN command is internally handled using PLAIN mechanism." http://wiki2.dovecot.org/Authentication/Mechanisms |