Bug in TIdMessage.ProcessHeaders and Charset-Property

Giganews Newsgroups
Subject: Bug in TIdMessage.ProcessHeaders and Charset-Property
Posted by:  JN (die…@gmx.de)
Date: Wed, 2 Jun 2004

When processing a message where charset is already included in ContentType
and the Content-Type property was
not set again before processing the message the Charset ist appended every
time you process this message!
Even if you set the Content-Type property (eg to "text/plain") the Charset
property exist two times

and then it look's like this:
----------------------------------------------------------------------------
-----------------------------------------
Return-Path: <mailin…@gmx.net>
Date: Mon, 31 May 2004 10:24:51 +0200
From: "GMX Best Price" <mailin…@gmx.net>
To: "Alle Mitglieder von GMX" <membe…@gmx.net>
Subject: Nokia 6230 - mehrfacher Testsieger - =?ISO-8859-1?Q?f=FCr?= 0,-
EUR!
Message-ID: <20040601221910.29727abo…@gmxinfo05-rz3.gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1";
charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Liebes GMX Mitglied,
(and so on...)
----------------------------------------------------------------------------
----------------------------------------

By the Way:
Why the Charset-Property in TidMessage.GenerateHeaders was added after + EOL
+ TAB
in Line ContentType := ContentType + ';' + EOL + TAB + 'charset="' + Charset
+ '"';
Can't find nothing similary in RFC2045

(Found in Indy 9.0.14 latest Dev-Snapsshot, but also Indy 10 seems to have
this problem (only by looking in code - not tested !)

Thanks !!!!!

Jens

Replies