FAQ
It looks like the 'disable on excessive bounces' is not working right for
my (only) list 'ontbirds'.... The bounce log contains patterns like this
(trimmed to show one address behaviour, omitting 'already counted'
messages):

Apr 05 09:15:34 2009 (20408) ___ at ___: ontbirds current bounce score: 2.0
Apr 06 00:26:23 2009 (20408) ___ at ___: ontbirds current bounce score: 3.0
Apr 06 00:26:23 2009 (20408) sending ontbirds list
probe to: ___ at ___ (score 3.0 >= 2.5)
Apr 07 07:47:22 2009 (20408) ___ at ___: ontbirds current bounce score: 1.0
Apr 08 10:57:38 2009 (20408) ___ at ___: ontbirds current bounce score: 2.0
Apr 09 08:08:36 2009 (20408) ___ at ___: ontbirds current bounce score: 3.0
Apr 09 08:08:36 2009 (20408) sending ontbirds list
probe to: ___ at ___ (score 3.0 >= 2.5)
Apr 10 08:57:05 2009 (20408) ___ at ___: ontbirds current bounce score: 1.0

This seems to be happening for ALL permanently bouncing addresses.
And I see no trace of 'disabled' anywhere in the logs.... Or is there
a different buzzword I should grep for?

mailman-2.1.5.1-34.rhel4.6

Yes, the bounce score threshold is 2.5
I have bounce info stale after set to 3 days, and addresses which bounce
for just a day or so are noted in the logs as 'bounce info discarded', so
I don't think this is the problem.

Any other info needed to solve this?

- Charles

Search Discussions

  • Mark Sapiro at Apr 10, 2009 at 3:43 pm

    Charles Gregory wrote:
    It looks like the 'disable on excessive bounces' is not working right for
    my (only) list 'ontbirds'.... The bounce log contains patterns like this
    (trimmed to show one address behaviour, omitting 'already counted'
    messages):

    Apr 05 09:15:34 2009 (20408) ___ at ___: ontbirds current bounce score: 2.0
    Apr 06 00:26:23 2009 (20408) ___ at ___: ontbirds current bounce score: 3.0
    Apr 06 00:26:23 2009 (20408) sending ontbirds list
    probe to: ___ at ___ (score 3.0 >= 2.5)
    Apr 07 07:47:22 2009 (20408) ___ at ___: ontbirds current bounce score: 1.0
    Apr 08 10:57:38 2009 (20408) ___ at ___: ontbirds current bounce score: 2.0
    Apr 09 08:08:36 2009 (20408) ___ at ___: ontbirds current bounce score: 3.0
    Apr 09 08:08:36 2009 (20408) sending ontbirds list
    probe to: ___ at ___ (score 3.0 >= 2.5)
    Apr 10 08:57:05 2009 (20408) ___ at ___: ontbirds current bounce score: 1.0

    This seems to be happening for ALL permanently bouncing addresses.
    And I see no trace of 'disabled' anywhere in the logs.... Or is there
    a different buzzword I should grep for?

    mailman-2.1.5.1-34.rhel4.6

    In 2.1.5, a "VERP probe" feature was introduced. Beginning in 2.1.6 it
    it disabled by default, but in 2.1.5 there was no way to turn it off.

    What is happening is when the threshold is reached, a special probe is
    sent with envelope from <LISTNAME-bounces+TOKEN at ...> and the user's
    delivery is disabled by bounce only if and when the probe bounces.

    The issue in your case is your incoming MTA is probably not delivering
    mail for LISTNAME-bounces+TOKEN to LISTNAME-bounces.

    If the MTA is Postfix, you need

    recipient_delimiter = +

    in main.cf, or if you want to use a different delimiter, say '-', you
    can change the defaults

    VERP_PROBE_FORMAT = '%(bounces)s+%(token)s'
    VERP_PROBE_REGEXP = r'^(?P<bounces>[^+]+?)\+(?P<token>[^@]+)@.*$'

    by putting

    VERP_PROBE_FORMAT = '%(bounces)s-%(token)s'
    VERP_PROBE_REGEXP = r'^(?P<bounces>.*)\-(?P<token>[^@-]+)@.*$'

    in mm_cfg.py. I think that regexp will work, but I didn't test it.

    Also see <http://wiki.list.org/x/p4A9>.

    If you don't have access to make these changes, you will need to get
    the installation admins to do it as bounce processing will not work in
    this installation until one or the other change is made.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Charles Gregory at Apr 14, 2009 at 3:29 pm

    On Fri, 10 Apr 2009, Mark Sapiro wrote:
    It looks like the 'disable on excessive bounces' is not working right...
    The issue in your case is your incoming MTA is probably not delivering
    mail for LISTNAME-bounces+TOKEN to LISTNAME-bounces.
    If the MTA is Postfix, you need (in main.cf):
    recipient_delimiter = +
    This is exactly what was needed! THANKS!

    - Charles

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedApr 10, '09 at 2:13p
activeApr 14, '09 at 3:29p
posts3
users2
websitelist.org

2 users in discussion

Charles Gregory: 2 posts Mark Sapiro: 1 post

People

Translate

site design / logo © 2022 Grokbase