Re: [PATCH 1/1] send-email: fix transferencoding config option

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Apr 10, 2019, 22:42 UTC
Message-ID: <20190410224250.GJ12419@genre.crustytoothpaste.net>
In-Reply-To: <668fc68f-4d94-39e8-256d-55229472761f@gmx.de>

On Wed, Apr 10, 2019 at 10:40:51PM +0200, Heinrich Schuchardt wrote:

Show 8 quoted lines

> Sounds reasonable. But including the tests requested nothing I could
> easily shoulder.
> 
> Just a quite different thought:
> 
> 'auto' should discover a safe transfer encoding. Why does 'auto' not
> discover that a patch contains carriage returns and should be base64
> encoded (see subroutine apply_transfer_encoding())?

Because nobody thought of it. The original rationale for "auto" was to replace "8bit" with something sane that worked due to long lines as an alternative to forcing people to choose it themselves.

And as the commit message says:

  Choose quoted-printable instead of base64, since base64-encoded plain
  text is treated as suspicious by some spam filters.

I'll try to see if I can write something up to handle this better. If quoted-printable works, I'll pick that; otherwise, I'll choose base64.

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204