Baptiste Daroussin <b...@freebsd.org> wrote: > No it was not sent to the whole list but only to the people whom mail server > have bounced an incoming mail.
Apologies. I should have checked the header more closely. I've never had one of these before, and I received one the same time as I saw the posting from Matthias about the same thing. > It is not a configuration, this can happen in 2 cases: > - a change in the on your email provider which start bouncing emails (hence > the > fact we don't stop those emails) > - but most case it is due to the antispam on your provider side, when a spam > managed to passthrough our (freebsd) antispam infrastructure. I run my own mailservers - The only antispam measure I use is the spamhaus SBL. I just checked the log - my end refused it because of: 2023 Aug 2 17:26:25 <mail.crit> donotpassgo sm-mta[60105]: 372GQP6W060096: SYSERR(root): Too many hops 27 (25 max): from <freebsd-net+bounces-3720-freebsd-lists=dyslexicfi sh....@freebsd.org> via mx2.freebsd.org, to <freebsd-li...@dyslexicfish.net> (The same for 3720 and 3719) > To receive the email that has bounced: > > mail freebsd-net+get-3...@freebsd.org (not that there is a good chance that it > bounces again if this was not a configuration change that has been fixed. Tried that, and it bounced again, same message. > and raw version: > https://lists.freebsd.org/archives/freebsd-net/2023-August/003718.txt If you look at that, it appears that the message was sent out from the list to a subscriber, where it looped a few times, and then got injected back into the freelist - this is presumably why a few people got the bounce. Cheers, Jamie
