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've been using for years Roundcube with a local Postfix instance on port 25 to send e-mails without authentication. However, with OAuth this no longer works because RC enforces XOAUTH2 auth type plus credentials: indeed, (at least with Postfix 3.7.6 on Debian 12) during the SMTP handshake, no ''250-AUTH" is offered at all, thus the client (Roundcube) bails out. I guess that's correct SMTP behavior before the client issues a STARTTLS, which won't happen because Roundcube is configured with smtp_host = 'localhost:25'.
Thus, I wonder if it could be OK to further extend RC's rcmail_oauth::smtp_connect() to skip authentication when explicitly requested, e.g., with smtp_auth_type = 'NONE', while possibly checking that we're on port 25 and no SSL/TLS was configured for SMTP.
What do you think?
P.S. OAuth + SMTP submission on tls://localhost:587 works as expected.
The text was updated successfully, but these errors were encountered:
I've been using for years Roundcube with a local Postfix instance on port 25 to send e-mails without authentication. However, with OAuth this no longer works because RC enforces XOAUTH2 auth type plus credentials: indeed, (at least with Postfix 3.7.6 on Debian 12) during the SMTP handshake, no ''250-AUTH" is offered at all, thus the client (Roundcube) bails out. I guess that's correct SMTP behavior before the client issues a
STARTTLS
, which won't happen because Roundcube is configured withsmtp_host = 'localhost:25'
.Thus, I wonder if it could be OK to further extend RC's
rcmail_oauth::smtp_connect()
to skip authentication when explicitly requested, e.g., withsmtp_auth_type = 'NONE'
, while possibly checking that we're on port 25 and no SSL/TLS was configured for SMTP.What do you think?
P.S. OAuth + SMTP submission on
tls://localhost:587
works as expected.The text was updated successfully, but these errors were encountered: