[Mailman-Users] periodic shunts might have been undetected bad bounce_matching_headers
Julian H. Stacey
jhs at berklix.com
Wed Aug 30 20:13:13 EDT 2017
Mark Sapiro wrote:
> On 08/30/2017 08:36 AM, Julian H. Stacey wrote:
> > Mark Sapiro wrote:
> >> It appears the 'from Mailman.Logging.Syslog import syslog' line is missing.
> > Yes, it's missing. Well analysed without seeing it, Thanks !
> > So I patched just that line in.
> > Mailman 2.1.22 source misses that line. 2.1.23 2.1.24 have it.
> This is a bug introduced in 2.1.21, never noticed and inadvertently
> fixed in 2.1.23. Presumably, it was never noticed before now because it
> was introduced with the member verbosity feature and only triggered if
> Privacy options... -> Sender filters -> member_verbosity_threshold is
> set greater than the default 0 and a "verbose" member is actually set to
2.1.24 has defaults 0 300. My most troublesome list had max 5/week =
which may have occasionaly triggered correctly, but at least one
of the shunted people was someone who very rarely posts so at least that
shunt was unintended by traffic criteria.
> > 2.1.23/NEWS has "Bug Fixes and other patches" ... SpamDetect.py
> But that is in the 2.1.16 section of NEWS.
Oh yes, I hadn't noticed it was in an old section.
So this is a till now undocumented old fix :-)
Julian H. Stacey, Computer Consultant, BSD Linux Unix Systems Engineer, Munich
Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable.
More information about the Mailman-Users