From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Bouncing messages
Date: Fri, 20 Jan 2023 07:44:24 -0700 [thread overview]
Message-ID: <44cd4db3-d2b2-7d6d-5dce-2e9b453c9cb0@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <7569d51f-6f61-ab52-e559-8bc3343d1db5@gmail.com>
On 1/20/23 2:07 AM, Dale wrote:
> It could be the OP is running into the same problem I have in the
> past, whatever that problems is.
My experience is that this is a combination of advanced email protection
on the sender /and/ the receiver.
E.g. the sending domain's email configuration specifies very specific
locations combined with a receiving domain's email configuration
honoring what the sending domain publishes. Thus when a message passes
through a 3rd party, saying a mailing list, the recipient refuses to
accept the message because it's not from where the sender says the
message is authorized to come from.
There's a lot of minutia to this and lots of ways that this can fail.
Yes, there are some things that the Gentoo Users mailing list can
change, but do to various reasons, this isn't done all the time.
> I might add, I don't recall seeing anything that leads me to believe
> I actually missed any messages. I tent to follow most threads and
> I don't recall ever seeing a quoted message that I don't have the
> original of.
My experience is similar.
> It's odd in my opinion. Maybe someone will figure it out.
I think it's been figured out. This is where "this isn't done all the
time" comes into play.
--
Grant. . . .
unix || die
next prev parent reply other threads:[~2023-01-20 14:46 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
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 [this message]
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=44cd4db3-d2b2-7d6d-5dce-2e9b453c9cb0@spamtrap.tnetconsulting.net \
--to=gtaylor@gentoo.tnetconsulting.net \
--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