No bad header here. We always suggest using MIME/None when using a
newsreader such as Outlook Express. I don't know how it is affected using
the Web Interface, which is, IMHO, pathetic.

Have you considered using OE as a newsreader?

Setting up Outlook Express Newsreader for MSNews:
http://www.michaelstevenstech.com/ou...snewreader.htm
And:
http://www.insideoe.com/resources/co...tm#setupmsnews

Your headers:

Thread-Topic: Avoiding bad headers
thread-index: Acc9ACNxoJ3X+jURTMGhEwOhSpKKGA==
X-WBNR-Posting-Host: 217.153.167.3
From: =?Utf-8?B?S3J6eXN6dG9mIMW7ZWxlY2hvd3NraQ==?=

Subject: Avoiding bad headers
Date: Sat, 20 Jan 2007 18:02:00 -0800
Lines: 10
Message-ID:
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
Newsgroups: microsoft.public.windows.inetexplorer.ie6_outlooke xpress
NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGP01.phx.gbl
microsoft.public.windows.inetexplorer.ie6_outlooke xpress:328190
--
Bruce Hagen
MS-MVP Outlook Express
~IB-CA~

"Krzysztof Żelechowski" wrote in message
...
My name, as included in From field, includes characters from the extended
character set. This causes problems with posting to newsgroups. The
moderators get the following warning:

X-Amavis-Alert: BAD HEADER Non-encoded 8-bit data (char F8 hex) in message
header 'From'

The workaround is to persuade Outlook Express to encode extended
characters
as MIME and not as UUEncode, which is the default. The default is wrong,
every newsreader supports MIME now and only MIME allows encoding headers.