T
The Lurker At The Threshold
Apologies for the mistake in my earlier posting; been sick in bed for the
past week and my organic editing comonent isn't functioning at optimum. The
problem is as follows:
On another computer running a fully-patched XP and Outlook 2003:
I send an email from the following address: <my address here>@pac bell.net
The above address is displayed to the recepient correctly
However....
When the Reply button is used, the reply address is displayed incorrectly
as: <my address here> @pacbelll.net - please note the extra "l" in pacbell
The reply, of course, bounces back as being sent to an invalid address.
This bad behavior is exhibited across a number of, if not all, different
recipients.
On further research, found the following in the MS KB:
CAUSE
This problem may occur if all the following conditions are true: . Your
mailbox is located on a server that is running Microsoft Exchange Server.
. The sender's display name is encoded by using UTF-8.
. The sender's display name contains both of the following:. A comma
. One or more extended characters, such as à, á, â, ã, ä, or å
. Either of the following updates was applied to the Exchange server
that contains your mailbox:. Microsoft Exchange Server 2003 Service Pack 1
(SP1). For more information about Exchange Server 2003 SP1, click the
following article number to view the article in the Microsoft Knowledge
Base:
836993 (http://support.microsoft.com/kb/836993/) How to obtain
the latest service packs for Exchange Server 2003
. Microsoft Exchange 2000 Server Post-Service Pack 3 Update
Rollup. For more information about Exchange 2000 Server Post-Service Pack 3
Update Rollup, click the following article number to view the article in the
Microsoft Knowledge Base:
870540 (http://support.microsoft.com/kb/870540/) Availability of
the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup
*****************************
The problem is that all of the above are not true and that is
the only entry in the KB which address the poblem.
Any ides as to what is going on here? Anybody got a fix? I suspect that
deleting the account and then reestablishing it should fix things but I am
as much interested in understanding the underlying cause as well.
Sleepless in Marin
past week and my organic editing comonent isn't functioning at optimum. The
problem is as follows:
On another computer running a fully-patched XP and Outlook 2003:
I send an email from the following address: <my address here>@pac bell.net
The above address is displayed to the recepient correctly
However....
When the Reply button is used, the reply address is displayed incorrectly
as: <my address here> @pacbelll.net - please note the extra "l" in pacbell
The reply, of course, bounces back as being sent to an invalid address.
This bad behavior is exhibited across a number of, if not all, different
recipients.
On further research, found the following in the MS KB:
CAUSE
This problem may occur if all the following conditions are true: . Your
mailbox is located on a server that is running Microsoft Exchange Server.
. The sender's display name is encoded by using UTF-8.
. The sender's display name contains both of the following:. A comma
. One or more extended characters, such as à, á, â, ã, ä, or å
. Either of the following updates was applied to the Exchange server
that contains your mailbox:. Microsoft Exchange Server 2003 Service Pack 1
(SP1). For more information about Exchange Server 2003 SP1, click the
following article number to view the article in the Microsoft Knowledge
Base:
836993 (http://support.microsoft.com/kb/836993/) How to obtain
the latest service packs for Exchange Server 2003
. Microsoft Exchange 2000 Server Post-Service Pack 3 Update
Rollup. For more information about Exchange 2000 Server Post-Service Pack 3
Update Rollup, click the following article number to view the article in the
Microsoft Knowledge Base:
870540 (http://support.microsoft.com/kb/870540/) Availability of
the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup
*****************************
The problem is that all of the above are not true and that is
the only entry in the KB which address the poblem.
Any ides as to what is going on here? Anybody got a fix? I suspect that
deleting the account and then reestablishing it should fix things but I am
as much interested in understanding the underlying cause as well.
Sleepless in Marin