[Feature Request] Independent SMTP credentials for email aliases

Open
#405 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
backend

Research direction

Start by reading the alias configuration flow and tracing how outgoing mail selects SMTP settings; the issue does not name specific files or tests. Check how account settings and alias settings are stored and used before estimating the change. Done means an alias can use its own SMTP host, port, security settings, username, and password independently of the main account.

Written by the indexing model from the issue text.

Description

enhancement future consideration

Is your feature request related to a problem? Please describe.
In our organization, multiple functional email addresses (e.g., [email protected], [email protected]) 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.

Dominant language
JavaScript
Stars
518
Forks
50
Avg merge
4d 45m
Merged PRs (30d)
43

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from maathimself/mailflow

All issues in maathimself/mailflow

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.