mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 00:35:51 +03:00
[GH-ISSUE #231] [FeatureREQ]Multidomain usage #149
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#149
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @plexmaniax on GitHub (Jan 3, 2024).
Original GitHub issue: https://github.com/axllent/mailpit/issues/231
It would be great if mailpit could be used in multidomain context.
We've got an agency server with couple of customers, we would like to provide access to mailpit to all of them, but they should see only the mails which belong to the own domain.
mailpit.domain1.tld
mailpit.domain2.tld
mailpit.domain2.tld
Maybe there is a way with a user management instead of domain managing?
@axllent commented on GitHub (Jan 3, 2024):
@plexmaniax I agree with you in that it would be an awesome feature, however multi-account support / mailboxes is not currently in the planning due to the technical overheads and the fact that Mailpit would need a major rewrite to support this.
The only possible solutions (with Mailpit) would be to run multiple instances of Mailpit on different ports, and then configure each respective website to send mail directly to their respective Mailpit ports - or to separate out your websites into individual self-contained Docker containers (each running their own Mailpit instance). The easiest solution (not using Mailpit) is probably using an off-the-shelf hosted commercial solution such as Mailtrap.
Please refer to #86 & #115 for the same questions & answers.