answers inline...
Mark Sapiro wrote:
> John wrote:
>
>> What hasn't worked:
>> * My service provider claimed the info in disable messages was insufficient
>> for
>> debug!?
>
>
> And can you post one?
This was around the time my provider changed the smart host pool... The
64.202.189.86 IP address was in the pool & on at least 2 RBLs. The
208.109.80.54 IP is in the new pool and apparently still on 1 RBL list :-(. They
claim they did not bounce back to my server... I haven't seen this since 11/10,
but the rx7 list email is not being delivered. I don't understand why my other
lists seem to be unaffected...
----------------------------------------
List: rx7
Member: [email protected]
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
[email protected].
<[email protected]>:
64.202.189.86 failed after I sent the message.
Remote host said: 554 Message refused.
long list of similar msgs removed...
<[email protected]>:
208.109.80.54 failed after I sent the message.
Remote host said: 554 Message refused.
----------------------------------------
>> * I reduced the bounce threshold, now people are kicked off sooner. Today's
>> batch of almost 200 disables returned no useful information! All returned:
>>> The triggering bounce notice is attached below.
>>>
>>> Questions? Contact the Mailman site administrator at
>>> [email protected].
>>>
>>> [disabled by periodic sweep and cull, no message available]
>
>
> Because there was no 'triggering' bounce. The disable occurred because
> the threshold was reduced to a value <= the current score for these
> 200.
That makes sense, since I changed the bounce threshold...
>> * VERP worked a couple times on my test list, but never on the other lists,
>> even
>> though *sometimes* it did send the messages individually from the standard
>> list-bounce address. I set VERP options:
>> VERP_PERSONALIZED_DELIVERIES = Yes
>> VERP_DELIVERY_INTERVAL = 1
>
>
> Did you restart Mailman after changing those settings in mm_cfg.py?
I don't remember, but I did now...
>> * couldn't find any useful information in the logfiles.
>
>
> Anything in smtp-failure?
empty
> Does the smtp log say it delivered the post to the appropriate number
> of recipients?
it's hard to say... there is no single entry for the problem list that has the
correct number (446 less a few nomail). I also don't know what the items are per
line. I assume it's:
timestamp, (???), msg ID, info
-> Nov 12 03:45:42 2009 (32441) <[email protected]>
-> smtp to rx7 for 1 recips, completed in 0.135 seconds
What's the value in ()'s? It doesn't seem to be msg length...
>> Hopefully someone has a hint that might help me find a resolution to the
>> problem....
>
>
> Show us a disable message with an actual triggering bounce.
see above...
Thanks,
John
------------------------------------------------------
Mailman-Users mailing list [email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
