Anand 6e008bae75 Fix SMTP auth failing with "unencrypted connection" over plaintext ...

net/smtp.PlainAuth refuses to send credentials unless the connection is TLS
or literally "localhost" — a hardcoded stdlib guard, not something the
UseTLS toggle controls. So an admin who deliberately configured a
plaintext relay with a username/password (a trusted internal network) got
every send rejected client-side with "authenticating: unencrypted
connection" before a single byte reached the server, surfacing as a 502
from the test-notification endpoint.

sendPlain now authenticates via a small unencryptedPlainAuth (PLAIN
without the TLS-or-localhost check) instead of smtp.PlainAuth — used only
on the explicitly-no-TLS path; the STARTTLS and implicit-TLS paths keep
the normal stdlib guard. Covered by a new test against an in-process fake
SMTP server that verifies the AUTH PLAIN payload actually reaches the
server over a real, non-localhost loopback connection.

2026-09-03 23:35:40 +05:30

..

notify_test.go

Fix SMTP auth failing with "unencrypted connection" over plaintext

2026-09-03 23:35:40 +05:30

notify.go

Fix SMTP auth failing with "unencrypted connection" over plaintext

2026-09-03 23:35:40 +05:30