Re: viewing duplicate messages
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_em...@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
signature.asc
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Re: viewing duplicate messages
Em 2019-05-30T19:02:57-0400, Daniel Kahn Gillmor escreveu: > Have you reported this to Dell? This sounds like something that anyone > at Dell who understands the technical issues would want to fix. If > you've reported it publicly, i'd appreciate a pointer to the discussion. I have just sent an email to a Dell saleswoman I had previously corresponded with. I asked her to forward the report to the appropriate organizational unit and tell me the ticket identifier should a ticket be created. This was the only contact channel I found; I first looked into Dell's website and found no better option. > If you'd care to forward me a zipfile containing examples of at least > two distinct messages with the same message ID, i'd love to look through > a copy of this sort of confusion. It's good to understand the different > ways these sort of things go wrong. dell_homonymous_messages.tar.xz Description: application/xz 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. Regards -- - I am Brazilian. I hope my English is correct and I welcome feedback - Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z - Free/libre software for Android: https://f-droid.org/ - [[https://www.gnu.org/philosophy/free-sw.html][What is free software?]] ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: viewing duplicate messages
Hi, On 19-07-28 21:07:56, Daniel Kahn Gillmor wrote: > fwiw, i don't think setting keep_msgid: false in schleuder is a good > answer, because setting it causes pretty nasty threading failures. > hopefully we can think through a better approach for dealing with this > from the client side. I fully agree, and probably should have made this more clearer in my mail. :) Cheers, Georg ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: viewing duplicate messages
On Wed 2019-07-17 15:08:49 +, Georg Faerber wrote: > On 19-07-17 14:50:50, drebs wrote: >> When I send a message to a schleuder list, it is first encrypted to >> the list's OpenPGP certificate before leaving my computer. Schleuder >> will then decrypt it and re-encrypt to the subscribers' certificates, >> and it will maintain the Message-Id untouched. > > FWIW: That's configurable, see [1]. Unfortunately, that's currently the > only place which documents this kind of stuff. fwiw, i don't think setting keep_msgid: false in schleuder is a good answer, because setting it causes pretty nasty threading failures. hopefully we can think through a better approach for dealing with this from the client side. --dkg signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: viewing duplicate messages
Hi drebs, all, Just a short note on this: On 19-07-17 14:50:50, drebs wrote: > When I send a message to a schleuder list, it is first encrypted to > the list's OpenPGP certificate before leaving my computer. Schleuder > will then decrypt it and re-encrypt to the subscribers' certificates, > and it will maintain the Message-Id untouched. FWIW: That's configurable, see [1]. Unfortunately, that's currently the only place which documents this kind of stuff. Cheers, Georg [1] https://0xacab.org/schleuder/schleuder/blob/191b5122403942496490e532e48a290d7dd0cd98/etc/list-defaults.yml#L49 signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: viewing duplicate messages
On Fri 2019-05-31 12:45:46 -0300, Jorge P. de Morais Neto wrote: > I have searched and found no copy. That's because I physically delete > these Dell notification messages after reading and acting on them. This > way there is always 0 or 1 such message, so Notmuch does not get > confused. But I will save the next ones and give you. In fact, in an > attempt to temporarily increase the frequency of notifications, I have > just subscribed to notifications about everything related to my notebook > series, even MS-Windows drivers. thanks! i don't mean to interrupt your workflow, which makes total sense to me. feel free to send them to me as they come in. --dkg signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: viewing duplicate messages
Daniel Kahn Gillmor writes: > Have you reported this to Dell? Not yet. > If you'd care to forward me a zipfile containing examples of at least > two distinct messages with the same message ID, i'd love to look through > a copy of this sort of confusion. It's good to understand the different > ways these sort of things go wrong. I have searched and found no copy. That's because I physically delete these Dell notification messages after reading and acting on them. This way there is always 0 or 1 such message, so Notmuch does not get confused. But I will save the next ones and give you. In fact, in an attempt to temporarily increase the frequency of notifications, I have just subscribed to notifications about everything related to my notebook series, even MS-Windows drivers. Regards -- - I am Brazilian. I hope my English is correct and I welcome feedback - Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z - Free/libre software for Android: https://f-droid.org/ - [[https://www.gnu.org/philosophy/free-sw.html][What is free software?]] ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: viewing duplicate messages
On Thu 2019-05-30 19:11:22 -0300, Jorge P. de Morais Neto wrote: > I have a Dell laptop and I subscribed to email notifications about > firmware updates. It turns out that Dell sends all such notifications > (which obviously have different content) with the same message-id. Have you reported this to Dell? This sounds like something that anyone at Dell who understands the technical issues would want to fix. If you've reported it publicly, i'd appreciate a pointer to the discussion. If you'd care to forward me a zipfile containing examples of at least two distinct messages with the same message ID, i'd love to look through a copy of this sort of confusion. It's good to understand the different ways these sort of things go wrong. --dkg signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: viewing duplicate messages
"Rollins, Jameson" writes: > It would be nice to have an easy way in notmuch-emacs-show to know if > there are multiple messages with the same message-id in the store, and > to cycle through viewing each individually. That would be useful to me too. I have a Dell laptop and I subscribed to email notifications about firmware updates. It turns out that Dell sends all such notifications (which obviously have different content) with the same message-id. Regards -- - I am Brazilian. I hope my English is correct and I welcome feedback - Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z - Free/libre software for Android: https://f-droid.org/ - [[https://www.gnu.org/philosophy/free-sw.html][What is free software?]] ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: viewing duplicate messages
On Thu, May 30 2019, Jorge P. de Morais Neto wrote: > That would be useful to me too. I have a Dell laptop and I subscribed > to email notifications about firmware updates. It turns out that Dell > sends all such notifications (which obviously have different content) > with the same message-id. [face palm] it's a wonder that the internet works at all... ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
