Re: Yahoo! Mail Issue

["Nathanael C. Cariaga" <nccariaga () stluke com ph>]

Just to clarify, the problem we are encountering is that emails sent 
from yahoo does not seem to reach our mail server (even any of our MX 
records / anti-spam servers).

We have neither implemented any of the items you have said (still in the 
process of doing so).  I tried to interview our email users regarding 
this issue.  They said that it was working perfectly before March.  Then 
we started to have this isolated problem since then.



On 4/12/2011 2:41 PM, Joshua William Klubi wrote:
> Well yahoo's mx tend to do that a lot. i used to have a lot of  bounced
> emails to yahoo until i implemented dkim, domainkeys and spf then all my
> yahoo problems disappeared ,
>
> I just want to know if you have implemented any of
> these technologies dkim,domainkeys and spf, other wise you would have
> all those problems
>
> Joshua
>
> On Tue, Apr 12, 2011 at 4:47 AM, Matthew Petach <mpetach () netflight com
> <mailto:mpetach () netflight com>> wrote:
>
>     On Mon, Apr 11, 2011 at 9:28 PM, Nathanael C. Cariaga
>     <nccariaga () stluke com ph <mailto:nccariaga () stluke com ph>> wrote:
>      > Hi All,
>      >
>      > It seems that we're having some problems receiving emails from
>     selected
>      > Yahoo! Mail Accounts.  I noticed that there is a commonality
>     between the
>      > accounts that fails when sending an email to our domain (see
>     email header
>      > below)
>      >
>      > From: "MAILER-DAEMON () nm1 bullet mail sg1 yahoo com
>     <mailto:MAILER-DAEMON () nm1 bullet mail sg1 yahoo com>"
>      > <MAILER-DAEMON () nm1 bullet mail sg1 yahoo com
>     <mailto:MAILER-DAEMON () nm1 bullet mail sg1 yahoo com>>
>      > To: *-*-*-*-*a () yahoo com <mailto:a () yahoo com>
>      > Sent: Fri, April 8, 2011 6:26:08 PM
>      > Subject: Failure Notice
>      >
>      > Sorry, we were unable to deliver your message to the following
>     address.
>      >
>      > <xxxxxxxxxa () stluke com ph <mailto:xxxxxxxxxa () stluke com ph>>:
>      > Mail server for "stluke.com.ph <http://stluke.com.ph>"
>     unreachable for too long
>
>
>     Um...it might be easier to get mail, if your host didn't close
>     the connection with a 5xx error.  :/
>
>     mpetach@hinotori:~> host -t mx stluke.com.ph <http://stluke.com.ph>
>     stluke.com.ph <http://stluke.com.ph> mail is handled by 20
>     qc.stluke.com.ph <http://qc.stluke.com.ph>.
>     stluke.com.ph <http://stluke.com.ph> mail is handled by 20
>     mx1.stluke.com.ph <http://mx1.stluke.com.ph>.
>     stluke.com.ph <http://stluke.com.ph> mail is handled by 40
>     gc.stluke.com.ph <http://gc.stluke.com.ph>.
>     mpetach@hinotori:~> nslookup qc.stluke.com.ph <http://qc.stluke.com.ph>.
>     Server:         127.0.0.1
>     Address:        127.0.0.1#53
>
>     Non-authoritative answer:
>     Name: qc.stluke.com.ph <http://qc.stluke.com.ph>
>     Address: 219.90.94.56
>
>     mpetach@hinotori:~>
>
>
>
>     mpetach@opstools1:~> telnet 219.90.94.56 25
>     Trying 219.90.94.56...
>     Connected to static-host-219-90-94-56.tri.ph
>     <http://static-host-219-90-94-56.tri.ph>.
>     Escape character is '^]'.
>     ehlo yahoo.com <http://yahoo.com>
>     554 SMTP synchronization error
>     Connection closed by foreign host.
>     mpetach@opstools1:~>
>
>
>     I imagine when port 25 stops giving 5xx
>     failure message back, mail reception
>     might improve.   ^_^;
>
>     Matt

--
Nathanael C. Cariaga
Network & Security Administrator
St Luke's Medical Center

Tel (QC) :  +63 2 723 0101 ext 5520 / 4206
Tel (GC) :  +63 2 789 7700 ext 6035 / 6036
Tel      :  +63 2 356 5686
Mobile   :  +63 922 8735686
EMail    :  nccariaga () stluke com ph