On Jun 14, 2014, at 1:03 PM, Mark Sapiro <mark@msapiro.net> wrote:

On 06/14/2014 09:22 AM, Conrad G T Yoder wrote:

...

I have recently (last couple weeks?) started getting "4.3.0 mail transport unavailable” bounces from roadrunner/TW addresses (the rate-limiting issue is not currently rearing its head), and that is causing Mailman (2.1.17) subscriptions to be disabled. Example error message in the “Bounce action notification” email:

Reporting-MTA: dns; zapata.dreamhost.com X-Postfix-Queue-ID: B6D6B8DB0B72 X-Postfix-Sender: rfc822; neohiopal-bounces@lists.neohiopal.org Arrival-Date: Mon, 9 Jun 2014 05:15:45 -0700 (PDT)

Final-Recipient: rfc822; foo@roadrunner.com Original-Recipient: rfc822;foo@roadrunner.com Action: failed Status: 4.3.0 Diagnostic-Code: X-Postfix; mail transport unavailable

...

From googling it appears this is may be a Postfix problem? Any one else seeing this with roadrunner/time warner?

Yes, it would seem to be a problem with Postfix at zapata.dreamhost.com. Is dreamhost.com your Mailman host or a downstream relay in this case? If they are your outbound MTA, it seems strange that this would affect only mail to the roadrunner.com domain, but in any case, I think it's up to Dreamhost to fix it.

DH is indeed my Mailman host. If you remember, I was (hopefully all in the past - knock on wood laminate) having issues with RR/TW rate-limiting mailing list emails from DH’s server, causing bouncing/subscription disabling. Who knows if this is related. I am in touch with them to see what is going on.

-Conrad

-- Is there a suspect in your family? Contact the Ministry of Information. Ring 100 00 00.

On 06/14/2014 05:04 PM, Stephen J. Turnbull wrote:

Conrad G T Yoder writes:

...

I have recently (last couple weeks?) started getting "4.3.0 mail transport unavailable” bounces from roadrunner/TW addresses (the rate-limiting issue is not currently rearing its head), and that is causing Mailman (2.1.17) subscriptions to be disabled. Example error message in the “Bounce action notification” email:

Note that the message you're reporting is a temporary failure (that's what a 4.x.x status code means) so I don't really understand why the bounce count is being incremented for this. Whichever MTA is actually talking to Time-Warner should be bumping this to a 5.x.x "permanent" failure (in this case, giving up after trying repeatedly).

Postfix will keep retrying the temporary failure at intervals until the message has been in the queue for maximal_queue_lifetime (default 5 days) at which point it gives up and returns the DSN.

The DSN has "Action: failed" which says delivery ultimately failed and this is what Mailman looks at. The extended status is still 4.x.x which is the status of each individual (or probably just the last) delivery attempt. This is compliant with RFC 1893.

RFC 1893 Sec 3.5 says in part:

   X.4.7   Delivery time expired

      The message was considered too old by the rejecting system,
      either because it remained on that host too long or because
      the time-to-live value specified by the sender of the
      message was exceeded. If possible, the code for the actual
      problem found when delivery was attempted should be returned
      rather than this code.  This is useful only as a persistent
      transient error.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan