Today our email forwarders started getting this from yahoo.com
mail handlers:
553 Mail from 216.220.40.247 not allowed - VS99-IP1 deferred - see
help.yahoo.com/help/us/mail/defer/defer-02.html (#5.7.1)
Connection closed by foreign host.
Which when you go look at that page basically tells you you're probably
an open relay (which we're not), etc.
Can any mail admins at Yahoo contact me offlist, or post what the
restrictions are or at what levels this will kick in?
-mark
Thus spake Mark Jeftovic (markjr@easydns.com) [09/10/03 16:57]:
Today our email forwarders started getting this from yahoo.com
mail handlers:553 Mail from 216.220.40.247 not allowed - VS99-IP1 deferred - see
help.yahoo.com/help/us/mail/defer/defer-02.html (#5.7.1)
Connection closed by foreign host.
Woah. Deja vu.
We got exactly the same thing, starting last night. We've worked around it
by relaying mail to yahoo.com/yahoo.ca through a different mail server.
Which when you go look at that page basically tells you you're probably
an open relay (which we're not), etc.
Ditto. The page also has some links to removal requests, which I've already
filled out. And submitted a followup asking /why/ we were listed. This was
about seven hours ago now, and I haven't even gotten an autoresponse from
them yet, for this note.
Can any mail admins at Yahoo contact me offlist, or post what the
restrictions are or at what levels this will kick in?
Apparently, they blacklist you at whim -- our mail server is confirmed
un-open-relay by ordb.org, and by rlytest. And we can be blacklisted for up
to 60 days at their discretion, according to the page above.
I have also sent a message to postmaster@, who was most unhelpful.
Basically redirected me to the 'I need help with Yahoo! mail' web page.
I /was/ going to wait until tomorrow to follow up on NANOG, but if a Yahoo!
admin is already looking at this for easydns.com, care to drop me a line for
the same reasons? Thanks.
- Damian
Mark Jeftovic writes on 10/10/2003 1:52 AM:
Today our email forwarders started getting this from yahoo.com
mail handlers:553 Mail from 216.220.40.247 not allowed - VS99-IP1 deferred - see
help.yahoo.com/help/us/mail/defer/defer-02.html (#5.7.1)
Connection closed by foreign host.
Us too. And more than one ISP that I have seen (for example, iglou.com mentioned that one of their boxes was being blocked)
Something looks badly borked there.
Yahoo is ticked at our mail server as well - apparently, Yahoo listens to some
DNSBL that thinks it's a mortal sin to be in the same /24 as a machine that
sends back "your mail has a virus" note.
Today our email forwarders started getting this from yahoo.com
mail handlers:<snip>
Us too. And more than one ISP that I have seen (for example, iglou.com mentioned that one of their boxes was being blocked)Something looks badly borked there.
bork bork bork
Indeed. They were blocking our servers this morning, but without any intervention by us (to my knowledge) it is working again now. Go figure.
Does yahoo have any *real* mail accounts anyway? I think the only time I actually send anything to yahoo.com mail addresses is when we are actively hiring people. Isn't yahoo mail only used to hide job hunting from current employers? =)
--chuck goolsbee
Thus spake chuck goolsbee (chucklist@forest.net) [09/10/03 18:37]:
Indeed. They were blocking our servers this morning, but without any
intervention by us (to my knowledge) it is working again now. Go
figure.
Can someone from Yahoo! confirm that the borked blacklist has been fixed,
and it's safe to remove the workarounds we've put in place?
From what we can tell, its a type of "throttling" mechanism, perhaps
intended to slow down problematic hosts.
We went back in our logs and found its been happening for weeks but at
a low level, we never noticed until today.
Today it got much worse, but even so, mail would trickle through to
yahoo, one second we get the refusal and the next a few emails would
be accepted.
So I'm not sure they've fixed it, they may have toned it back down to
the levels we saw from our older logs.
At the time of writing this I think its better than it was earlier:
spawn:/home/markjr/tmp# telnet mx1.mail.yahoo.com 25
Trying 64.157.4.78...
Connected to mta-v22.level3.mail.yahoo.com.
Escape character is '^]'.
220 YSmtp mta107.mail.sc5.yahoo.com ESMTP service ready
quit
and then the next second:
221 mta107.mail.sc5.yahoo.com
Connection closed by foreign host.
spawn:/home/markjr/tmp# telnet mx1.mail.yahoo.com 25
Trying 64.157.4.79...
Connected to mta-v23.level3.mail.yahoo.com.
Escape character is '^]'.
553 Mail from 216.220.40.247 not allowed - VS99-IP1 deferred - see
help.yahoo.com/help/us/mail/defer/defer-02.html (#5.7.1)
Connection closed by foreign host.
Same deal on mx2, looks about 50/50 for a while, then blocks us out
for a few minutes.
It's definitely still happening, if I had to guess I'd say maybe its
eased somewhat.
-mark
Thus spake Mark Jeftovic (markjr@easydns.com) [09/10/03 21:42]:
At the time of writing this I think its better than it was earlier:
spawn:/home/markjr/tmp# telnet mx1.mail.yahoo.com 25
Trying 64.157.4.78...
Connected to mta-v22.level3.mail.yahoo.com.
Escape character is '^]'.
220 YSmtp mta107.mail.sc5.yahoo.com ESMTP service ready
quitand then the next second:
221 mta107.mail.sc5.yahoo.com
Connection closed by foreign host.
spawn:/home/markjr/tmp# telnet mx1.mail.yahoo.com 25
Trying 64.157.4.79...
Connected to mta-v23.level3.mail.yahoo.com.
Escape character is '^]'.
553 Mail from 216.220.40.247 not allowed - VS99-IP1 deferred - see
help.yahoo.com/help/us/mail/defer/defer-02.html (#5.7.1)
Connection closed by foreign host.Same deal on mx2, looks about 50/50 for a while, then blocks us out
for a few minutes.
Ditto, here, from all our inbound and outbound MXes.
As of last month Yahoo! are providing some mail services for BT Openworld in
the UK, soon to be all of their consumer mail accounts.
P.
Paul S. Brown writes on 10/11/2003 3:41 AM:
As of last month Yahoo! are providing some mail services for BT Openworld in the UK, soon to be all of their consumer mail accounts.
They've been providing mail services for SBC as well, since quite some time.