From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Bouncing Messages
Date: Thu, 1 Mar 2018 23:28:51 -0600 [thread overview]
Message-ID: <7b80215b-f60b-19c5-1aa4-b962300c59b9@gmail.com> (raw)
In-Reply-To: <20180302044541.3ghfup6pglgds3hd@31c0.net>
Floyd Anderson wrote:
> On Thu, 01 Mar 2018 20:21:52 -0800
> Ian Zimmerman <itz@very.loosely.org> wrote:
>> On 2018-03-01 18:12, Dale wrote:
>>
>>> Here is the list of the bounced messages:
>>> - 182748
>>> - 182749
>>> - 182751
>>
>> If you succeed in retrieving them, please let us know which ones they
>> were, so we can guess as to the cause.
>>
>
> Just send an empty mail to:
>
> <gentoo-user+get-N@lists.gentoo.org>
>
> where ‘N’ is the message number, for instance:
>
> <gentoo-user+get-182749@lists.gentoo.org>
>
> and you should receive the requested mail (182749). I got it within
> one minute.
>
>
Interesting. The plot thickens. I sent mine hours ago and got nothing
yet, other than the recent replies which are in sequence so far. This
is what I sent to get them:
gentoo-user+get-182748@lists.gentoo.org
gentoo-user+get-182749@lists.gentoo.org
gentoo-user+get-182751@lists.gentoo.org
Those look like the same format as yours. Wonder why I haven't got
anything yet? Am I missing something? I wonder if google is blocking
them. I have to BCC myself to get my replies since google sends them to
/dev/null otherwise. Annoying thing. I keep saying I'm going to get a
real email but it's always next week, which never seems to get here. :/
Dale
:-) :-)
next prev parent reply other threads:[~2018-03-02 5:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2018-03-02 11:04 ` Floyd Anderson
2018-03-02 16:36 ` [gentoo-user] " Ian Zimmerman
2018-03-02 18:25 ` [gentoo-user] " Floyd Anderson
2018-03-02 22:51 ` [gentoo-user] " Grant Taylor
2018-03-03 0:47 ` Ian Zimmerman
2018-03-03 3:06 ` Grant Taylor
2018-03-03 14:47 ` [gentoo-user] " Stroller
2018-03-03 19:00 ` Grant Taylor
2018-03-03 19:22 ` Grant Taylor
2018-03-04 12:45 ` Stroller
2018-03-04 17:18 ` Grant Taylor
2018-03-02 21:52 ` Dale
2018-03-02 23:08 ` Grant Taylor
2018-03-02 23:59 ` Dale
2018-03-03 0:42 ` Grant Taylor
2018-03-02 0:24 ` Neil Bothwick
2018-03-02 2:00 ` Dale
2018-03-03 15:26 ` J. Roeleveld
2018-03-01 21:04 ` [gentoo-user] " Ian Zimmerman
2018-03-02 15:26 ` [gentoo-user] " Branko Grubic
2018-03-02 16:28 ` Daniel Frey
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 10:12 [gentoo-user] Bouncing messages Peter Humphrey
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=7b80215b-f60b-19c5-1aa4-b962300c59b9@gmail.com \
--to=rdalek1967@gmail.com \
--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