Support for Dynamic '+' Email Aliases in Office 365
Hello,
I am familiar with using a plus sign following my email alias to create dynamic unique addresses for a Gmail account. e.g. test.email+signedup@gmail.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?
Thanks!
Ryan
Ryan Kendall
shared this idea
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.
158 comments
-
Alex Filatov
commented
This email alias feature would be a great addition to outlook. Similar feature exists in other email providers that allow for a suffix to be added to the username part of email with a + plus sign.
-
Bradley
commented
What the heck man? This solves a huge problem for me and most (including outlook.com!) support this except for O365... Come on!
-
Anonymous
commented
I have a developer who would like to create a "plussed" email address. For example , he had a address called something like dev@outlook.com. He could create dynamic email address dev+Newuser@outlook.com or dev+technicalsupport@outlook.com without creating aliases for the new name. It was all dynamic. We would like to be able to do this for our Office365 email domains.
-
Anonymous
commented
When are we going to get this feature in Office 365?
-
martin petz
commented
this is a major issue for us - we use dynamic aliases for available job positions in our hr software (e.g. jobs+developer@...)
right now the inability to use these aliases blocks me from switching the company over from google to office365.
please fix asap. this is basic e-mail functionality in this day and age that anyone can build with a run of the mill postfix server in 5 minutes.
-
Erlend Sogge Heggen
commented
Discourse, just like many other forums, support desks, issue trackers, newsletters and other SAAS services rely on this convention to support reply-by-mail functionality. Those of our users with Office 365 are severely inconvenienced by the lack of this feature in your email client.
In the meantime, here's the workaround we currently recommend for Discourse. Similar solutions could be applicable to other services as well:
"I recommend routing all mail destined for your Discourse instance via a separate domain, that you can point to something that is more standards-friendly. For replies and from addresses, all you need to do is change the site config to use "{foo}@discoursemail.com" (with appropriate +%{reply_key} as appropriate) and we'll do the rest. If you'll be using per-category incoming addresses (to allow people to create new topics via e-mail, to more completely simulate a regular mailman-style mailing list), we can setup support for incoming e-mail sent to either "something@{foo}.discoursemail.com" or "something@community.{foo}.org" (or both!)."
-
Krzysztof Wolny
commented
It would be nice to dynamically create email aliases, using e.g. "+" (like in GMail) so if my account is user@domain.com then any email sent to user+somestring@domain.com will be delivered to my inbox, without any additional setup.
This will allow to use different email addresses in different sites, etc.
-
Bee Dee
commented
Plain hotmail-a-la-outlook.com seems to support subaddressing.
Found a reference here: http://www.ghacks.net/2013/09/17/can-now-use-email-aliases-outlook-com/ (or somewhere), and tested recently with a public @outlook.com mailbox. (Can't find any Microsoft references to it)
Us poor Office 365 users need this as well...
-
Benjamin
commented
Oh dears, yes, please make this dream come true.
Here's one use case: for each of our customers, we have to register to some external services, using a different email address every time. So now, we have to create a distribution list manually for each, redirecting to some email accounts. Instead, we want to have ONE distribution list (say, registrationstuff@contonso.com), and use aliases of this one for each registration (registrationstuff+customer1@contonso.com, registrationstuff+customer2@contonso.com, etc.).
No extra manual work anymore!Gmail does it, Postifx does it, Qmail does it, iCloud does it, Yahoo does it, and even Outlook.com does it!
Only Exchange/Office365 doesn't do it yet. -
Nicholas
commented
You should be able to tag emails so that they file into a folder/sub folder automatically.
Maybe in the send you put #Other then all communications will go to that folder.
-
Anonymous
commented
+1
-
Mike Davis
commented
-
Tomas Dostal
commented
Why is everyone from MS avoiding this issue? Whatever link I dig up about this has no reaction from MS..
This is also blocking our project as we want to implement a solution around having dynamic part of email address (not pre-defined), but cannot do it with current MS mailbox...
-
Mikael Puittinen
commented
Many email services (e.g Google) support subaddressing, i.e emails of format user+modifier@domain.com (emails are routed to user@domain.com) as decribed in RFC5233.
To allow seamless migration from one of those providers to O365, add support for that into O365. -
Greg
commented
This is preventing my company from migrating over from another service as we have many existing email addresses out there using these subaddress formats and moving to Office 365 would cause all these to become undeliverable. Please add this feature ASAP.
-
Michael Jephcote
commented
This is a must, I can't believe it isn't added when the feature has been around for 7 years or more! https://tools.ietf.org/html/rfc5233#section-4
-
Robert van der Linde
commented
By enabling sub-addressing (someuser+randomtext@domain.com) you'll give your customers a lot more options to distinguish emails. As well as allow businesses to integrate software that uses this method to fulfill specific functions with the online exchange environment.
-
Adrian Santangelo
commented
Google Apps allows instant creation of an email alias using the "+" feature, for example username+whatever _AT_ domain.com (replace _AT_ with email symbol - don't want to get stuck into a spam filter.) More info here: http://fieldguide.gizmodo.com/how-to-use-the-infinite-number-of-email-addresses-gmail-1609458192
The bigger issue isn't that we can't do that here (as I have users that are quite used to it), but that I can't even CREATE the existing ones. This makes it extremely hard to migration users away from Google Apps since I can't recreate their existing aliases they are already using. Now, I have to have them change every single email address they are using, say to use an underscore instead, then create all of those aliases within the portal. This is an unreal request when trying to sell people on the merits of switching, as the SERVICE is much better, just not the implementation in parts.