On Sat, 27 Jul 2024 14:33:46 +0200 Walter wrote:
> On Fri, 26 Jul 2024 19:02:21 +0000  Claus Assmann wrote:
> > On Fri, Jul 26, 2024, Walter Alejandro Iglesias wrote:
> > > I've been reading more carefully the standards.  According to rfc6532,
> > > headers can be sent directly in UTF-8, so I ended up discarding the
> >
> > 3.  Changes to Message Header Fields
> > ...
> >    Also note that messages in this format require the use of the
> >    SMTPUTF8 extension [RFC6531] to be transferred via SMTP.
> >
> > So your patches require SMTPUTF8 support by all involved MTAs?
>
> Let me rephrase what Claus says here to avoid confusion.  Sending
> non-ASCII characters in headers and body without MIME specifications or
> regard for what MTAs support or don't support is what mail(1) currently
> does.  What is debatable is to what extent my patches should address
> this problem, given that we're not talking about Mutt and certainly not
> Thunderbird and the minimalist approach of this project.
>

Standards aside, I know that sending UTF-8 in the message body without
including the Content-Type and Content-Transfer-Encoding headers affects
how MUAs (e.g. Mutt) display the body.  What I don't know for sure yet
is whether sending UTF-8 headers can "really" cause any problems,
whether you're sending messages through servers that don't support the
SMTPUTF8 extension or not.  So far I've sent test messages to the Gmail,
Hotmail, and Yahoo accounts I have, and also to my hosting email server,
and they don't seem to have any issues with this.  If anyone has
experienced this problem with any mail server let me know, please.