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.
indeed outlook.com now also supports this. I'm hoping for this feature on exchange/office365 for years
Todd Goetsch commented
To clarify - My team really likes the ability to add a plus (+) to addresses in other email systems (such as GMail, FastMail, and others). I tried it on Office 365 but it immediately bounced back. Does Office 365 have an alternate option to accomplish the same thing?
I'm referring to this feature:
Denis Plante commented
Yes, Maybe i need to get off Office365 and go to gmail...
this would be awesome, bring it on!
Ian Halliday commented
This would be beyond helpful to us!
Igor Barinov commented
I googled around and it looks like Outlook.com already has this feature, so it's just 365 lagging behind.
Please add RFC 5233 sub-addressing to O365. Gmail has had this feature for ages.
Dai Rees commented
Office 365 (and on-prem Exchange) needs the ability to have "disposable" or "instant" email address aliases, like GMail has.
This is where you can specify an arbitrary "tag" in your email address after your normal alias. So if you have "firstname.lastname@example.org" then you can use "email@example.com" and "firstname.lastname@example.org" to let you give a different address to GameStop and Amazon, which makes it easier to filter their emails, as well as protecting your mailbox from untrusted spammers (especially if you add a fake top-level alias and block all email to that alias).
GMail has supported this feature for over a decade now, it's only fair that Outlook/Office 365/Exchange catch-up, and it's a great weapon in a way against spam and unwanted mail.
As a bonus, please add an optional "message count" feature like SpamGourmet has, where you can limit the number of messages received on a particular disposable alias (e.g. "email@example.com" would be limited to 10 emails before all messages are blocked).
Disposable aliases require an ability to instantly block an alias once spam is detected, but a simple GUI can be used for that.
Disposable aliases could be stored in another list-type property in the Active Directory user object the way current aliases for Exchange are stored, so I don't understand why the Exchange team hasn't built this feature.
Dustin C. commented
I would like this, as well. It would make signing up for various web sites more secure (firstname.lastname@example.org, email@example.com). It lets you immediately know which web site sold your information when you receive spam to one of the aliases.
Ideally, this would be a configurable string in the EOP admin center. I could, for instance, change the "+" to be a string ".at." that would be harder for web sites to automatically filter it out.
enable rfc5233 + Tagging
I took this feature for granted when I decided to use O365. Now my money will regretfully go to someone else instead until this feature has been implemented.
This alone make gmail a better product.
Please add plus addressing it works in others why not office 365?. It is needed in our environment.
Someone Special commented
How does this not work on O365? It's 2016 people, this is a basic part of email and has been for years, many people rely on this.
Because of this bug, I've had to migrate clients to Google Apps (GSuite) instead of Office 365. (Yes it is a bug - the plus symbol is a supported character in an email address.)
Microsoft, can we get an update on when it will be fixed?
Derek D commented
"subaddressing" has been a part (or a valid addressing scheme) of the SMTP Standard (STD10 aka RFC 821/2821/5321) since 1982. RFC 5233 was the addition of it to the SIEVE language.