Header problem: Content-Type: text/plain; charset=x-user-defined

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

E-mail messages received with the following header line are causing a problem
in Outlook 2000 (from information does not display, header is shown in
message text, cannot forward messsage).

Content-Type: text/plain; charset=x-user-defined

Is there some seeting which will allow Outlook 2000 to handle this?
 
Nope and believe it or not, Outlook is operating as designed. Just ask
whomever is sending you messages to switch their encoding type to Western
European (or whatever is right for their region).

/neo

ps - it is the "x-user-defined" that causes the grief part.
 
I guess they decided to change the design in later versions of Outlook.

This is somewhat off topic for this group, but by any chance, do you know
how to change the encoding in Netscape 4.8 (which is what the sender is
using). Also note that the sender is sending formatted text, even though it
says "text/plain".
 
Eli Jacobs said:
I guess they decided to change the design in later versions of Outlook.
Click to expand...

Sorry, I forget to explain this comment. The same message is handled
without problem on machines I have running Outlook 2002(XP) and Outlook 2003.
Just confirming that this is due to version difference, as opposed to a
setting.
 
I know, I whined like a school girl during the beta of Outlook 2002 because
Outlook 2000 IMO would let you reply and click send, but would throw an out
of memory condition when it came time to transport the message via SMTP.
(Not to mention that after Outlook 2000 accepted one of these jems, every
plain text message after it didn't come in right either. :(

From searching the web, is there a View > Character Set option?
 
I looked at the sender's machine today, and found that there is a setting in
Netscape 4.8 for the encoding. However, whenever I set this to Western, it
sets itself back to user-defined. (I looked at someone else's Netscape 4.8
setup - and they do not have this problem - they are able to set the encoding
to Western.)

I guess we'll have to somehow find the source of the problem in the sender's
machine (the clean solution), or upgrade to a newer version (which deals with
user-defined) on the recipient's macine (the band-aid solution).

Thanks for your help.
 
Back
Top