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. firstname.lastname@example.org 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?
I’m pleased to announce that the plus addressing feature is now available for Exchange Admins to enable. This can be done through Powershell using the following command:
Set-OrganizationConfig -AllowPlusAddressInRecipients $true
For instructions on how to use Powershell, you can find out more here:
The setting may not instantly take effect so please expect a delay before you can start using plus addresses.
The Exchange Transport team
I would also like to have this to sort mails in receipts using a forward triggered by having a invoice+ in front of my usual mailaddress.
quite easy, add this in the normal rules, do we have a matching local part, no, ok, cut on + do we have a matching now? Oh goodie!
Another issue is to get outlook to show the address an email was addressed to, _not_ which mailbox recived it.
Keep in mind, O Implementers, that it doesn't have to be a plus. Several other email system support the concept other than Gmail, but in some cases just use a different character for the functionality. From the RFCs there are some good options:
RFC 2822 defines these characters as special: "()<>:;@\,." and the double quote, making them useless for the "+suffix" idea.
However, the RFC also defines a mailbox as having a phrase part for the local box built out of words, built out of atoms, which in section 3.2.4 are built from atexts which allow a fairly wide set of characters include the semantically suggestive "+", "/" and "=", and 3.2.5 suggests that quoting might not be required for mailboxes containing such characters.
"+" would be ideal, but if "+" is an issue, what about "/" or "=" ? <joe.smith/forspam123> or <amy.forster=junkbox345> both seem pretty obvious. See the RFC for more options.
Old email servers shouldn't have issues, since RFC 822 defines an atom as:
"*<any CHAR except specials, SPACE and CTLs>", and those three chars aren't in RFC 822 3.3: specials.
The fact that outlook does not support something that has been available with most e-mail systems for at least 15+ years is rather depressing. I hope my organization is paying lots less for the downgrade in service we got by switching to Office365....
Kirk Gleason commented
I would use all 10 votes on this, if I could.
Please for the love of god and all that is holy add this feature ASAP.. Lagging so far behind other providers and trying to re-invent the wheel with O365 is going to cause you to lose even more of the market...
This is a requirement - please add.
Billy Purdue commented
Seems silly Outlook.com has had this for half a decade and Office 365 doesn't have it in Exchange yet.
Seconding Brian's comment - This is a must have for us to support software development, testing, employee alpha and beta testing, and general good security practices. I would love to understand why it has not yet been prioritized and what may be blocking it.
This request is climbing the ladder. To help the MS folks understand this, here are some references for the functionality:
- Wikipedia SMTP Subaddressing: https://en.wikipedia.org/wiki/Email_address#Subaddressing
- RFC 5233: https://tools.ietf.org/html/rfc5233
Come on guys. I’m trying to sell this to 1000’s of google users and it all falls down here.
For people who don't understand this, it allows you to use versions of your email for specific things...
Whatever. If you're signing up for a conference, you could use..
Then anytime you received an email at that address, you'd know exactly where it came from.
Now you know. It's great for testing, and all kinds of little things. This would be a great addition.
This would be great. I'm starting to use it more and more since I found out my GMail had it. I didn't even know that my Outlook.com email would work with it also.
A Ghacks article proves that this feature has been available on Outlook.com since 2013. Since Outlook.com has been using a version of Office 365 for a couple years now, how is it possible that full-blown Office 365 doesn't have this? It's a superset of Outlook.com! So it must have been a deliberate choice.
Chris Van Vorous commented
this is so frustrating. i'm guessing the o365 team doesn't understand how hard it is to pitch migration from gsuite when so many tools are relying on dynamic addresses for functionality.
This is a must have for us to support software development, testing, employee alpha and beta testing, and general good security practices. I would love to understand why it has not yet been prioritized and what may be blocking it.
Not even "Thinking about it"? Bad form! Add this to the roadmap asap