From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Make Message more RFC compliant
Date: Sat, 14 Apr 2018 16:27:55 +0300 [thread overview]
Message-ID: <83lgdp5350.fsf@gnu.org> (raw)
In-Reply-To: <87po32j5x1.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Sat, 14 Apr 2018 15:04:10 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-devel@gnu.org
> Date: Sat, 14 Apr 2018 15:04:10 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I don't understand why we need to remove the support code. Making the
> > variable obsolete is OK, but if there's someone out there whose bad
> > habits die hard, or who needs to communicate with some weirdo mail
> > software that requires this obsolete format, why not let them do it?
> >
> > Or am I missing something?
>
> Well, sending emails with the old format is now apparently in violation
> ("SHOULD") of the relevant RFCs, and I think Emacs should be
> standards-compliant when talking to other systems, and not generate
> invalid emails.
Sorry, I'm not convinced. If the user insists on using deprecated
features, I see no reason to prevent them just because some RFC says
SHOULD. Our defaults should not generate invalid or frowned-upon
headers, but that and the obsolescence of the variable is more than
enough for us to be OK with the standards.
next prev parent reply other threads:[~2018-04-14 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 21:27 Make Message more RFC compliant Lars Ingebrigtsen
2018-04-14 6:36 ` Eli Zaretskii
2018-04-14 13:04 ` Lars Ingebrigtsen
2018-04-14 13:27 ` Eli Zaretskii [this message]
2018-04-14 13:52 ` Lars Ingebrigtsen
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=83lgdp5350.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).