Sep 15 2016 07:38 AM
Sep 15 2016 07:38 AM
Suddenly, aliases have been capped at 200 without any stated reason.
I have been using more than 200 aliases for 15 years because I assign a specific address to vendors to find out who sells my email address. I currently have 416 aliases. For what it's worth, I have started a support ticket but I'm wondering if anyone knows what prompted this unwelcome change?
Sep 15 2016 11:11 AM
Is your mailbox on an Exchange Server or Exchange Online. If Exchange Server, what version?
Sep 15 2016 11:51 AM
There's a lengthy thread about this on Answers: New limit on "proxy" addresses - unable to delete old proxy addresses or add new ones
I've pinged some MS guys on this, guess I should give them another poke.
Sep 15 2016 01:28 PM
I, too, commented on that thread with added emphasis. I'm just trying to get to the bottom of the actual reason this has suddenly been limited. It has created yet another issue I didn't need today.
Sep 16 2016 02:24 AM
The number of proxy addresses was limited because of an AD limit that can be reached otherwise.
Sep 16 2016 06:47 AM
I do not believe that article applies because (1) it describes the 2000 and 2003 versions of AD and (2) this change only occurred this month.
I know this because we migrated to O365 in December 2013 with accounts containing more than 300 aliases and without any such complaint. One account went over 400 earlier this year.
I log into the Exchange Admin Center almost daily and this "error" dialog only began appearing this week. There is no other conclusion I can draw except that an arbitrary, possibly accidental and certainly unwelcome policy change has occurred.
I am simply attempting to question this change as I do not believe the full impact was considered. I would like to petition for reconsideration.
Sep 16 2016 07:51 AM
Sep 16 2016 08:29 AM
Sep 16 2016 10:44 AM
Yes, Nino has promised to get to the bottom of it. Once we have any info I'll reply here as well.
Sep 22 2016 08:46 AM
This article was updated to reflect the change in recipient proxy address limit.
Sep 22 2016 01:36 PM
Nino just posted another comprehensive update on the Answers thread: Read this reply
Nov 29 2016 08:56 PM
UPDATE: Unwelcome resolution.
The only option for any kind of solution was to create multiple Distribution Groups for individuals requiring more than 200 "proxy addresses" or aliases. It's the most stupid thing I've ever had to do in all of my 30 years of administration experience. I now have four, count 'em, FOUR distribution groups specifically for ME that contain 100 or more addresses in unequal alphabetic divisions.
I now accept that there may have been a limit previously however I was not even close to halfway at only 416 of some supposedly high number of 1200-1300 or more. Suddenly I was shown this popup in September 2016 that mandated no more than 200 addresses were acceptable after I had been well over 350 for years so I know this was a conscious decision by a bureaucrat somewhere at Microsoft. There is no other possible conclusion. Furthermore, I sincerely doubt this was carefully considered whatsoever.
There has to be a better way — if sensibility could ever prevail! If only Microsoft could find some way to incorporate WILDCARD addresses, this problem would hardly occur. Yes, I've seen the supposed "workarounds" for wildcards but it shouldn't be required. As always with Microsoft, I am once again disappointed, almost as much as with the Edge "browser" that some bureaucrat at Microsoft laughingly thought was a good idea. Sigh.
Dec 01 2016 12:47 AM
Have you tried to use the plus-sign in your mail-address instead of aliases?
Then you only need one E-mail address on your mailbox.
For example, if you have the mail address firstname.lastname@example.org.
Then use email@example.com when you register mail-address at HPE or firstname.lastname@example.org etc.
All mail should be delivered to the mailbox with the alias email@example.com
Dec 01 2016 05:30 AM
Thanks for the suggestion but I have just confirmed that plus sign addressing does not work with Office 365. It generates a "550 5.4.1 Recipient address rejected" error.