In article <[log in to unmask]>, Andrew Herd
<[log in to unmask]> writes
>I am in discussions with Microsoft over this, and they are keen to see
>examples. In addition, can anyone who has this problem with my messages
>email me privately and let me know which email client and operating system
>they use? Any other examples of messages including headers and the error
>code would be appreciated.
>
>From talking to MS, this is a 'feature' of Outlook and I don't think it is
>fixable. I only seem to have a problem with it on GP-UK (and interestingly
>enough, it only seems to have reared its head recently, despite my having
>used this version of Outlook for about six months), which presumably because
>of the number of people here using non-windoze apps. If it is a big problem,
>you are going to need a new list-owner, chaps.
>
>Andrew
>
Andrew
I have spent an afternoon sending myself messages on different accounts
in differing formats and searching the web for character sets.
When I use mime with Outlook Express it automatically is sent in:-
Content-Type: text/plain;
charset="iso-8859-1"
This reads OK for me
Character Sets can be altered in the compose message window
format/language. If I change to another character set then the previous
problems occur.
As far as I can see the choice between "iso-8859-1" and "Windows-1252"
is set at installation time.
For mailing list use The problem can be solved entirely by going to
Outlook Express
Tools/Options/send/plain text/settings and using uuencode rather than
mime.
That appears to send plain asci without defining a char set.
We did that some time back to sort out other incompatibilities
--
David Meldrum
[log in to unmask]
http://www.suffolk-maag.ac.uk
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|