On 8/5/22 09:17, summersan@nclack.k12.or.us wrote:
My Questions:
Is it normal to see large amounts of
Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>lines in logs?Should there normally be other detectors listed in the logs beyond the
DSNone?If so, is there a setting I can change somewhere to make this happen?
Prior to flufl-bounce 4.0, it would run all detectors on every message
to the -bounces address. Beginning with 4.0, it runs the detectors in a
defined order from most specific/authoritative to least. If you are
seeing only or mostly the DSN one, you have 4.0 and the DSN detector
recognizes a RFC 3464 compliant bounce.
For reference, I can only find one other logcheck log that shows a
Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>line from before the recent Mailman 3 upgrade. In that past logcheck log, there are other detectors listed as well, which makes me wonder if something is still stuck with the new Mailman 3 install (or if maybe something needs to be changed in a setting file somewhere):
Probably the upgrade also upgraded flufl.bounce to 4.0.
So the real question is why are you seeing large numbers of bounces.
Since it appears they are recognized by DSN, they probably aren't spam
to the -bounces address. Do you have verp probes enabled (verp_probes =
yes in the mta section of mailman.cfg)? If so, it's possible that you
are getting bounces for spam and the like, but the probes don't bounce
so the user's delivery is never disabled.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan