HTML like code in e-mail

[TerryTutor]

Friend has interesting problem I've never seen. Has Outlook 2003 - started
after using match.com (could be coincidental). When he receives e-mail, and
then forwards it, the reply comes back with what looks to be HTML tags on the
e-mail he sent.

Anyone know of a way to stop that?

Should he not hit the reply button, but cut and paste into a new e-mail,
then send?

 

[Pat Willener]

What do you mean by "comes back"? Forwarded mail should not come back,
unless an invalid email address has been specified (or an error occurred
on the receiving mail server). Mail that "comes back" like that are
Non-Delivery Receipts, and they can contain just about anything,
including HTML code of the original message.

 

[TerryTutor]

Sorry for the delay - I had trouble accessing the question I posted.

Here is an example of what he sends me:

I am still getting back emails that I wrote where the apostrophe is
converted into a question mark.

And when I forward or reply to an email, it still changes the format into
codes.

He sent me an example of an e-mail where he copied and pasted webtext into
an e-mail which looked normal when he sent it out, but when the person
replied, it changed images into what looks to be HTML code. I have no
explanation for the apostrophes converting to question marks.

 

[TerryTutor]

Here is another example of what started out as: Blue Cross Blue Shield

When the person replied, his original message looked like this:

"<!--[if! SupportList]-->? <!--[endif]-->Blue Cross Blue Sheld"

Does that help?

 

[TerryTutor]

More data for you. He has Outlook 2003 set to HTML mail format. However,
when he goes to compose a new e-mail, Outlook is seemingly converting the
view to webpage layout view. Short of detect and repair, is there another
fix?

 

[Brian Tillman]

More data for you. He has Outlook 2003 set to HTML mail format.
However, when he goes to compose a new e-mail, Outlook is seemingly
converting the view to webpage layout view. Short of detect and
repair, is there another fix?

Is this on a Vista PC?