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 - email - starttls support #1117

Open
r0one opened this issue Jun 4, 2024 · 1 comment
Open

Feature request - email - starttls support #1117

r0one opened this issue Jun 4, 2024 · 1 comment

Comments

@r0one
Copy link

r0one commented Jun 4, 2024

(I would have gladly opened this issue on the gitea instance, but it was down at the moment I checked. Please tell me if you'd prefer me to close it here and reopen it on gitea!)

Is your feature request related to a problem? Please describe.
I cannot plug plume on my mail relay, which has a typical configuration: submission on port 587, with starttls.

Describe the solution you'd like
Implement a new configuration environment variable, and use the object described here. That would add probably 5-10 new loc in mail.rs.

Describe alternatives you've considered
Spin off a local mail relay, that would listen unencrypted on port 25 and relay emails to my provider on port 587. But that would be a ton of new binaries and processes to monitor but solving just one little issue that lettre::transport::smtp handles seamlessly.

@r0one
Copy link
Author

r0one commented Jun 4, 2024

suggested labels: Backend and Feature request.

I do not believe this is "instance specific" - nowadays sending an email is a pain, so it's very common to separate the infrastructure for sending emails, and not to be able to trust the client (because we do not listen on the loopback).

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

No branches or pull requests

1 participant