Other responders have indicated that Yahoo recently began requiring
Reverse-DNS Lookup (rDNS) for messages sent to a Yahoo email address, as AOL
did earlier this year.
That is actually a reasonable check, too. Do you know how much spam comes
from address without a proper rDNS configuration? Or how many rDNS names are
not MX for the domain in the name?
Spammers have to use open proxies from which to send because there are so
few open relays any more, and so few ISPs that will tolerate high sending
volumes from their residential gateway pools. Two thirds of Chinese
residential gateway pools, and half of Korean residential gateway pools have
no rDNS configured (and also a small number of Verio IP addresses, as
well!), and most residential gateways with proper rDNS configured are not
listed as MX for the domain they server (probably ALL of them, if one were
inclined to check). But those are precisely where the spammers are finding
open proxies to abuse.
And, so far, my ISP, SBC Yahoo! DSL Service, has not followed others down
the outbound port 25 redirect path. Odd, because with the SMTP AUTH servers,
they could easily get away with it without affecting those, like me, running
MTAs from home.
It is breaking things, yes; but so is spam, and the steps being taken are
hurting spammers.
All the way through July I got between 7 and 9 spam messages a month at my
pop.pacbell.YAHOO.COM account. August and September saw that number
climbing; October was a record. I have a yahoo.com address that peaked at 60
spam messages last January, then dropped. In October that account only had
about 10, but my pacbell.net account, also pulled from
smtp.pacbell.YAHOO.COM, had a record amount of spam. My pacbell.net account
never went over 20 spams in a month for as long as I had it, since February
2001. Until October, 2003, when it was hit with 99 spam messages; most from
sources without proper rDNS. November has shown a auspicious start, with the
Mercury Mail maiser log showing a decline in the number of messages pulled
from smtp.pacbell.YAHOO.COM over the high spam months. Maybe that is the
result of rDNS checks. If so, I might even consider keeping SBC Yahoo! DSL
Service, even though I can't get rDNS configured for my MTA.