Re: [Mailman-Developers] Content-Type and Content-Transfer-Encoding headers
On Thu, 27 Jul 2000 13:48:06 +0400 Michael Sobolev mss@transas.com wrote:
Content-Type: text/plain; charset=koi8-r
And, as our users use different MUA, Content-Transfer-Encoding may well be different from 8bit, and it's usually equal to base64 or quoted-printable.
Mailman will nto help you here. You need to use an external archiver that handles character set definitions properly. MHonArc is such an animal:
The problem is two folded. The mailing list engine just appends footer maillist administrator creates and this usually results in garbage...
This is a known problem as the list signature code is not MIME aware. The only useful solution is to turn off list signatures.
-- J C Lawrence Home: claw@kanga.nu ---------(*) Other: coder@kanga.nu http://www.kanga.nu/~claw/ Keys etc: finger claw@kanga.nu --=| A man is as sane as he is dangerous to his environment |=--
"JCL" == J C Lawrence claw@kanga.nu writes:
JCL> This is a known problem as the list signature code is not
JCL> MIME aware. The only useful solution is to turn off list
JCL> signatures.
Patches welcome (but please use the SourceForge patch manager). I don't have time to work on this right now.
-Barry
participants (2)
-
bwarsaw@beopen.com
-
J C Lawrence