[Mailman-Developers] Re: [Mailman-Users] Bounce Options

Barry A. Warsaw barry@zope.com
Sat, 1 Dec 2001 14:53:28 -0500


>>>>> "CVR" == Chuq Von Rospach <chuqui@plaidworks.com> writes:

    CVR> If the bounce is RFC compliant, it's fairly simple to
    CVR> determine "hard" and "soft" bounces, and since they are
    CVR> following the standards, it's not a huge amount of
    CVR> work. Treat a "soft" bounce as half a bounce. That gives the
    CVR> soft bounce twice as long to actually come into effect.

Nice.  I like that.

    CVR> If the bounce is one of the many non-RFC compliant mail
    CVR> systems, treat everything as hard bounces. You don't spend
    CVR> the work trying to read their non-compliant tea leaves, and
    CVR> they have some quiet encouragement to get their act together
    CVR> and become RFC compliant.

Yup.

    >> I like the idea that subscribers can wind up "on probation"
    >> (assuming the list admin configures the list that way).  I
    >> understand that this simplifying assumption makes the design
    >> much easier to think through.

    CVR> It'd be really nice if bounce-nomail and user-nomail are
    CVR> separate modes, so we can tell the difference. Beyond that,
    CVR> what would be optimum for me is if bounces went to nomail
    CVR> mode, and then if they're still nomail 30 days later, deleted
    CVR> from the system. That gives a user a chance to "come back"
    CVR> without losing their subscription state, but not hang around
    CVR> forever....

Yes, definitely.  That's part of the plan.

    CVR> At some point, it'd be nice to be able to validate those
    CVR> other nomail addresses, similar to the monthly password
    CVR> reminder (or part of it).  Something that says "you have this
    CVR> account sent to this mode. If you want this, click 'here'. If
    CVR> you don't, do nothing and we'll delete it. Where 'click here'
    CVR> takes you to a link that sets the "I'm okay" counter on that
    CVR> nomail status for another 90 days or something...

Yes.  That's why the current "disabled-by-idunno" state should be a
third, transitional state.  We can hook that in with some cronjob to
convert folks.

Thanks,
-Barry