Follow up to the thread JMAP Identity/set rejects mailing list address that SMTP submission accepts - #5 by stalwart, where staff asked for a feature request.
Use case 1: “Send As” on a distribution list (Exchange-style)
A company runs [email protected] as a distribution list. Every member of the sales team gets their own copy of each inquiry in their personal inbox, so each person works from their own mailbox, with their own flags, folders and rules. A group with one shared mailbox doesn’t fit this workflow.
When a team member answers an inquiry, the reply has to come from [email protected], not from their personal address. Customers should keep writing to the team, and personal addresses shouldn’t leak. In Exchange/Microsoft 365 this is the standard setup: a distribution group, with “Send As” granted to selected members.
In Stalwart this already works over SMTP submission, through a mustMatchSender rule. In a JMAP client, creating an identity for [email protected] fails with “E-mail address not configured for this account.”, so webmail users can’t reply as the team. The only workaround (overriding the From header) leaves the member’s personal address in the envelope sender and Return-Path.
Use case 2: sub-addresses that should not reveal the main address
Employees hand out per-purpose sub-addresses instead of their main address, for example [email protected] for supplier contacts, or a separate address per vendor portal or newsletter. Mail to these addresses is delivered to Jane’s mailbox. The point of the sub-address is that the other side never learns Jane’s main address. If a sub-address starts receiving spam or gets passed on, it can simply be blocked without touching her main address.
Over SMTP submission Jane can reply from the sub-address. In a JMAP client she can’t: no identity can be created for it, so her reply goes out from [email protected]. The main address that the sub-address was meant to protect is then disclosed to exactly the party it was hidden from. The From-override workaround doesn’t help either, because the envelope sender and Return-Path still carry the main address.
Request
Let JMAP identities cover the addresses a user is already allowed to send as. Possible ways (your call):
Identity/setevaluates the same sender rule as SMTP submission (mustMatchSender), so both protocols agree.- A per-list setting such as “members may send as this address”, added to the members’ allowed identity addresses.
- Sub-addresses that resolve to an account allowed as identities for that account.
This grants no new rights. It only makes over JMAP what SMTP already permits, and the default behaviour stays unchanged.