Hi Clint - I'm the guy that originally posted this in another forum (the one you referenced in your original post). I believe I've found a solution to this - at least where it relates to my particular case. While the resolution makes little sense
to me, it does work so hopefully it will be useful to you and others reading this later.
Background: I have a client experiencing similar issues - we were getting "Invalid e-mail alias" when editing certain user accounts within the SBS 2008 console. This error would come up when making ANY change to the user within the console (regardless
of whether it was related to emails, aliases, or Exchange). What confused me initially was that many of the users I was trying to change were affected by this issue. Then, due to lack of response from MS, and an increasingly frustrated client,
I dug hard into this to compare the users.
For our situation, deleting and recreating multiple User accounts or Exchange accounts was not really an option and would quite likely create another swarm of support calls and world of headaches. So I took another approach.
I found that the only users having the issue happened to use blackberry devices and had contacts setup for their Blackberry alias to forward mail to. However, it was not affecting all Blackberry users - so what gives? The answer, the email address
of the blackberry contact record. If the email address (EXCLUDING domain) was the same as the user's Exchange alias it was creating conflicts. So if Joe User's Exchange alias is
JUser@MyCo.com and he had a Blackberry contact setup at
JUser@Blackberry.net this was causing a conflict. Why? I have no freaking idea since a duplicate alias should not register (IMHO) if the domain itself is different. In this case, not only is the domain
different but the "conflicting" address is an external contact!
So I dug further... The contact had been setup in the same OU as the User (this had been migrated from SBS2003 which I believe had defaulted the creation of new Contacts to the same OU). The OU in this case was MyDomain\MyBusiness\Users\SBSUsers.
Here's options to fix it (assuming, of course, you have the same scenario):
- User a different email address for the contact (obviously easier said than done).
- Remove any forwards or other dependancies that you had to it within Exchange. Delete the Contact from the current OU. Recreate it in a new OU (recommend a new OU especially for Contacts). Note that simply moving the Contact from the old
OU to the new OU doesn't seem to work (maybe it would with a full restart, but I wasn't in the position to be constantly restarting the server to play around with a new idea).
Note that disabling the old Contact, nor disabling the Exchange forwarding rule to the Contact, nor moving the Contact to the new OU worked for me. It only worked by deleting and recreating a new Contact in another OU.
<sarcasm>I'd like to thank Microsoft for their prompt reply to this and other forums including Microsoft Connect</sarcasm>
Seriously though - can someone at Microsoft please make note of this and list it as a potential bug for review?
EDIT - it looks like the success was temporary. While this worked and I was able to edit the initial users I modified in the above manner, when I went to make changes to the additional users at a later time I first did a check on the users I had already
updated - FAIL. So the change I made worked, but only for a while. This may have something to do with the 24-hour refresh cycle of the SBS console that was mentioned in one of the posts above. So, to refresh, I am able to reproduce this issue
(just create a Contact with an email name that matches the Exchange email name), but am currently only able to work around the "Invalid E-mail Address" warning with temporary measures (such as temporarily renaming the external Contact's SMTP address).
I again look to Microsoft for answers on this - now that I seem to be able to reproduce the error, can you look into this and provide a solution?
Tuesday, July 27, 2010 4:37 PM
The initial solution recommended worked only temporarily.
Proposed as answer by
Sunday, October 17, 2010 3:35 AM