Support for Dynamic '+' Email Aliases in Office 365
I am familiar with using a plus sign following my email alias to create dynamic unique addresses for a Gmail account. e.g. email@example.com will arrive at my Gmail mailbox, where I can then apply rules based on the 'To:' address. See this page for details: https://support.google.com/mail/answer/22370
I tested this on my Office 365 address and it works, but only for email addresses in my parent domain. Using the aliases on subdomain addresses results in a 'recipient not found' NDR.
Does anyone out there have more information on this feature or if it even is one for 365 / Exchange?
We announced at Ignite that we are actively working on bringing dynamic plus aliases to Office 365.
To get around existing usage, the plan is for an opt-in setting. Our ETA is to have this available for all customers by the third quarter of 2020.
I will keep you updated in Uservoice on our progress.
Scott Francis commented
it's not just a genius idea, it's a REQUIREMENT from the relevant RFCs (822, 2822, etc.)
Not supporting "+" in the user-part means an email handling software is in violation of the RFCs that specify the standards that must be adhered to.
[Deleted User] commented
i am sorry but i does not work on Office 365 Business Premium accounts; even with the rule in the mail flow section. maybe I did something wrong.
This workaround doesn't work in my environment. Throws the error:
550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
I suppose it's checking the address existence before checking the mail flow role.
Be able to receive emails to: "FirstPartOfYourMail+ANYTEXT@YourDomain"
Here is how:
- Got to Exchange admin portal
- Go to MailFlow
- Create a rule
With the following settings:
- Apply this rule:
- "When recipient matches: "FirstPartOfYourMail+" <- please note the plus in the end
- and :A recipients domain is "YourDomain"
- Do the following
- redirect messages to "ChooseYourExchangeMailbox" <= you will be able to select them from a list
DO the following
This will only ALLOW YOU TO receive Emails for disposable addresses though while google enabled you to also SEND emails from these addresses as they became a dynamic alias.
That our MAIN concern was to loose emails as we were not able to receive emails from previously setup accounts anymore and it was impossible to run them all down. I hope somebody else that runs into this issue dosen't have to spend weeks to figure this out when the fix is relatively simple.
Should somebody need to send from these emails you will have to add them one by one (this could also be scripted):
- Add Alias for specific email that user wants to send with
- Since the alias contains a "+" we CANNOT use the office admin portal as this wont let us enter "+" as alias, but we HAVE TO to use the Exchange admin portal
- In Exchange admin portal go to Recipients
- Double click on user you wanne add an alias for
- go to email adress tab on user
- now add the new alias (this interface allows us to enter a "+")
- make sure you save after
Does the standard e-mail () notation work in 365? Example:
These are both standards as well as the + notation you're familiar with.
The E-mail standard says that comments can be included by surrounding them in () at the beginning or end of the local part. Example:
- or -
Has anyone tried this with 365?
Jason Reskin, Senior Software Engineer commented
john lumley commented
This would be a very helpful feature to have, that many other providers already use.
Phillip Birk commented
This would be a useful feature for admins who want to configure Moodle to handle inbound forum emails. See https://docs.moodle.org/dev/Inbound_message_API
@Ruben SAADA Can you please add more details how you configured the mail flow rule, there is no "the recipient address matches these templates"option.
We have systems sending out automated emails. The only people not getting them are those with Office 365 eMail addresses.
Ruben SAADA commented
I found a manual solution while waiting for Microsoft to develop the functionality.
You can create a mail flow rule in Exchange with the following options:
If the message ...
the recipient address matches these templates: "^mailnickname\+"
Perform the following operations ...
Redirect the message to "firstname.lastname@example.org"
Received from "Inside the Organization"
The last option is very important because if you do not put it you risk losing emails.
So you will enjoy the same functionality as Gmail except internally.
(The allias + feature will only work if the sender is not part of the company's Microsoft tenant - normally this is not a problem for most of us)
Make me your returns if it suits you!
Briauna Gardner commented
This is a great topic and I think it should be widely considered. But check out the newest idea and see what you think!
Chris Smith commented
If I am ever going to stop having to hear my co-workers talk about how GMAIL is Better than O365, then MSFT needs to get with the program!!
also waiting for this to be added. +1000000000
Lucas Wood commented
Me and all my email aliases vote for this.
Josh Davidson commented
As a developer we made heavy use of this feature in GSuite before moving over to O365. It allowed us to create disposable accounts for testing purposes. We're kind of stuck now with creating a bunch of manual of aliases.
Still cannot believe Office 365 doesn't support RFC 5233 subaddressing. Outlook.com does it well. As does Gmail. This is a pretty widely used feature, so please make it happen Microsoft!
Andy Appel commented
Most of my coworkers are still using their personnel gmail accounts because of this feature.