Well, I truly suspect it has more to do with certificate authorities at a broader scale, and your insights are on the right track at least for this mailing list. Virtually anything can be flagged as offensive content with some metadata we'll never see, so perhaps one bad egg keeps reporting this list and we wouldn't know. Could also be Google's shit tier ML making bad judgements. I suspect we're all kind of working thru this even if we understand the algorithms behind it all. To Ben's point about what he's seeing in logs with legit mail server acks, if you will, in a way its business as usual. This is why big organizations used to outright block entire /16 networks - some new jerk out east would fire a shot and make services go poof. My account with Gmail goes back to being a beta tester of their service, so I suppose I could blow my stack and wake 'em up if there's a deeper technical problem here we can unearth. On Fri, Feb 13, 2026, 2:32 p.m. Eric Marceau via sigs-l3go < sigs-l3go [ at ] linux-ottawa [ dot ] org> wrote: > I don't know enough to ask if this is relevant or not: > > If the exploded mailing list was in the *bcc:* distribution, vs the *cc:* > or *to:* lists, > > - would that somehow bypass the fencing logic preventing proper use of > the service, or > > - is the "sigs-l3go [ at ] linux-ottawa [ dot ] org" <sigs-l3go [ at ] linux-ottawa [ dot ] org> > address itself being "discriminated" against because it is a ".org", or > > - is the hosting service "linux-ottawa.org" being discriminated > against because that domain specifically has been flagged as offensive? > > ... or maybe I completely misunderstood the gist of this conversation! :-( >