unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Make Message more RFC compliant
Date: Sat, 14 Apr 2018 15:04:10 +0200	[thread overview]
Message-ID: <87po32j5x1.fsf@mouse.gnus.org> (raw)
In-Reply-To: <83tvse47lu.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 14 Apr 2018 09:36:45 +0300")

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.

If a user really really needs to send an invalid email, that's also easy
enough without Emacs having direct support for it: Just type in the From
header in the Message buffer, and Message will send out whatever you ask
it to.

We don't control (and don't want to control) what people are allowed to
do, but we can control what we generate.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2018-04-14 13:04 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 [this message]
2018-04-14 13:27     ` Eli Zaretskii
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=87po32j5x1.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).