Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I had setup an external contact in exchange (Mail Contact) for a contractor (let's say Joe User, forwarding to

I was having the problem whereby any mail sent to Joe User from within exchange was always arriving at Joe's end with a winmail.dat attachment. Figuring this may be related to the fact that I had Joe setup as a mail contact in exchange, I removed the contact from exchange.

Now from Outlook, if I compose an email to (as I would to any person not I get a delivery error, immediately, from exchange advising that the recipient 'Joe' can't be found. It's as if Exchange is trying to resolve this locally, rather than delivering it externally.

Any suggestions on how to get Exchange to 'forget I ever added this guy as a mail contact' and deliver the mail externally as it would with any other domain?


share|improve this question

Try deleting your nickname cache in Outlook to deal with the delivery error.

You also might want to read these:

share|improve this answer
Exactly. Outlook is vigilant about this kind of thing, which is why us Exchange admins have to be real careful about changing peoples names after things like marriages. Do it wrong and everyone they ever emailed will start getting this exact error. – sysadmin1138 Jun 23 '10 at 16:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.