E
E. L. Wimett
Since moving to Office 2003 and specifically Outlook 2003 last week to test
it before deploying widely at our museum, I have discovered a problem with
forwarding messages received from the internet. This is enough of a problem
that it will be a show-stopper for wider deployment unless I can find a fix
or a workaround.
We are currently a single Exchange 5.5 server shop. The internet mail
connector is not active on the server and the few folks with internet mail
access are set up a corporate users with Exchange Server as primary and the
internet mail account separately specified. (Yes, I know that Microsoft has
had some issues with that in the past, but it has worked solidly for five
years and for hardware reasons we are not planning to activate the internet
mail connector until we can upgrade and go to Exchange 2000 later this
year.)
If I send a regular message to someone on the Exchange Server global address
book, there is no problem. It goes directly to their mailbox.
If I forward an internal message to someone on the Exchange Server global
address book, there is no problem. It goes directly to their mailbox.
However, if I forward a message received from the internet, Outlook 2003
uses my internet return address and tries to send the message as an external
SMTP message to the internet rather than to the Exchange Server, even if I
have carefully used the global address book drop down to address it. In
other words, it uses the dummy SMTP address created by Exchange Server and
throws it outside the firewall, where it of course bounces back as an
unresolvable address. This behavior occurs whether the local server address
is a cc or bcc or one of a series of to addresses or the only to address.
This is definitely an issue with Outlook 2003 rather than the Exchange
Server since when I go to another machine on which my identical profile
resides and open the same Exchange message store with the version of Outlook
that ships with Office XP and perform the same send on the same message to
the same recipient, this does NOT happen.
Can anyone help on this? Obviously, we do not want local mail having to go
out to the internet for delivery even if the mail connector was active!!!
E. L. Wimett
Director of Information Systems
Patriots Point Development Authority
it before deploying widely at our museum, I have discovered a problem with
forwarding messages received from the internet. This is enough of a problem
that it will be a show-stopper for wider deployment unless I can find a fix
or a workaround.
We are currently a single Exchange 5.5 server shop. The internet mail
connector is not active on the server and the few folks with internet mail
access are set up a corporate users with Exchange Server as primary and the
internet mail account separately specified. (Yes, I know that Microsoft has
had some issues with that in the past, but it has worked solidly for five
years and for hardware reasons we are not planning to activate the internet
mail connector until we can upgrade and go to Exchange 2000 later this
year.)
If I send a regular message to someone on the Exchange Server global address
book, there is no problem. It goes directly to their mailbox.
If I forward an internal message to someone on the Exchange Server global
address book, there is no problem. It goes directly to their mailbox.
However, if I forward a message received from the internet, Outlook 2003
uses my internet return address and tries to send the message as an external
SMTP message to the internet rather than to the Exchange Server, even if I
have carefully used the global address book drop down to address it. In
other words, it uses the dummy SMTP address created by Exchange Server and
throws it outside the firewall, where it of course bounces back as an
unresolvable address. This behavior occurs whether the local server address
is a cc or bcc or one of a series of to addresses or the only to address.
This is definitely an issue with Outlook 2003 rather than the Exchange
Server since when I go to another machine on which my identical profile
resides and open the same Exchange message store with the version of Outlook
that ships with Office XP and perform the same send on the same message to
the same recipient, this does NOT happen.
Can anyone help on this? Obviously, we do not want local mail having to go
out to the internet for delivery even if the mail connector was active!!!
E. L. Wimett
Director of Information Systems
Patriots Point Development Authority