Reading Plain Text Instead of HTML, Embedded Images Missing

  • Thread starter Thread starter Vicki
  • Start date Start date
V

Vicki

I have Outlook 2003 set up to compose in HTML and NOT read in plain text.
Al;though my settings accurately reflect what I set up, messages I send to
e-mail groups ( I receive copies) are now plain text. Everything I know to
check is correct.

I noticed this when I sent an image inserted in the body of an e-mail. When
I received it the first time, the dreaded red "x" appeared where the jpg
image should have been. So, I resent an e-mail as a test. That 2nd e-mail and
several subsequent ones I sent were brought in Outlook as plain text, not
HTML as it had been 2 hours before, and the image is, of course, missing.

I visited Microsoft's website and could find no help other than what I had
already tried, and I completed a system restore to yesterday, to no avail.

I'm working with Windows XP Pro.

Any suggestions on what may have happened and how I can fix it?

Thanks.
 
If you see an X in the message body where a picture should be, you are
composing in HTML format and not Plain Text.
Which method of inserting a picture did you use?
Is the picture located on a web server?
Do other recipients of the message also get the red X?
 
Outlook is set to compose AND read (by virtue of not having "read in plain
text checked") in HTML, which is why I'm having the problem. I don't know why
messages I am sending with an embedded picture are being read as plain text.
The red x only occurred once. After that, the picture simply was not in the
body of the e-mail when it came into Outlook, but when I checked my Sent box
the picture was embedded in the body.

When I insert a picture I go to the menu bar, click on Insert, then on
Picture and Browse to where the picture is saved on my computer, select the
picture and click OK.

Images I send are not located on a web server, but on my personal computer.

When the red x version appeared, it was also a problem for other individuals
who read e-mails in HTML.

Another note. This started occurring yesterday AFTER my computer was
automatically updated overnight and restarted. That would have been a
Microsoft update.

Thank you for working with me to resolve this issue.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top