[leafnode-list] Re: Base64 coding in list messages

[Whiskers <catwheezel@xxxxxxxxx>]

On Tue, 21 Oct 2008 17:57:08 +0200 Matthias Andree
<matthias.andree@xxxxxx> wrote:
> Whiskers schrieb:

[...]

> Peter J. Ross's and your second message already arrived in
> quoted-printable CTE with UTF-8 charset.
> 
> The paths from the list to my account as well as to @operamail.com are
> 8-bit-clean, all advertise 8BITMIME, so no reencoding takes place. AFAIK,
> Postfix never reencodes to base64, only to quoted-printable, if at all.
> 
> I don't know who re-encoded them; I presume it was Mailman or Python's
> SMTP library. Base64 encoding might then happen behind the scenes at
> outblaze.com/operamail.com.

I've never observed Operamail do that to any messages received in UTF-8; I 
just tested again, and the coding was not changed from the

    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

which Claws-Mail gave the text - which was:-

Schrödinger's cat is worth çirca €1 and drives a Citroën DS paþetically.

I've unsubbed from this list via my Operamail address, so I won't see what 
happens to this message when received there, but it will be interesting to
see if it gets re-coded anyway.

> > so perhaps it isn't the actual characters, so much as the sender's 
> > character set - I used UTF-8 (automatic setting by my software when I
> > use non-US-ASCII characters); perhaps Peter did too?  If the messages
> > go through a system that can't handle UTF-8 I can see that causing a
> > problem.
> 
> The charset is only of interest to systems actually presenting the
> message, i. e. my mailer such as Evolution, KMail, Thunderbird, mutt, or
> a webmailer such as SquirrelMail or Horde IMP or custom systems.

[...]

> The first option. Please report this problem to the FreePOPs maintainers
> only.

OK.

> > I have in fact migrated my subscription to this list to a new free
> > email account with GMX's new 'beta testing' service , which includes
> > POP and IMAP access, so the immediate difficulty for me should be
> > solved.  But the curious changing of the encoding of messages remains.
> 
> I'm quite confident it's outside of the list server and the paths which I
> can influence, since I've set up the list server.
> 
> HTH
> MA

Once again, thanks for you interest  :))

-- 
-- ^^^^^^^^^^
--  Whiskers 
-- ~~~~~~~~~~
-- 
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/