Hi Kevin,
On 2023-09-07 20:07, Kevin J. McCarthy wrote:
> On Thu, Sep 07, 2023 at 11:57:09AM +0200, f...@igh.de wrote:
> > 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...
>
>
On Thu, Sep 07, 2023 at 11:57:09AM +0200, f...@igh.de wrote:
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...
See if 'unset allow_8bit' helps.
--
Kevin J. McCarthy
GPG Fingerprint:
Hello Ed,
On 2023-09-06 14:46, Ed Blackman wrote:
> On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@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,
Hello Raf,
On 2023-09-07 10:31, raf via Mutt-users wrote:
> On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@igh.de wrote:
>
> > Dear Mutt Users
> >
> > recently I experienced DKIM fails that depend on the
> > Content-Transfer-Encoding of messages text part.
> >
> > Being a german I use to
On 2023-09-07, raf via Mutt-users wrote:
> On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@igh.de wrote:
>
>> Dear Mutt Users
>>
>> recently I experienced DKIM fails that depend on the
>> Content-Transfer-Encoding of messages text part.
>>
>> Being a german I use to write my messages in german
On Thu, Sep 07, 2023 at 10:31:53AM +1000, raf via Mutt-users wrote:
> Hi, This has come up recently in the Postfix mailing list. MTAs can
> convert 8bit messages when sending to another MTA that doesn't
> advertise that it can accept 8bit. If the DKIM signing happens
> before the conversion,
On Wed, Sep 06, 2023 at 04:28:46PM +0200, f...@igh.de wrote:
> works perfectly if the subject contains any non-ASCII characters.
I think this case is not relevant, because any non-ascii characters
in the Subject are converted to use the RFC-2047 scheme, I guess
already in mutt.
--
Ian
On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@igh.de wrote:
> Dear Mutt Users
>
> recently I experienced DKIM fails that depend on the
> Content-Transfer-Encoding of messages text part.
>
> Being a german I use to write my messages in german with UTF-8
> encoding. I prefer plain text. My
On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@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
Dear Jan,
On 2023-09-06 15:25, Jan Eden via Mutt-users wrote:
> On 2023-09-06 13:33, f...@igh.de wrote:
>
> > Dear Mutt Users
> >
> > recently I experienced DKIM fails that depend on the
> > Content-Transfer-Encoding of messages text part.
> >
> > Being a german I use to write my messages in
On 2023-09-06 13:33, f...@igh.de wrote:
> Dear Mutt Users
>
> recently I experienced DKIM fails that depend on the
> Content-Transfer-Encoding of messages text part.
>
> Being a german I use to write my messages in german with UTF-8
> encoding. I prefer plain text. My e-mails are DKIM signed. I
Dear Mutt Users
recently I experienced DKIM fails that depend on the
Content-Transfer-Encoding of messages text part.
Being a german I use to write my messages in german with UTF-8
encoding. I prefer plain text. My e-mails are DKIM signed. I have
checked DKIM to be set up correctly twice.
By
12 matches
Mail list logo
