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
Currently all mails are sent out via courier and, as far as I could find, courier only supports smtp/smtps.
For normal email sending most mail providers like sendinblue/sendgrid still provide an smtp interface, however the preferred way is via their api.
Using their api would allow also us to use more advanced features like transaction email templates.
Our usecase would be sending all emails via sendinblue so we can use their transactional mail templates (which can be edited/maintained by non-developers)
Describe your ideal solution
It seems #1941 already lays the foundation, but only applies for sending sms.
This would need to be extended to also allow sending mails via an api.
add support for http/https protocol in courier.smtp.connection_uri
add courier.smtp.request_config (similar to courier.sms.request_config)
^ although it might better to rename courier.smtp to courier.mail or introduce a new courier.api option
Workarounds or alternatives
It might be possible to use webhooks for this, but that would require a whole lot of extra configuration per flow + would not be as robust.
Version
0.8
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight checklist
Describe your problem
Currently all mails are sent out via courier and, as far as I could find, courier only supports smtp/smtps.
For normal email sending most mail providers like sendinblue/sendgrid still provide an smtp interface, however the preferred way is via their api.
Using their api would allow also us to use more advanced features like transaction email templates.
Our usecase would be sending all emails via sendinblue so we can use their transactional mail templates (which can be edited/maintained by non-developers)
Describe your ideal solution
It seems #1941 already lays the foundation, but only applies for sending sms.
This would need to be extended to also allow sending mails via an api.
courier.smtp.connection_uri
courier.smtp.request_config
(similar tocourier.sms.request_config
)^ although it might better to rename
courier.smtp
tocourier.mail
or introduce a newcourier.api
optionWorkarounds or alternatives
It might be possible to use webhooks for this, but that would require a whole lot of extra configuration per flow + would not be as robust.
Version
0.8
Additional Context
No response
The text was updated successfully, but these errors were encountered: