MIME email vs. Ecartis (was Re: [PATCH] Re: Prepare dynamic plugins (again))

[Derrick Hudson <dman@xxxxxxxxxxxxxxxxx>]

On Thu, Sep 10, 2009 at 08:53:43AM +0200, Christoph Höger wrote:
| Am Donnerstag, den 10.09.2009, 01:50 +0200 schrieb Nicolas Sebrecht:
| > On Thu, Sep 10, 2009 at 12:35:11AM +0200, Christoph H??ger wrote:
| > > 
| > > +Developing your own UI
| > > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This text looks like the "quoted-printable" Content-Transfer-Encoding.
It is an alternative to "base64" for sending data that does not meet
the restrictions of (legacy) SMTP (ie non-ASCII characters or long
lines).

That particular line, when interpreted as quoted-printable, is a
sequence of 22 ASCII/UTF-8 '=' signs.

(ASCII is a 7-bit character set, and is a proper subset of UTF-8,
which is one reason UTF-8 is popular)

| > So, the problem does not come from Mutt nor Ecartis. The only thing wich
| > can cause troubles is an SMTP server. Do you use a local or personnal
| > SMTP server?
| 
| Yes I do use my own postfix mta, but that cannot be the cause, because
| the patch I have sent to you (and to me for that matter) was perfectly
| valid. I guess it is Ecartis. Could you try to resend my patch to the
| list (and cc me) with 

The MTA has nothing to do with it, unless it is horribly broken (which
postfix isn't), and mutt handles MIME just fine.

| Content-type: text/plain; charset=utf-8
| 
| set?

If you look at your message, you'll see the following two headers:

    Content-type: text/plain; charset=utf-8
    Content-Transfer-Encoding: 8bit

This means that:

    a) there is only one section -- the message body
    b) the bytstream directly represents the in character encoding
        with no additional encoding

however neither of these is correct.

Your message is intended to have two parts: the message body and the
patch, and the patch is further encoded using quoted-printable to make
it safe for mail systems that doesn't support the 8BITMIME extension.

I have some recollection from the past that Ecartis doesn't handle
MIME.  In fact, your most recent message seems to confirm that:

| -- Attached file included as plaintext by Ecartis --
| -- File: signature.asc

Your PGP signature was completely wrecked by Ecartis, and Ecartis even
willingly claims the blame.

I expect my signature will be trashed by Ecartis in the same manner.

-Derrick

-- 
The teaching of the wise is a fountain of life,
turning a man from the snares of death.
        Proverbs 13:14
 
www: http://dman13.dyndns.org/                  jabber: dman@xxxxxxxxxxxxxxxxx

-- Attached file included as plaintext by Ecartis --
-- File: signature.asc
-- Desc: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqo2dcACgkQtXbfIkiu82vteQCghQwvwBOvarud0WgjQudlFO5U
a5gAn0Fvi8zreBpW+Tk9ZgPUZ/jZOwyE
=Nxio
-----END PGP SIGNATURE-----