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
As a notqmail user, I want to relay mail securely to other hosts. Currently qmail-remote does not support SMTP AUTH at all, but e.g. the smtp-auth branch does. qmail-remote also needs to support TLS to not send the credentials in plain text.
For current best practices, at least PLAIN and LOGIN should be supported.
The text was updated successfully, but these errors were encountered:
I've organized my thoughts about one way qmail-remote could be made to do this. It's the qmail-iest way I can think of so far, and we could merge it (under a temporary new name) in increments until it's ready to replace the original. What do you think?
I am in favor of merging all patches that became synonym of "e-mail" today: the kind of patches that everybody would be applying to get email mostly working.
Net works are moving from trusted LANs to constantly attacked WANs.
Do you (@josuah) mean you’re in favor of e.g. landing TLS in notqmail specifically by merging the popular inoa.net patch, more generally in favor of landing TLS in notqmail one way or another, or...?
As a notqmail user, I want to relay mail securely to other hosts. Currently
qmail-remote
does not support SMTP AUTH at all, but e.g. thesmtp-auth
branch does.qmail-remote
also needs to support TLS to not send the credentials in plain text.For current best practices, at least
PLAIN
andLOGIN
should be supported.The text was updated successfully, but these errors were encountered: