"Clayton, Robert (Bob)" wrote:
> It seems to me there would be a less convoluted way of handling these. As it stands
>now the nomail is qualified by x times per hour for y amount of days. Seems very
>inefficient
You can always change them. :) The reason I agree with the current setup is that
sometimes someone's server just goes offline for a while, and if during that period x
messages get send in an hour, we don't necessarily want to set them instantly to
nomail - but rather let it "slide"... However, if they stay down for y days, then
we'll change them.
Keep in mind that your MTA also contributes to this time frame. For example, if
you were running sendmail, and if the bounce message was just a time-out, or host
rejected (not unknown user, or other fatal error), sendmail will by default retry
messages for a while (several days at that) - factor this in with the way mailman
decided when to change someone's subscription, you may end up with messages in the
queue that are several days, maybe
weeks old before anything gets done with them.
I personally have changed both my outbound MTA to report back after 6 hours, and
to cancel after 48 hours, as well as mailman. It now changes people's subscription in
a more aggressive mode (as opposed to the default settings).
--
W | I haven't lost my mind; it's backed up on tape somewhere.
+--------------------------------------------------------------------
Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
IT Director / SysAdmin / WebSmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
------------------------------------------------------
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
