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: Thu, 30 May 2019 19:02:57 -0400 [thread overview]
Message-ID: <87h89bilzy.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87pnnztwxh.fsf@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-05-31 1:19 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 [this message]
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
-- 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=87h89bilzy.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).