From: Dan Jacobson <jidanni@jidanni.org>
Cc: md@linux.it
Subject: stop rewriting Message-IDs
Date: Thu, 25 Sep 2003 05:46:59 +0800 [thread overview]
Message-ID: <87oex9voz0.fsf_-_@jidanni.org> (raw)
In-Reply-To: <3F6F155C.4010606@yahoo.com> (Kevin Rodgers's message of "Mon, 22 Sep 2003 09:29:32 -0600")
Dear bug-gnu-emacs: again: for RFC compliant Message-IDs, there is no
reason for bug-gnu-emacs's mailman to rewrite them.
For instance, here reading from gmane.org NNTP, my message has
References: <mailman.443.1064004252.21628.bug-gnu-emacs@gnu.org>
<3F6F155C.4010606@yahoo.com>
however mailman.443.1064004252.21628.bug-gnu-emacs@gnu.org is how my
article looks to Kevin, but that article can't be found on gmane. The article's
original rightful Message-ID is what is on gmane.
There is no justification for rewriting Message-IDs other than being
too lazy to use a regexp to see if the Message-IDs is RFC compliant.
And it's creating a big mess.
I sent a message to the maintainers last year.
next prev parent reply other threads:[~2003-09-24 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.443.1064004252.21628.bug-gnu-emacs@gnu.org>
2003-09-22 15:29 ` report-emacs-bug could also list current modes Kevin Rodgers
2003-09-24 21:46 ` Dan Jacobson [this message]
2003-09-24 21:50 ` Dan Jacobson
[not found] ` <mailman.677.1064447066.21628.bug-gnu-emacs@gnu.org>
2003-09-25 14:55 ` Kevin Rodgers
2003-09-25 16:16 ` Andreas Schwab
2003-09-27 4:59 ` describe-mode should first summarize all modes in effect Dan Jacobson
[not found] ` <mailman.819.1064714879.21628.bug-gnu-emacs@gnu.org>
2003-09-29 17:10 ` Kevin Rodgers
2003-10-02 22:27 ` Dan Jacobson
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=87oex9voz0.fsf_-_@jidanni.org \
--to=jidanni@jidanni.org \
--cc=md@linux.it \
/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).