public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Branko Grubic <bitlord0xff@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Bouncing Messages
Date: Thu, 1 Mar 2018 23:48:27 +0100	[thread overview]
Message-ID: <20180301234827.5a070e07@x220.linux.gnu> (raw)
In-Reply-To: <aa78567a-3db9-2749-19bf-a280027e87f1@gmail.com>

On Thu, 1 Mar 2018 16:38:42 -0600
Dale <rdalek1967@gmail.com> wrote:

> Branko Grubic wrote:
> > On Thu, 1 Mar 2018 14:42:35 -0600
> > R0b0t1 <r030t1@gmail.com> wrote:
> >  
...
> 
> 
> I have got a couple recently as well.  I wonder, can this be used to
> retrieve those messages somehow??
> 
> 
> Here is the list of the bounced messages:
> - 182748
> - 182749
> - 182751
> 
> 
> I keep my messages locally so when I miss messages, it can throw a
> thread into some random weirdness.  If one uses the web interface to
> read/reply etc then it wouldn't matter but for those who use email
> software, it seems we are missing something.  
> 
> I might also wonder, what happened to 182750??  
...

I have no idea, does it mean it bounced, and mailing list software did
re-send them later or not. I don't see a way to use those numbers to
find out which email message relates to the number. So no answer for
any of those.

But what is interesting is that all of us use gmail.

It could be that gmail is receiving a lot of messages from
lists.gentoo.org and that triggers some spam protection? :(

Regards,
Branko



  reply	other threads:[~2018-03-01 22:52 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 [this message]
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 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=20180301234827.5a070e07@x220.linux.gnu \
    --to=bitlord0xff@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