Is your feature request related to a problem? Please describe.
In our organization, multiple functional email addresses (e.g., support@example.org, legal@example.org) are routed to the same mailbox and accessed via a single set of IMAP credentials. However, due to administrative and delivery policies, outgoing emails for these aliases must be sent through distinct SMTP servers (e.g., using Mailjet for support/bulk communication, but an internal secure SMTP server for legal affairs).
Currently, setting up an alias forces the client to use the primary account's SMTP configuration or restricts custom SMTP settings per alias, making it impossible to handle different sending requirements for emails arriving at the same IMAP inbox.
Describe the solution you'd like
Allow users to specify custom SMTP server credentials (hostname, port, security/TLS settings, username, and password) individually when configuring an email alias, independently of the main account's IMAP/SMTP configuration.
Describe alternatives you've considered
What I'm doing currently is, adding aliases as separate accounts with invalid IMAP configurations. That allows me to send with the SMTP configuration, while not recieveing duplicate mails.
Additional context
This feature is useful for multi-domain setup, shared service mailboxes, or instances where transactional email services (like Mailjet, SendGrid, Amazon SES) are used alongside traditional mail servers for different operational functions.
If you think this is feasible, I would be happy to submit a PR to get this done.
Is your feature request related to a problem? Please describe.
In our organization, multiple functional email addresses (e.g.,
support@example.org,legal@example.org) are routed to the same mailbox and accessed via a single set of IMAP credentials. However, due to administrative and delivery policies, outgoing emails for these aliases must be sent through distinct SMTP servers (e.g., using Mailjet for support/bulk communication, but an internal secure SMTP server for legal affairs).Currently, setting up an alias forces the client to use the primary account's SMTP configuration or restricts custom SMTP settings per alias, making it impossible to handle different sending requirements for emails arriving at the same IMAP inbox.
Describe the solution you'd like
Allow users to specify custom SMTP server credentials (hostname, port, security/TLS settings, username, and password) individually when configuring an email alias, independently of the main account's IMAP/SMTP configuration.
Describe alternatives you've considered
What I'm doing currently is, adding aliases as separate accounts with invalid IMAP configurations. That allows me to send with the SMTP configuration, while not recieveing duplicate mails.
Additional context
This feature is useful for multi-domain setup, shared service mailboxes, or instances where transactional email services (like Mailjet, SendGrid, Amazon SES) are used alongside traditional mail servers for different operational functions.
If you think this is feasible, I would be happy to submit a PR to get this done.