Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: TLS and SMTP AUTH support in qmail-remote #174

Open
leahneukirchen opened this issue Aug 3, 2020 · 3 comments
Open

Feature request: TLS and SMTP AUTH support in qmail-remote #174

leahneukirchen opened this issue Aug 3, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@leahneukirchen
Copy link
Contributor

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.

@schmonz
Copy link
Member

schmonz commented Nov 20, 2020

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?

@josuah
Copy link

josuah commented Nov 27, 2020

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.

@schmonz
Copy link
Member

schmonz commented Dec 1, 2020

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...?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants