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

[Nicolas Sebrecht <nicolas.s-dev@xxxxxxxxxxx>]

On Thu, Sep 10, 2009 at 06:50:01AM -0400, Derrick Hudson wrote:
> 
> 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.

BTW, I've send the same patch with mutt. These two headers was :

     Content-type: text/plain; charset=iso-8859-1
     Content-Transfer-Encoding: 8bit

and the content looks fine.
 
> Your message is intended to have two parts: the message body and the
> patch

Well, with Git patches are expected to be inline rather than
attachement. Christoph used either 'mutt -H' or 'git send-email' which
both make the patch the body of the mail.

>        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.

AFAICS, it didn't. But it was a good idea.

-- 
Nicolas Sebrecht