Please HELP, outlook cant read incredimail messages

[Guest]

I use Outlook 2000. when I receive an Incredimail, all I see is pages and pages of script/code. Is there a setting so I can see the mail as intended?

 

[*Vanguard*]

"(e-mail address removed)" said in

I use Outlook 2000. when I receive an Incredimail, all I see is pages
and pages of script/code. Is there a setting so I can see the mail as
intended?

You sure it isn't one sender using Incredimail that is somehow sending their
message in plain text format rather than in HTML format?

 

[JAG]

Hi Vanguare - I didn't ask my friend that as he said all his other correspondants have no trouble reading his mail correctly. I spoke with one of them and he uses OE, but he's not computer literate so cant tell me about his settings etc. I'll check with the originator though and let you know. Thanks JAG

PS. Do you know why my message text has no line breaks after posting, although it looke fine in the composing box???

 

[*Vanguard*]

"JAG" said in news:[email protected]:

Hi Vanguare - I didn't ask my friend that as he said all his other
correspondants have no trouble reading his mail correctly. I spoke
with one of them and he uses OE, but he's not computer literate so
cant tell me about his settings etc. I'll check with the originator
though and let you know. Thanks JAG

Do other HTML-formatted e-mails (*not* sent from an Incredimail user) look
okay? If not, and if all HTML e-mails look like plain text format, it could
be you have a registry value set to force Outlook to view all e-mails in
text-only format.

Also, Outlook uses Internet Explorer to render what you see for
HTML-formatted e-mails. Web browsers often make up for a lot of slop in
HTML code but can't figure out all the screwups. That is, the HTML code
generated by Incredimail may not be 100% compliant with HTML standards. The
browser may or may not be able to compensate. So it could be something to
do with how you have IE configured. Make sure Outlook is configured to use
the Restricted Sites security zone in its Security options. Then look in
Internet Options to verify that the Restricted Sites security zone is
configured to the default setting of High.


OL2002: Users Can Read Nonsecure E-mail as Plain Text
http://support.microsoft.com/?kbid=307594

Although the article notes it is for OL2002, it might apply also against
OL2000.

PS. Do you know why my message text has no line breaks after posting,
although it looke fine in the composing box???

Are you still asking about Outlook when sending e-mail or when using Outlook
Express to post to newsgroups?

For Outlook 2002 (don't have OL2000 to look at) when sending e-mail, there
is an option to enable/disable the display of extra line breaks:

Tools menu -> Options -> Preferences -> Email Options -> "Remove extra
line breaks ..."

For Outlook Express, I noticed the following difference between your post
and mine. Yours has a MIME part of "Content-Type: text/plain; ..." and each
of your lines ends with " =" (space character and equals sign). Mine
doesn't have a MIME part and the lines aren't postfixed with any special
tag. In OE:

Tools menu -> Options -> Send

is HTML or Plain Text selected for the newsgroup posting format? I suspect
Plain Text. I optioned OE to read all messages as plain text.
HTML-formatted messages will show an attachment (for the .htm file). I
don't see an attachment on your posts so I suspect you are sending in Plain
Text format to newsgroups. Now check under

Tools menu -> Options -> Send -> Plain Text Settings

Are you sending in MIME or UUencode format? My Outlook Express v6 is
configured to send in UUencode format. I don't recall ever changing this
setting so it is probably the default. Using MIME format probably explains
why there was a MIME header and part in your posts.

If you right-click on your post in the item list pane, Properties, Details,
Message Source, you'll see that your lines did get wrapped at about 72
characters which I suspect is what you have configured in OE for the max
line length or wrap point. However, MIME capable clients, like OE, will
treat the " =" postfix as a line continuation character and so they will
merge the lines together and wrap them according to the size of the window
in which you are

viewing the message.

I continue using UUencode format because all the old foggie standards
preferred by the newgroup "elders" dictate not using any of the newer
message formats.  You're told not to use HTML for posts, users debate top-
versus bottom-posting, what character to use for indenting, spacing, and
other "standards" that you're supposed to follow when posting to newsgroups.
With all the vehement fanaticism to comply with 20- to 30-year old standards
to provide a least-common-denominator format for messages, you'd think they
also be bitching and mandating valid grammar, punctuation, capitalization,
and so forth.  The point is to communicate reasonably well enough to convey
your question, response, or opinion.  If you like to use MIME format for
your newsgroup posts, I don't see any big damage because of it.  Rather than
having your lines artificially truncated on a word boundary at some max
length of, say, 72 or 76 characters based on some 20-year or older
"standard", your MIME-formatted e-mail will be wrapped within the window
size of the reader's newsreader and probably be a lot more intelligible.
The only place I've seen teletype machines are in museums so the "standard"
that we still have to chop lines up at some max length is really antiquated
and inappropriate.  That's as stupid as making everyone who starts their car
get out, walk to the front, and jump up and down several times because at
one time you had to wind a crank at the front.