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
openssl s_client -crlf -connect imap.yandex.ru:993
* OK Yandex IMAP4rev1 1.0.0 at imap5e.mail.yandex.net:993 ready to talk with 188.244.44.84:47549, 2012-Sep-05 18:35:32, WZVoefPaWeA1
a002 AUTHENTICATE PLAIN
+
dGVzdC11c2VyMDAwMgB0ZXN0LXVzZXIwMDAyQHlhbmRleC5ydQBVbmVUYng4U2E=
a002 BAD command syntax error
a003 AUTHENTICATE PLAIN
+
AHRlc3QtdXNlcjAwMDJAeWFuZGV4LnJ1AFVuZVRieDhTYQ==
a003 OK AUTHENTICATE completed
Authentification success without authzid but not with authzid.
I am test mail client thunderbird, he does not send authzid and auth success.
/* RFC 4616.2. PLAIN SASL Mechanism.
The mechanism consists of a single message, a string of [[Unicode](UTF-8]
encoded) characters, from the client to the server. The
client presents the authorization identity (identity to act as),
followed by a NUL (U+0000) character, followed by the authentication
identity (identity whose password will be used), followed by a NUL
(U+0000) character, followed by the clear-text password. As with
other SASL mechanisms, the client does not provide an authorization
identity when it wishes the server to derive an identity from the
credentials and use that as the authorization identity.
Reported by lefoyer on 5 Sep 2012 15:32 UTC as Trac ticket #1488674
Some servers do not accept authentication with authzid.
Sample problem:
Auth line with authzid:
Auth line without authzid:
Authentification success without authzid but not with authzid.
I am test mail client thunderbird, he does not send authzid and auth success.
/* RFC 4616.2. PLAIN SASL Mechanism.
The mechanism consists of a single message, a string of [[Unicode](UTF-8]
encoded) characters, from the client to the server. The
client presents the authorization identity (identity to act as),
followed by a NUL (U+0000) character, followed by the authentication
identity (identity whose password will be used), followed by a NUL
(U+0000) character, followed by the clear-text password. As with
other SASL mechanisms, the client does not provide an authorization
identity when it wishes the server to derive an identity from the
credentials and use that as the authorization identity.
message = [authzid] UTF8NUL authcid UTF8NUL passwd
Example:
Migrated-From: http://trac.roundcube.net/ticket/1488674
The text was updated successfully, but these errors were encountered: