-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
EmailPlugin: Allow Email SMTP settings per channel #2043
Comments
This was referenced Feb 21, 2023
martijnvdbrug
changed the title
Allow Email SMTP settings per channel
EmailPlugin: Allow Email SMTP settings per channel
Feb 21, 2023
For future reference @is0utfitters |
Yes this proposal seems reasonable. We would also need to expose an |
Thanks for the response, can you assign this to me? |
This was referenced Feb 27, 2023
This was referenced Apr 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I would like to be able to have different SMTP settings per channel, preferably stored in the database, so that administrators can configure their own mail server.
Describe the solution you'd like
My initial thought is to transform the
transport
property in theEmailPlugin.init()
to a function, so that developers can dictate where SMTP settings are coming from:This way we can, for example, get SMTP config stored on custom fields on a Channel
Describe alternatives you've considered
I am currently using a transactional mail service, that also enables me to send emails from different domains with a single SMTP connection, which works fine, but all channels are forced to use the same transactional email service.
I would like to hear your thoughts on this. Is this something that should be included in Vendure, or is this a use case for a separate plugin?
Additional context
The process function is already async, so it shouldn't be to hard to resolve transport settings here:
vendure/packages/email-plugin/src/email-processor.ts
Line 77 in 7b0fae1
The text was updated successfully, but these errors were encountered: