Outlook using wrong address from Exchange contact when sending via

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Rick Voland - 23 Feb 2006 18:48 GMT

My setup: I am using Outlook 2002 with an Exchange server (SBS 2K3) account
and an external pop mail server account. The default sending account is set
as the pop account.

My problem: When I send an external email to someone and CC an address of a
user that is on my Exchange server, Outlook 2002 is using the wrong email
address for the CC entry. Instead of using the address that is set as the
primary address on the exchange server, ("user@domain.com"), Outlook is using
the local domain address ("user@domain.LOCAL"). This causes the recipient to
get an error back if they do a reply to all because of the user@domain.local
address.

Is there a way I can force Outlook to use the primary address? This seems
to work fine with Outlook 2003 users and is only a problem with Outlook 2002.

If this should be posted in an Exchange group, please let me know.

Reply to this Message

Diane Poremsky [MVP] - 23 Feb 2006 19:56 GMT

Is there a reason why the exchange server isn't sending mail to the
internet? Is the domain.com address set as default for all the internal
users? Was originally set up that way or changed later? You might have to
refresh the local address book to show the changes.

Signature

Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/

Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:
EMO-NEWSLETTER-SUBSCRIBE-REQUEST@PEACH.EASE.LSOFT.COM

> My setup: I am using Outlook 2002 with an Exchange server (SBS 2K3)
> account
[quoted text clipped - 19 lines]
>
> If this should be posted in an Exchange group, please let me know.

Reply to this Message

Rick Voland - 23 Feb 2006 21:37 GMT

Our external "domain.com" email is hosted at an ISP. When email is sent
through the exchange server, it uses "domain.dyndns.org" (temporary domain)
as the fully qualified domain name because if I set it for "domain.com", it
will fail on reverse dns lookups. The reason we don't want to send email to
external clients using the exchange server is because it was tried and had
some problems. I think mainly because of the reverse dns problem, but at any
rate, they decided they want to keep using our external ISP email.

The exchange server is currently setup with "domain.com" as the default for
all internal users. It was originally setup with "domain.org" as the default
and then changed to "domain.com". It used to use "domain.org" in the same
way it is now using "domain.local" until I deleted "domain.org" from the list
of Default Policy E-mail addresses. There have not been any changes for at
least 2 months. How can I force an update of the local address book?

> Is there a reason why the exchange server isn't sending mail to the
> internet? Is the domain.com address set as default for all the internal
[quoted text clipped - 24 lines]
> >
> > If this should be posted in an Exchange group, please let me know.

Reply to this Message

Rick Voland - 23 Feb 2006 23:13 GMT

I have done some more testing and am going to try to explain what I have found.

I created a new user to test with. I used my current outlook 2002 profile,
sent email to an external account and CC to an old exchange account and the
new exchange account. When I looked at the external message, the old account
address showed up as the unwanted "user@domain.local" but the new account
address showed properly with "user@domain.com".

I tried to create a fresh new Outlook profile using my old exchange account
thinking this would update any locally cached address info, but it produced
the same results as before.

I created a new Outlook profile using the new exchange account and when the
test message was sent, both old and new accounts showed their addresses using
the proper "domain.com" address.

So, it looks like the actual problem is that the old exchange account has
cached the exchange global address book locally and is not updating it. Is
this the case and can someone tell me how to force it to update?

I’m still not sure why it did not update when I created the fresh new
profile using my old exchange account though.

Reply to this Message