Re: [gentoo-user] Re: Bouncing messages
Dave On Wed, Jan 18, 2023, 18:20 Dale wrote: > Grant Taylor wrote: > > On 1/18/23 8:07 AM, Neil Bothwick wrote: > >> You can also request redelivery of messages based on the internal > >> numbers if you follow the help advice in all list message headers. > > > > The problem is that if the message is rejected because of filtering > > the first time around, there's a very good chance that it will also be > > filtered on subsequent re-delivery requests. > > > > > > > > > I might add, in the past I followed the instructions to get bounced > messages, I've never once had it work. I don't get a error or anything > either, like I do if I do something wrong doing something else. > > Just a FYI. > > Dale > > :-) :-) > >
Re: [gentoo-user] Re: Bouncing messages
Grant Taylor wrote: > On 1/18/23 8:07 AM, Neil Bothwick wrote: >> You can also request redelivery of messages based on the internal >> numbers if you follow the help advice in all list message headers. > > The problem is that if the message is rejected because of filtering > the first time around, there's a very good chance that it will also be > filtered on subsequent re-delivery requests. > > > I might add, in the past I followed the instructions to get bounced messages, I've never once had it work. I don't get a error or anything either, like I do if I do something wrong doing something else. Just a FYI. Dale :-) :-)
Re: [gentoo-user] Re: Bouncing messages
On 1/18/23 8:07 AM, Neil Bothwick wrote: You can also request redelivery of messages based on the internal numbers if you follow the help advice in all list message headers. The problem is that if the message is rejected because of filtering the first time around, there's a very good chance that it will also be filtered on subsequent re-delivery requests. -- Grant. . . . unix || die
Re: [gentoo-user] Re: Bouncing messages
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! pgpdEJ9wdop1k.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: Bouncing messages
On 1/18/23 06:44, Peter Humphrey wrote: On Wednesday, 18 January 2023 08:59:21 GMT Nuno Silva 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. Jack
Re: [gentoo-user] Re: Bouncing messages
On Wednesday, 18 January 2023 08:59:21 GMT Nuno Silva wrote: > And *now* I haven't received one of these messages I was talking about > (which would usually appear for every post of mine to the list, albeit > possibly delayed by a few hours), so I guess either the forwarding > problem was fixed or that person is not subscribed to the list anymore. I've just had another one. [...] > So it is delivery *to* you that's failing? Hm, seeing you mentioned one > of these message numbers that are internal to the list, I think I now > understand what kind of bounce message you're talking about, sorry for > the confusion. > > 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. -- Regards, Peter.
[gentoo-user] Re: Bouncing messages
On 2023-01-14, Peter Humphrey wrote: > On Saturday, 14 January 2023 07:00:29 GMT Nuno Silva wrote: >> On 2023-01-13, Peter Humphrey wrote: >> > Hello list, >> > >> > Ever since the new year I've been getting a bounce message from this list >> > - 19 of them so far. The first of those listed one message twice, most of >> > the others six times. The message was 200359. >> > >> > I don't know what that message was, but why is the system Out There > having >> > such a hard time with it? >> >> Was the message from the list software or from a Microsoft system? > > I don't know - I haven't received it as far as I know. The only archive > entries I've found are of this conversation. And *now* I haven't received one of these messages I was talking about (which would usually appear for every post of mine to the list, albeit possibly delayed by a few hours), so I guess either the forwarding problem was fixed or that person is not subscribed to the list anymore. >> There's possibly one subscriber that has configured their >> Exchange/Outlook account to forward e-mails to a Gmail account, and >> forwarding as implemented by Microsoft apparently isn't done correctly >> and so "SPF" checks run by Gmail are failing. > > Hmm. Would that cause the message to me to fail, in particular? No, in the case I was writing about, it'd only cause you to get these failure messages/reports delivered to you, I think precisely because of the incorrect Microsoft forwarding implementation that'd present you as the sender. So it is delivery *to* you that's failing? Hm, seeing you mentioned one of these message numbers that are internal to the list, I think I now understand what kind of bounce message you're talking about, sorry for the confusion. 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 tried to send a message to this list about this topic back in November >> but it never made through, perhaps it was filtered because it quoted >> some of the error messages. -- Nuno Silva
