Send again

David

On Sun, Jan 15, 2023, 19:50 Jigme Datse <jra...@armispiansystems.ca> wrote:

> On Sat, 14 Jan 2023 10:25:27 +0000
> Peter Humphrey <pe...@prh.myzen.co.uk> 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.
>
> This seems like it might be a problem.  A lot of the time when I get
> "weird bounces" for messages for a mailing list, it isn't the list, but
> somewhere down the line, which is bouncing because they either aren't
> properly handling mailing lists, or something else (like in this
> example given, failing to properly handle forwarding "bouncing onward"
> sort of as the PINE parlance was used) list messages.
>
> > > 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?
>
> The message *to* you?  I don't think so.  Or it might be someone
> sending from a server which somehow throws something into the header
> that causes it to be bounced that the list manager doesn't properly
> deal with?
>
> > > 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.
> >
> >
>
>

Reply via email to