From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Marcin Borkowski <mbork@mbork.pl>, 22754@debbugs.gnu.org
Subject: bug#22754: 25.1.50; Rmail does not follow RFC 2822
Date: Mon, 22 Feb 2016 13:14:53 -0500 [thread overview]
Message-ID: <osegc43942.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <838u2enjc8.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Feb 2016 18:01:27 +0200")
Eli Zaretskii wrote:
>> From: Marcin Borkowski <mbork@mbork.pl>
>> Date: Sun, 21 Feb 2016 11:28:27 +0100
>>
>> Rmail inserts lower-case field names in the header, which goes against
>> RFC 2822 (pp. 22 and 23, see
>> https://tools.ietf.org/html/rfc2822#page-22). It seems that the problem
>> affects Cc: and In-reply-to: fields.
>
> I use Rmail all the time, and these headers are capitalized in my
> reply messages. So please provide a recipe starting from "emacs -Q",
> there could be some other factor at work here.
I assume it was a theoretical analysis...
With sendmail-user-agent, mail-setup inserts "Cc" and "In-reply-to"
directly (apparently the latter should be "In-Reply-To"?), ignoring the
case passed via other-headers.
With message-user-agent, message-mail explicitly uses capitalize on all
headers.
I suppose there's no guarantee that some other mail-user-agent won't use
the headers as supplied, but perhaps that would be a bug in the
user-agent?
next prev parent reply other threads:[~2016-02-22 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 10:28 bug#22754: 25.1.50; Rmail does not follow RFC 2822 Marcin Borkowski
2016-02-21 15:42 ` Andy Moreton
2016-02-21 16:01 ` Eli Zaretskii
2016-02-22 18:14 ` Glenn Morris [this message]
2016-02-22 19:23 ` Eli Zaretskii
2016-02-22 20:13 ` Marcin Borkowski
2016-02-23 0:09 ` Glenn Morris
2016-02-23 12:58 ` Marcin Borkowski
2016-02-26 17:43 ` Glenn Morris
2016-02-26 18:17 ` Marcin Borkowski
2016-02-28 3:04 ` Glenn Morris
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=osegc43942.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=22754@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mbork@mbork.pl \
/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).