Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
To: ding@gnus.org
Subject: Re: [PATCH] private message id
Date: Mon, 29 Nov 2010 13:41:46 -0800	[thread overview]
Message-ID: <8739qjyfhh.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <87fwujreui.fsf%lukasz.stelmach@iem.pw.edu.pl> (=?utf-8?Q?=22?= =?utf-8?Q?=C5=81ukasz?= Stelmach"'s message of "Mon, 29 Nov 2010 22:37:25 +0100")

Łukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> writes:

> I'd like to share an idea, and a patch that implemnts it, to make
> Message-ID slightly worse source of data tracking down an individual who
> uses multiple accounts on one machine. All message get the same fqdn
> part so it is quite obvious they are sent from the same machine.  I
> know, there are Received headers but they are not as easy to parse, and
> may be a lot less accurate behind a NAT.

> I propose a Message-ID consiting of unique-id%e-mail-address grabbed
> from the From header. Take a look at the ID of this message.

In theory, this is a minor violation of best practices for generating
Message-IDs because you're "stealing" message IDs from the space owned by
the e-mail address domain and may conflict with some message ID generation
algorithm used separately by the owner of that domain, thus resulting in
message ID collisions.  In practice, though, the addition of the username
makes that very unlikely, so I doubt it would be a practical problem.

Seems like a fairly good idea to me.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



  reply	other threads:[~2010-11-29 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 21:37 Łukasz Stelmach
2010-11-29 21:41 ` Russ Allbery [this message]
2010-11-30 20:35 ` Lars Magne Ingebrigtsen
2010-12-01  1:10   ` Łukasz Stelmach
2010-12-01 17:09     ` Lars Magne Ingebrigtsen
2010-12-01 23:16       ` Łukasz Stelmach
2010-12-05 12:30         ` Lars Magne Ingebrigtsen
2010-12-06  6:28           ` Łukasz Stelmach
2010-12-06 19:40             ` Lars Magne 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

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

  git send-email \
    --in-reply-to=8739qjyfhh.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    --cc=ding@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.
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 NNTP newsgroup(s).