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 m
Kirke Johnson wrote:
>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
Kirke Johnson wrote:
>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.
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
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 r
hi,
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
