At 08:54 AM 1/27/2009, Mark Sapiro wrote:
Kirke Johnson wrote:
(-- snip --)
If bounce_you_are_disabled_warnings is 0, cron/disabled is not involved
in removing the bouncing member. The member should be removed
immediately. The fact that you received an unsubscribed notice and the
subsequent message didn't yield a bounce would seem to say the bogus
address was in fact removed.
What "membership list" are you looking at? Could it be stale?
I have been refreshing the Membership List in the admin GUI for the list.
Identical results? You mean the first message bounced and unsubscribed
the member and the second message wasn't sent (or at least didn't
bounce)?
The first message bounced and unsubscribed the member, but they did
not go away.
The second message did not bounce as there was already a bounce that day.
(-- snip --)
Do you by chance have
VERP_PROBES = Yes
(or On or True or 1) in mm_cfg.py? If so, when threshold is reached,
score is reset and a VERP like probe is sent. If that doesn't bounce
or if the bounce is not correctly delivered, the member will never be
removed.
YES! This was the problem - thanks!! After changing the
configuration, the next test message removed the member very nicely.
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
----------------------------------------------------------------------
Kirke Johnson Internet: [email protected]
Email Administrator, TSS , Sylvania Campus http://www.pcc.edu/
Portland Community College, Portland, OR, USA (503) 977-4368
------------------------------------------------------
Mailman-Users mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
