Error message showing above the "TO" area when making a new email
"This e-mail message can not be delivered to Distribution List because the e-mail address is no longer valid"
I know there was another discussion on it, but the topical heading throws people off about Outlook Tips.
On a Windows 7 Enterprize, with Outlook 2007, with Exchange 2010 for a very large company.
Even the big cheeze had this error show up in his machine and doesn't look good on us, cuz, you know, we suggested the rollout upgrade...
Not every email. Not the same email address or same person sending it. They work on my machine, and someone elses, but just random machines. THey were all imaged the same, so I suspect a profile exchange handshake issue.
Even weirder some can still send the email in question to the address "not valid" and it will get there, but some other emails won't go through.
Tried deleting their autocomplete (drop down when typing the email) and getting directly from the Global Contact List.
Will try the remove cache item and reset, but doubt it.
We are having the exact same issue with a hosted exchange server that one of our clients runs.
They recently deleted a distribution list and transferred the e-mail address that it used to hold email@example.com to a users mailbox. Externally its no problem, but nobody in the organization can send to firstname.lastname@example.org and they all receive the no longer valid error message.
Anybody got any clues?
Found a fix!!
At least for our problem.
It was actually client side and I suspect something to do with the way outlook 2010 handled x.400 address changes.
All we had to do was click the to. field in a new e-mail on the clients having problems and have them select the user from the GAL.
Once they had done this the first time the problem was resolved.
Hope this is of help
Yeah, tried the GAL and same issue. Ended up going through the users mailbox and recreating the contact list for them. But this is like the 3rd person, I don't want to do that for all 500 employees!
Somehow the handshaking from Outlook 2010 and Exchange 2010 fubard.
Clean Win7 machines too.
Yeah Carlos you'll have to get the users to delete any email addresses that are not complete in their address book and then recreate them. Seems OL2003 even made addresses out of phone numbers.
- Proposed as answer by Moshe Hirsch Tuesday, February 11, 2014 7:44 PM
Use one of the following methods to reset the whole Outlook nickname cache for Microsoft Outlook 2010.
- With Outlook 2010 open, click File (BackStage), and then click Options.
- Click the Mail tab.
- Under Send Messages, click Empty Auto-Complete List.
Outlook will generate a new nickname cache.
- Click Start, and then click Run.
- Start Outlook by using the /CleanAutoCompleteCache switch.
For example: Outlook.exe /CleanAutoCompleteCache
Note If Outlook is not installed in the default location, you must point to the path of Outlook.exe.
Outlook will generate a new nickname cache.
- Proposed as answer by VincentA Friday, November 25, 2011 5:21 AM
Despite the helpful tips to try to remedy, nothing is working. Exchange is 2010, Outlook is 2010. Enterprise environment, globally used. Pull DL from GAL directly, never used before, shows the error.
The delivery to that DL happens, but users complain about the fact that error exists. Lot's of other odd errors from exchange on many migrated DL's, or Functional mailboxes (says no permission to send from, or to) but those errors are null, not accurate.
Any other ideas to be able to remove these GAL related, issues? GAL is controlled by MIIS so cannot delete actual entries, and re-enter. They are globally replicated so the entries are not controlled by users, rather by exchange admins but I see no errors on exchange either.
Thanks for any ideas you may have,
- Edited by Michele_Boz Thursday, July 26, 2012 4:52 PM
Hello Everyone , there is also another reason why this error would occur. Every account has their exchange addresses stored in the proxyAddresses attribute, but GAL uses the mail attribute to read the primary SMTP of an user account.
Please make sure if the Email information in General tab in Active Directory is equal to the primary SMTP address of the user.
This will fix the issue.
- Proposed as answer by JamesB75 Monday, July 01, 2013 8:47 PM
Here is what I have witnessed: (restarting outlook and PC didn't help)
I entered the address card of one problematic contact' changed the display name and e-mail and saved (without closing)
then changed back the DIsplay NAme and e-mail address to the real ones counting only on my typing from scretch.
Then saved the contact and CLOSED OUTLOOK immediately witout trying to send mail to this recipient.
Verified OUTLOOK.EXE is not running at the Process Tab on Task Manager
Started OUtlook and the problem was gone.
ANoher PC which had the same problem which the user over there has full rights on the problematic mailbox - was now functioning well without taking any action on it.
Hope it works for the coming after IT persons
In our case, the user created an Outlook Contact for this particular recipient, even though it could be found in the GAL. I was able to resolve by opening the Outlook Contact created by user and removing the email address, then Saved. I deleted that particular auto-complete cache entry, pulled it from GAL again and the error stopped appearing. I suppose the user created a Contact to add additional info that the GAL we implemented for our business did not provide (cell number, home address, etc).
- Proposed as answer by dabassguy1 Monday, December 19, 2016 6:49 PM
Just ran into a similar issue where one user tried to email another user whose mailbox was still being created. It seemed to cache the fact that the email wasn't valid, but the emails still go through properly. All we had to do was start typing the email address so that it prompted to auto-complete, then click the X next to the suggestion to remove it. We entered the username, told it to "Check Names" and all was well. There were no issues in AD or Exchange, just the individual Outlook client which was the 2013 version connecting to Exchange 2010.