Gentoo Archives: gentoo-user

From: David Rosenbaum <rosenbaumd181@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: Bouncing messages
Date: Mon, 16 Jan 2023 12:03:55
Message-Id: CAL+8hePy=LsQSQoKTDjjTFzVCm_LXCubXPtuQDAE2h292Qnu=Q@mail.gmail.com
In Reply to: Re: [gentoo-user] Re: Bouncing messages by Jigme Datse
1 Send again
2
3 David
4
5 On Sun, Jan 15, 2023, 19:50 Jigme Datse <jrasku@××××××××××××××××.ca> wrote:
6
7 > On Sat, 14 Jan 2023 10:25:27 +0000
8 > Peter Humphrey <peter@××××××××××××.uk> wrote:
9 >
10 > > On Saturday, 14 January 2023 07:00:29 GMT Nuno Silva wrote:
11 > > > On 2023-01-13, Peter Humphrey wrote:
12 > > > > Hello list,
13 > > > >
14 > > > > Ever since the new year I've been getting a bounce message from
15 > > > > this list
16 > > > > - 19 of them so far. The first of those listed one message twice,
17 > > > > most of the others six times. The message was 200359.
18 > > > >
19 > > > > I don't know what that message was, but why is the system Out
20 > > > > There
21 > > having
22 > > > > such a hard time with it?
23 > > >
24 > > > Was the message from the list software or from a Microsoft system?
25 > >
26 > > I don't know - I haven't received it as far as I know. The only
27 > > archive entries I've found are of this conversation.
28 >
29 > This seems like it might be a problem. A lot of the time when I get
30 > "weird bounces" for messages for a mailing list, it isn't the list, but
31 > somewhere down the line, which is bouncing because they either aren't
32 > properly handling mailing lists, or something else (like in this
33 > example given, failing to properly handle forwarding "bouncing onward"
34 > sort of as the PINE parlance was used) list messages.
35 >
36 > > > There's possibly one subscriber that has configured their
37 > > > Exchange/Outlook account to forward e-mails to a Gmail account, and
38 > > > forwarding as implemented by Microsoft apparently isn't done
39 > > > correctly and so "SPF" checks run by Gmail are failing.
40 > >
41 > > Hmm. Would that cause the message to me to fail, in particular?
42 >
43 > The message *to* you? I don't think so. Or it might be someone
44 > sending from a server which somehow throws something into the header
45 > that causes it to be bounced that the list manager doesn't properly
46 > deal with?
47 >
48 > > > I tried to send a message to this list about this topic back in
49 > > > November but it never made through, perhaps it was filtered because
50 > > > it quoted some of the error messages.
51 > >
52 > >
53 >
54 >