[Mailman-Users] 4.3.0 mail transport unavailable

Jim Popovitch jimpop at gmail.com
Sat Jun 14 19:09:34 CEST 2014


On Sat, Jun 14, 2014 at 1:03 PM, Mark Sapiro <mark at 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 at lists.neohiopal.org
> > Arrival-Date: Mon,  9 Jun 2014 05:15:45 -0700 (PDT)
> >
> > Final-Recipient: rfc822; foo at roadrunner.com
> > Original-Recipient: rfc822;foo at 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.

This link was posted on the MailOP list earlier today, possibly
related (little details)

 http://wivb.com/2014/06/13/time-warner-responds-to-email-outage-complaints/

-Jim P.


More information about the Mailman-Users mailing list