From: Tom Prince <email@example.com>
To: Jeremy Nickurak <firstname.lastname@example.org>,
Subject: Re: a DoS vulnerability associated with conflated Message-IDs?
Date: Sat, 10 Mar 2012 12:38:44 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
On Thu, 8 Mar 2012 10:38:32 -0700, Jeremy Nickurak <firstname.lastname@example.org> wrote:
> On Thu, Mar 8, 2012 at 10:16, Daniel Kahn Gillmor <email@example.com> wrote:
> > Any other suggestions or ideas?
> What about representing the contents from both message in one apparent message?
> - ...
> - If the bodies disagree, display both.
We'd probably need to do some like doing a diff. I find it annoying
enough displaying both text and html copies of a mail. Displaying two
copies of a message, just because one of them has a few extra lines as a
footer would be equally annoying.
Maybe it would be enough to ignore the signature too, when comparing messages?
next prev parent reply other threads:[~2012-03-10 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 16:37 a DoS vulnerability associated with conflated Message-IDs? Daniel Kahn Gillmor
2012-03-08 17:04 ` James Vasile
2012-03-08 17:16 ` Daniel Kahn Gillmor
2012-03-08 17:38 ` Jeremy Nickurak
2012-03-10 17:38 ` Tom Prince [this message]
2012-10-29 11:15 ` Peter Wang
2017-08-04 20:42 ` David Bremner
2017-08-04 22:15 ` Daniel Kahn Gillmor
2022-07-30 12:41 ` David Bremner
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:
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).