Chit Chat
There is currently 1 person viewing this thread.
I have a number of contacts in my win 10 people app whose names are edited to reflect their changing positions within an organisation – so “John Smith Facilities Manager” may be edited to become “John Smith HR Manager”.
When I open up a new e-mail and begin typing the name in the “To” box, a list appears showing the edited (correct) name. However once selected, it then displays as the original incorrect name. The person receiving the email also sees the incorrect name.
This is obviously not only confusing but bloody annoying too! The same thing happens when using the webmail rather than the app.
Does anyone on here know why this happens and what I can do to stop it?
Thanks.
When I open up a new e-mail and begin typing the name in the “To” box, a list appears showing the edited (correct) name. However once selected, it then displays as the original incorrect name. The person receiving the email also sees the incorrect name.
This is obviously not only confusing but bloody annoying too! The same thing happens when using the webmail rather than the app.
Does anyone on here know why this happens and what I can do to stop it?
Thanks.
sort by:
Show
per page
Replies: 2
|
By:
Clear Outlook's cache (or whatever mail app you are using).
Here is a link to Microsoft's instructions for Outlook which include an "easy fix" program to download. https://support.microsoft.com/en-gb/help/287623/how-to-reset-the-nickname-and-the-automatic-completion-caches-in-outlook |
|
By:
Thanks for the reply Ramruna.
I have tried searching but can't seem to find any information on deleting cache from the windows 10 mail app. I have exported the contacts and cleaned them up before importing into a fresh installation of the app but the problem still appears. I can only guess that it is drawing information from old saved emails. Unfortunately, I can't delete the old emails as they need to be kept. Logging into the account via a browser on another PC shows the same problem so I guess it's not just a cache problem. |