From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Francesco Potortì" <pot@gnu.org>
Cc: 53412@debbugs.gnu.org
Subject: bug#53412: wrappin text lines is not enough, headers shoould be split too
Date: Mon, 07 Mar 2022 16:57:46 +0100 [thread overview]
Message-ID: <878rtlah6t.fsf@gnus.org> (raw)
In-Reply-To: <8735jtpxuc.fsf@tucano.isti.cnr.it> ("Francesco Potortì"'s message of "Mon, 07 Mar 2022 16:48:59 +0100")
Francesco Potortì <pot@gnu.org> writes:
>>> If there is an overlong header, other headers which are utf-8
>>> escaped are not sent correctly, and the recipient sees something
>>> like this:
>>>
>>> Subject: test =?utf-8?Q?=C3=A0?= b c
>>> =?utf-8?Q?=C3=AC?=
>>
>>That looks correct to me?
>
> No, if that's what the recipent sees in their inbox. I don't know
> why, but mail sent by Emacs with an overlong header (whichever header)
> ends up with recipients seeing that string in their MUA.
They see literally that displayed? Then it sounds like the mail you're
sending out has been double-rfc2047-encoded.
> I can send mail to you or this list to demonstrate the problem, if you
> think that would be useful
Sure.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-03-07 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 15:16 bug#53412: 27.1; sendmail does not wrap overlong lines Francesco Potortì
2022-01-21 19:24 ` Eli Zaretskii
2022-02-20 12:42 ` Lars Ingebrigtsen
2022-03-07 12:35 ` bug#53412: wrappin text lines is not enough, headers shoould be split too Francesco Potortì
2022-03-07 13:11 ` Francesco Potortì
2022-03-07 15:38 ` Lars Ingebrigtsen
2022-03-07 15:48 ` Francesco Potortì
2022-03-07 15:57 ` Lars Ingebrigtsen [this message]
2022-03-07 17:27 ` Andreas Schwab
2022-03-07 17:31 ` Lars Ingebrigtsen
2022-03-07 17:36 ` Francesco Potortì
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rtlah6t.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=53412@debbugs.gnu.org \
--cc=pot@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).