-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Multiple SMTP servers #2290
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
Multiple SMTP servers #2290
Conversation
Thanks @lcd1232. This is nice. I'll review and test this in the next couple of weeks and consider it for the upcoming release. This has been a long pending request from many users. |
- Make email messenger accept a name and remove any logic from within it. - Refactor SMTP and and messenger init for consistency. - Refactor app.messengers to be a slice[] and not map to remove superfluous sorting logic. - Refactor SMTP settings and move the new name field to the bottom to not break familiarity. - Refactor campaign form to print email messengers as a sub <optgroup> of the main messenger. - Init all individual e-mail messengers as `email / $name`. - Remove unrelated compose file.
@knadh added some comments. Other than that it looks good |
This patch adds a new optional `name` field to SMTP server config on the UI. When a name is given to an SMTP server, it's initialized as a standalone messenger which shows up as a sub-group item under the main "email" messenger on the campaign page. Co-authored-by: Kailash Nadh <kailash@nadh.in>
This patch adds a new optional `name` field to SMTP server config on the UI. When a name is given to an SMTP server, it's initialized as a standalone messenger which shows up as a sub-group item under the main "email" messenger on the campaign page. Co-authored-by: Kailash Nadh <kailash@nadh.in>
Hi, thanks for this implementation! |
Closes #1703
Screenshots