Feedback by UserVoice

How can we improve the tenant admin features O365?

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

1,548 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ryan Kendall shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    39 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Nick commented  ·   ·  Flag as inappropriate

        please fix this issue so we can start using dynamic email address with a third party tool like activeCollab.

        Thanks,
        Nick

      • Anonymous commented  ·   ·  Flag as inappropriate

        please fix this issue so we can start using dynamic email address with a third party tool like activeCollab.

        Thanks
        Roger

      • Anonymous commented  ·   ·  Flag as inappropriate

        This breaks email as a standard. It is a requirement of the email RFCs. Please fix!

      • Anonymous commented  ·   ·  Flag as inappropriate

        This is totally unacceptable. Sadly, our alumni association decided they didn't want to pay in-house services anymore/and or in-house did not want to deal with us so we were forcefully migrated to O365. Now what am I supposed to do with all of the e-mail addresses that have been out in the wild? I don't even know what all of them are. In most cases it fails silently to the sender as well as the recipient, to make the problem even worse!

      • IT commented  ·   ·  Flag as inappropriate

        That is not even a feature, it's a RFC compliance bug. MS somehow has plenty of dev time to add gizmos and promoted products but not for bugfixes to core features.

      • Tim Phang commented  ·   ·  Flag as inappropriate

        As an exchange admin you can set this up for specific addresses. Follow the instructions in:
        https://durdle.com/2015/01/11/office-365-email-suffix-matching/ and change the match rule in step 6 to be something along the lines of:

        ^name\+\w*@domain.com$

        This will catch "name+anything@domain.com" and redirect it to the appropriate mailbox. This will need to be configured for each user who needs the functionality. For a team of developers to be able to use for testing, I'd recommend creating a shared inbox and applying the rule there.

      • Scott Carlow commented  ·   ·  Flag as inappropriate

        A bit late, but to the person who asked this:

        "The E-mail standard says that comments can be included by surrounding them in () at the beginning or end of the local part. Example:

        someAddy(someComment)@foo.com

        - or -

        (someComment)someaddy@foo.com

        Has anyone tried this with 365?"

        You are referencing RFC822, which was made obsolete be RFC2822. "Comments" are referring to things like the friendly name of a person or system name, and that syntax was replaced with addr-spec (e.g. [Comment or folding whitespace] "<"local@domain">". So in any case, this is not subaddressing, but addressing syntax.

        That said, It's mind boggling that outlook.com implements this but not Office 365. While 365 accepts messages from addresses that use subaddressing and you can add subaddresses to mailboxes via Powershell and ECP, the implementation is quite poor especially when compared to their own *consumer* product. I am extremely surprised that Business and Enterprise clients even need to ask for this.

      • Kindle commented  ·   ·  Flag as inappropriate

        We once wanted to use Office 365 and startet with configuration, but then realised there's no support for + adressing. That's really bad, cause we couldn't use office365 then with all other benefits.

      • Josh commented  ·   ·  Flag as inappropriate

        We will sorely miss this feature now that we are with exchange. Please add this. Our development team has used this extensively and now we'll have to use an alternate email service to continue using it.

      • Andy Doyle commented  ·   ·  Flag as inappropriate

        Come on Microsoft... you already have this working for Hotmail/Outlook accounts and these sit on Office 365 now.

      • Anonymous commented  ·   ·  Flag as inappropriate

        It's really time this gets added. It's a great way to find out when a company has sold your email address.

      • John commented  ·   ·  Flag as inappropriate

        Do you know what makes this issue worse. Dynamic "+" addresses work on free Hotmail/Outlook addresses!

      • David commented  ·   ·  Flag as inappropriate

        Reported March 2017, no response as of July 2018? Nice. But I suppose it should be no surprise that Microsoft wouldn't follow the RFC's, nor listen to their users.

        I used to use this feature every day on G Suite and it looks like there's no chance of O365 getting this fairly basic functionality.

      ← Previous 1

      Feedback and Knowledge Base