DKIM fails depending on Content-Transfer-Encoding

[fi at igh.de]

Hello Ed, 

On 2023-09-06 14:46, Ed Blackman wrote:
> On Wed, Sep 06, 2023 at 01:33:30PM +0200, fi at igh.de wrote:
> > Can I force Mutt to use quoted-printable or base64 by default for
> > encoding of plain text?
> 

> It would be better to fix the DKIM problem, but as I have no idea
> about that, I'll tell you how I force q-p encoding: include a
> non-ASCII space in my signature.

> The space between my first and last name in my signature is a
> non-breaking space, eg   in HTML.  In vim I used
> <ctrl-k><space><space> to insert it.  The non-ASCII character in the
> message body tickles mutt to send the message encoded as
> quoted-printable.

Thank you for this hint. Unfortunately it does not work for me. Mutt
insists in 8bit, maybe depending on my locales. Seems I have to study
the source code...




Best Regards

Torsten


> Ed Blackman

-- 
------------------------------------------------------------------------
Torsten Finke
fi at igh.de
------------------------------------------------------------------------