I have been attempting to test out the bounce processing on a test
list and am confused by the results so far. We are running Mailman
2.1.9 on RHEL, installed with the OS.
The test list (tsstst) has the following settings:
bounce_score_threshold: 1.0 (originally 5.0)
bounce_info_stale_after: 7
bounce_you_are_disabled_warnings: 0 - for immediate removal (originally 3)
bounce_you_are_disabled_warnings_interval: 7
I have sent four test messages thus far, with an invalid list member
"[email protected]". The first two tests were on 1/22. The first one
detected the bounce and issued the unsubscribe notification that
"[email protected] has been removed from Tsstst". The member was
still listed in the membership list, and did not go away when
/usr/lib/mailman/cron/disabled ran the next morning. The second
message on the 22nd did not yield a bounce.
Today (still within the 7 day warning interval), I sent two more test
messages with the identical results. Running
"/usr/lib/mailman/bin/list_members -n bybounce tsstst" as suggested
below produces no output.
Is there another way to examine the counters inside the "black box"
to see what is going on? I can conceive of this process dragging on a
couple more days before the original disabled_warnings threshhold of
3 is reached and the disabled cron job has a final chance to run, if
that is even worth doing at this point.
Thanks for your help in supporting Mailman!
At 10:49 PM 12/20/2008, you wrote:
faisal anif wrote:
>
>I have the following settings:
>
>bounce_score_threshold: 2.0
>bounce_info_stale_after: 7
>bounce_you_are_disabled_warnings: 0 - for immediate removal
>bounce_you_are_disabled_warnings_interval: 7
>
>then I notice that the addresses that have delivery disabled for
bounce reason is still in the members list and not completely
removed from the list .. which is not good becasue I want them
totally removed and know the exact number of active members ..
>
>how can I do that?
The settings you have will do that. If you recently reduced
bounce_you_are_disabled_warnings to 0 from some other number, those
members whose delivery was disabled by bounce at the time of the
reduction will still get the number of warnings they were set to get
when their delivery was disabled before they are removed. Also,
cron/disabled has to be run in order to send the warnings and
ultimately remove the members.
If you don't want to wait for these to be automatically removed, you
can always remove them via the admin interface or if you have command
line access, do
bin/list_members -n bybounce LISTNAME | bin/remove_members -f - LISTNAME
which will remove all members with delivery disabled by bounce.
In any case any members who in the future bounce on two out of seven
days will be immediately removed.
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
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/kjohnson%40pcc.edu
Security Policy: http://wiki.list.org/x/QIA9
----------------------------------------------------------------------
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
