Is your feature request related to a problem? Please describe.
Yes. Currently, the application relies exclusively on Resend for sending emails. I'm always frustrated when I try to self-host a great open-source project but find myself forced to create an account with a third-party SaaS provider (vendor lock-in) just to get basic transactional emails working. Self-hosters usually prefer keeping their data private and routing emails through their own infrastructure or preferred providers.
Describe the solution you'd like
I would like to see standard SMTP support implemented as an alternative to the Resend API.
The ideal solution would allow users to configure custom SMTP credentials via standard environment variables, such as:
SMTP_HOSTSMTP_PORTSMTP_USERSMTP_PASSWORDSMTP_FROM_EMAILEMAIL_PROVIDER (e.g., set to resend or smtp)
Resend can absolutely remain as the default option for cloud users, but a fallback to classic SMTP is essential for a true self-hosted experience.
Is your feature request related to a problem? Please describe.
Yes. Currently, the application relies exclusively on Resend for sending emails. I'm always frustrated when I try to self-host a great open-source project but find myself forced to create an account with a third-party SaaS provider (vendor lock-in) just to get basic transactional emails working. Self-hosters usually prefer keeping their data private and routing emails through their own infrastructure or preferred providers.
Describe the solution you'd like
I would like to see standard SMTP support implemented as an alternative to the Resend API.
The ideal solution would allow users to configure custom SMTP credentials via standard environment variables, such as:
SMTP_HOSTSMTP_PORTSMTP_USERSMTP_PASSWORDSMTP_FROM_EMAILEMAIL_PROVIDER(e.g., set to resend or smtp)Resend can absolutely remain as the default option for cloud users, but a fallback to classic SMTP is essential for a true self-hosted experience.