Re: Duplicate Mime-version error with 1.7.5
Urs Janßen <[email protected]>
| Newsgroups | gmane.network.tin.user |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jun 28, 2004 at 11:26:46PM +0200, Matt Anton wrote:
> Hi,
>
> Since tonight, i couldn't post anything with tin-1.7.5
> Here's the error:
>
> Posting failed (Duplicate 'Mime-Version' header)
this error comes from the newsserver, not tin
> This error cames up after i turned off options 101 in tin's preferences
> menu ('Use 8bits characters in news headers', ndlr).
which is the setting what one should use (except for some hierarchies like fr.*
which refuse to honor RFC2047). post_8bit_header=OFF will not only
RFC2047 encode 8bit chars in headers but also add the required
mime-headers if there are any !us-ascii chars in the body, so if
anything else also adds these headers (i.e. your newsserver or an
dumb extrnal inews or ...) you will get dublicated headers and the
server will complain about them.
> The reasons i turned off this option
btw. off (=RFC2047-encode 8bit chars) is the default as it's the
RFC-complaint setting.
> is when it's off i can successfully
> display 8bits characters that are in From headers...
right, as the 8bit chars then are RFC2037-encoded and thus do have a well
defined meaning. otherwise (plain 8bit) they don't have (cause if you
do not specify a charset you can't tell what 0xa0 etc.pp. is).
> Know bug?
no bug at all, you just have to find what is going zo try to _also_
add mime-headers and eleminate that.
urs
--
"Only whimps use tape backup: _real_ men just upload their important stuff
on ftp, and let the rest of the world mirror it ;)" - Linus