all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: nljlistbox2@gmail.com (N. Jackson)
To: 23432@debbugs.gnu.org
Subject: bug#23432: 25.0.93; Email from Gnus now going out with Message-IDs @gmail.com
Date: Wed, 04 May 2016 15:31:08 -0300	[thread overview]
Message-ID: <87mvo5brpv.fsf@moondust.awandering> (raw)
In-Reply-To: <wuh9edag5y.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 04 May 2016 13:26:01 -0400")

At 13:26 -0400 on Wednesday 2016-05-04, Glenn Morris wrote:
>
> I added a sentence to NEWS.

Thanks Glenn.

However, I don't believe this is enough.

This is an extremely egregious flaw. Inserting an inappropriate string like
"i-did-not-set--mail-host-address--so-tickle-me" in Emacs users' email
messages, without asking their permission and without informing them, is
unacceptable.

If the "fix" is to document the danger in NEWS, then it should be in the
sections on Message and Gnus. No one is going to think to look under
`system-name'. After all, even the person who made this change to
`system-name' clearly didn't make the connection that it would effect
users's Message-IDs; there's no reason to expect a casual email user to
make that connection.

> (Should name.localdomain even have counted as valid for a message-id in
> the first place? The point is to be unique.)

Well, that's just the suffix of the Message-ID. The full thing would be,
for example, something like 877ff9dc26.fsf@moondust.localhost. Clearly
not unique like a GUID, but having a high probability of uniqueness.

N.






  reply	other threads:[~2016-05-04 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03  7:34 bug#23432: 25.0.93; Email from Gnus now going out with Message-IDs @gmail.com N. Jackson
2016-05-03 20:13 ` Glenn Morris
2016-05-04  0:59   ` N. Jackson
2016-05-04 14:50     ` Eli Zaretskii
2016-05-04 16:26       ` N. Jackson
2016-05-04 17:26         ` Glenn Morris
2016-05-04 18:31           ` N. Jackson [this message]
2016-05-04 21:27             ` Phillip Lord
2016-05-05  0:10               ` N. Jackson
2016-05-04 22:15             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mvo5brpv.fsf@moondust.awandering \
    --to=nljlistbox2@gmail.com \
    --cc=23432@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.