From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Jorge P. de Morais Neto" <jorge+list@disroot.org>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: viewing duplicate messages
Date: Sun, 18 Aug 2019 16:20:08 -0400 [thread overview]
Message-ID: <87mug6kyyv.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87k1bb8mr9.fsf@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 2057 bytes --]
On Sat 2019-08-17 19:12:26 -0300, Jorge P. de Morais Neto wrote:
> I have attached a tarball with three homonymous messages from Dell. The
> last (most recent) two have the same subject and bodies, but the first
> (earliest) one is different and yet they all have Message-Id 1. I have
> included the Notmuch list as a recipient because the tarball is a mere
> 11252B.
thanks for this. Looking at the headers, it occurs to me that the
problem might actually be that Dell ("idd_messaging_email@dell.com")
might not including a message-id header at all, and it is being added
their IronPort/Sophos AV client as it passes through their mail system.
I suspect this possibility because the placement of the Message-ID
header itself is supiciiously high up in the list of headers (it looks
like it might have been placd there by the initial relaying MTA, rather
than the MUA).
If this is the case, it could be solved in one of two ways: they could
inject a proper unique Message-ID before handing the message off to
IronPort; or they could fix their IronPort appliance to inject a proper
unique Message-ID header.
That's all about fixing it on the sender side though. Are there
possible fixes on the receiving side?
one thought is that notmuch could treat an obviously low-entropy
message-ID the same way that it treats a message with no Message-ID at
all. Of course, that raises the question: what is a low-entropy message
ID? A single-character message-id is pretty clearly too low-entropy to
be useful, but if we said "1-character long" was too short, it would at
least avoid this particular mistake.
i also note that NEWS claims (in the section for notmuch 0.17) that
notmuch treats "overlong" message-ids in the same way as missing
message-ids, but i don't see where that distinction is done in the code.
It doesn't appear to be in lib/message-file.c, where the notmuch-sha1-*
generation is done. But anyway, if we are treating "overlong"
message-ids as missing, it's nicely symmetric to treat "overshort"
message-ids in the same way.
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-08-19 3:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 16:34 viewing duplicate messages Rollins, Jameson
2019-05-30 22:11 ` Jorge P. de Morais Neto
2019-05-30 22:17 ` Rollins, Jameson
2019-05-30 23:02 ` Daniel Kahn Gillmor
2019-05-31 15:45 ` Jorge P. de Morais Neto
2019-05-31 16:32 ` Daniel Kahn Gillmor
2019-08-17 22:12 ` Jorge P. de Morais Neto
2019-08-18 20:20 ` Daniel Kahn Gillmor [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-17 14:50 drebs
2019-07-17 15:08 ` Georg Faerber
2019-07-29 1:07 ` Daniel Kahn Gillmor
2019-07-29 13:34 ` Georg Faerber
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mug6kyyv.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=jorge+list@disroot.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).