[Mailman-Developers] Bounce action policy - not distinguish "user not found"?

[Ken Manheimer]

Here's a bounce-action policy question, primarily for john, but also i
think useful for general discussion and information.  Currently, "user
not found"/"user unknown" bounces are treated a fatal problems,
invoking immediate (disable or unsubscribe, according to list conf)
action.  Most other random types of bounces are treated as potentially
transient, and just added to the members tally.  It was suggested to
me that it might be better to just handle them all as potentially
transient, and only take the action when the tally exceeds the
threshhold.

Offhand, i don't see the *need* to treat the "user not found" bounces
specially, though i can imagine they're a bit less likely to be
transient than, eg, "spool dir full" bounces.  I'm inclined to think
it would be simpler and more sensible to just lump all the bounces
together.  Thoughts?

Ken