| Metrocast server problem - only me ?? Am I the only one who has friends reporting that they often get the following bounce back when they email me ? Any ideas on what's wrong ? 
--- On Fri, 4/29/11, MAILER-DAEMON@nm18.bullet.mail.bf1.yahoo.com wrote:
> > From: MAILER-DAEMON@nm18.bullet.mail.bf1.yahoo.com
> > Subject: Failure Notice
> > To: xxxxxxxx@yahoo.com
> > Date: Friday, April 29, 2011, 12:44 AM
> > Sorry, we were unable to deliver your
> > message to the following address.
> >
> > :
> > Mail server for "ct.metrocast.net" unreachable for too
> > long
> >
> > --- Below this line is a copy of the message.
> >
> > Received: from [98.139.212.144] by
> > nm18.bullet.mail.bf1.yahoo.com with NNFMP; 27 Apr 2011
> > 04:41:20 -0000
> > Received: from [98.139.212.223] by
> > tm1.bullet.mail.bf1.yahoo.com with NNFMP; 27 Apr 2011
> > 04:41:20 -0000
> > Received: from [127.0.0.1] by omp1032.mail.bf1.yahoo.com
> > with NNFMP; 27 Apr 2011 04:41:20 -0000
> > X-Yahoo-Newman-Property: ymail-3
> > X-Yahoo-Newman-Id: 916186.25345.bm@omp1032.mail.bf1.yahoo.com
> > Received: (qmail 88529 invoked by uid 60001); 27 Apr 2011
> > 04:41:20 -0000
> > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> > d=yahoo.com; s=s1024; t=1303879280;
> > bh=+7xhqvVTcfxzLYNZrMY2vXfwMKqNYatgx7V9xeMwdak=;
> > h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type;
> > b=eXXvKpWgli1VF5rugyz1ssG9ZD+ZUcLmCpFbIsvsaK2X5Ne5/9os9uQ7I4yU6DwH4Dhy5ftpo6JFO5u9QbQAb/bRo8JHlUWm/AbupjbHJ4z/lW5nHrFz515VH1c7aTpznZuzl3l144VlsPBkNiWYxFmDA6aSTlkP9f/ti0uz7sM=
> > DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
> > s=s1024; d=yahoo.com;
> >
> > h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type;
> >
> > b=6SnBaHboC9K+iJNhIgY9jCDjXPnrzovuexFkmO1m4hEyR+ftrKb4VKORBn36Z7zyAXdZAXGf/oMn4TI49vU30nXiqYTWEvuaWGs49eKvFWXiTmq7ITaPEDSjIOunr+QWf4NTtfFzUqbJz7jcmLcAJIvYlVfy9yWmfJK4chzhN40=;
> > Message-ID:
> > X-YMail-OSG:
> > FGma_j0VM1kmpbESaKJyKlL8wa2AbHbUOD4meOMWm4t3AkE
> >
> > IfQL0jt1f6qDTkinq.iKlgdS4qoVzveaAaoWrYNbSr_XWGS.EjPfS4kC1b.T
> >
> > p9bq4PIjSs7g1bFU2IAiuNfYAt7argY96EZsy0rf0ZFHifoiJpJWr3CjUby2
> >
> > TcRjYMoFZsYm23pXvXPzIc08mT0eaVeE27TgEFTEJDIuYamtsY5MR6HoiOwx
> >
> > ge_CmsIU95XkYlPZUOtgK.CEyX0DHIKWm5_dCo_SqwLueNQEI6Hn9kjk4wdB
> >
> > Q1JxuYjDxHqRSo7t4dh7pbDQJl7Fb9JPF2dQifEJLpvqef1FQ6zIDOW4JoFl
> >
> > R4qr8j7eqRuBO_lrdDv8tXtSHCkWM5W5ICo7EjysH5QVmNu3znbmd0ozFr_y
> > z00xgNwr83V2ML6pNgg--
> > Received: from [71.50.97.189] by
> > web31802.mail.mud.yahoo.com via HTTP; Tue, 26 Apr 2011
> > 21:41:20 PDT
> > X-Mailer: YahooMailClassic/12.0.2
> > YahooMailWebService/0.8.111.303096
> > Date: Tue, 26 Apr 2011 21:41:20 -0700 (PDT) |
|
| The error "Mail server for "ct.metrocast.net" unreachable for too long" means Yahoo had issues getting to that domain, for whatever reason.
You'd need to have contacted Yahoo at that time to figure out why I bet, but if it happens again give MetroCast a call and we can look into our side at least if it's happening again. |
|
1 edit | reply to mangurian
appears to be yahoo contacts (at least) having the problem Unfortunately, I despair of ever getting Yahoos attention. They are too damn big to worry about me. Any Ideas on why it would be just Yahoo and is there anything I can do on my end?
Turns out it is not just YAHOO mail. Others are reporting they have msgs to me bounce. |
|
| Well it looks like your using Yahoo mail right? If that's the case I (personally) would have no idea why mail gets rejected or bounced or times out if it happens on your end.
If it hits the MetroCast servers and you get a bounce from us, that I can definitely look into, though it doesn't appear to be that from the example you posted.
Feel free to IM me your email address and I can send mail from Metrocast to it to see what happens though. |
|
| I am seeing the same issue. It has been going on for the past few days. It is the same thing: Yahoo fails to contact ct.metrocast.net.
If I ping ct.metrocast.net, I get timeouts. I do get an DNS translation of 65 175 128 188. Trying this from a different ISP, I get the same translation, so it appears to be correct. |
|
