From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Bouncing messages
Date: Wed, 18 Jan 2023 15:07:14 +0000 [thread overview]
Message-ID: <20230118150714.362d7481@digimed.co.uk> (raw)
In-Reply-To: <3801a02c-2b8a-eb9f-918f-b4f352508db5@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
On Wed, 18 Jan 2023 08:51:10 -0500, Jack wrote:
> >> Now was there (I recall asking about this previously, but I forgot
> >> what the answer was) a way to get a message-ID from that internal
> >> number, or at least a way to get the address of the message's
> >> archive copy on the gentoo website?
> > I haven't found it, if so.
>
> Some time back I traded some emails with a sysadmin about this, and I'm
> pretty sure there is no way to make that translation. The number is
> internal to the list software database and is apparently not surfaced
> anywhere except such messages. In my case, I was usually able to to to
> the archive page for the list, and by displaying as messages (instead
> of threads) identify the one I never received.
You can also request redelivery of messages based on the internal numbers
if you follow the help advice in all list message headers.
--
Neil Bothwick
Hard work has a future payoff. Laziness pays off NOW!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-18 15:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 10:12 [gentoo-user] Bouncing messages Peter Humphrey
2023-01-14 7:00 ` [gentoo-user] " Nuno Silva
2023-01-14 10:25 ` Peter Humphrey
2023-01-14 10:41 ` [gentoo-user] Remove NetworkManager without breaking cinnamon ? mehdi chemloul
2023-01-15 10:05 ` Michael
2023-01-16 0:48 ` [gentoo-user] Re: Bouncing messages Jigme Datse
2023-01-16 12:03 ` David Rosenbaum
2023-01-18 8:59 ` Nuno Silva
2023-01-18 11:44 ` Peter Humphrey
2023-01-18 13:51 ` Jack
2023-01-18 15:07 ` Neil Bothwick [this message]
2023-01-18 23:02 ` Grant Taylor
2023-01-18 23:19 ` Dale
2023-01-19 0:05 ` David Rosenbaum
2023-01-20 5:59 ` Grant Taylor
2023-01-20 9:07 ` Dale
2023-01-20 14:44 ` Grant Taylor
2023-01-20 16:09 ` Peter Humphrey
2023-01-20 17:18 ` Grant Taylor
2023-01-20 12:20 ` Dr Rainer Woitok
2023-01-28 8:19 ` Nuno Silva
2023-01-19 8:56 ` Nuno Silva
2023-01-19 9:30 ` Peter Humphrey
2023-01-22 22:33 ` Peter Humphrey
2023-01-22 23:04 ` Michael
2023-01-24 13:03 ` Peter Humphrey
-- strict thread matches above, loose matches on Subject: below --
2018-03-01 20:42 [gentoo-user] Bouncing Messages R0b0t1
2018-03-01 20:45 ` Branko Grubic
2018-03-01 22:38 ` Dale
2018-03-01 22:48 ` Branko Grubic
2018-03-01 23:53 ` [gentoo-user] " Ian Zimmerman
2018-03-02 0:12 ` Dale
2018-03-02 3:23 ` Ian Zimmerman
2018-03-02 4:21 ` Ian Zimmerman
2018-03-02 4:45 ` [gentoo-user] " Floyd Anderson
2018-03-02 5:28 ` Dale
2018-03-02 11:04 ` Floyd Anderson
2018-03-02 16:36 ` [gentoo-user] " Ian Zimmerman
2018-03-02 22:51 ` Grant Taylor
2018-03-03 0:47 ` Ian Zimmerman
2018-03-03 3:06 ` Grant Taylor
2018-03-01 21:04 ` Ian Zimmerman
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=20230118150714.362d7481@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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