The ramifications for this became apparent. Yahoo servers started sending out spam. I had no proof in the beginning but this post verified my suspicions. Spammers became aware of the golden opportunity and started abusing Yahoo servers to the fullest. This led to really tough times for the Yahoo Mail people and their PR guys as apparent from this post on Yahoo Mail Blog. Not only were the email servers overloaded, but ISPs started blocking mails from Yahoo servers which led to delayed/undelivered mails.

Now it seems that Yahoo has changed the way it routes emails through its SMTP servers. Earlier methods were quite trivial as the mail headers would have shown.
Received: from smtp104.plus.mail.re1.yahoo.com (smtp104.plus.mail.re1.yahoo.com [69.147.102.67]) by rly-ma08.mx.aol.com (v120.9) with ESMTP id MAILRELAYINMA088-8c647354bcb3bd; Sat, 10 Nov 2007 01:12:27 -0400
Received: (qmail 55018 invoked from network); 10 Nov 2007 06:12:27 -0000
Received: from unknown (HELO localhost) (myYahooID@myIPAddress with login)
by smtp104.plus.mail.re1.yahoo.com with SMTP; 10 Nov 2007 06:12:26 -0000

Gradually Yahoo started repairing its servers from the smtp11x.plus.mail.re1.yahoo.com series to smtp10x.plus.mail.re1.yahoo.com as the latter still worked for a long time without FROM address checks.

Now the mail headers are more complicated. It seems that Yahoo does some internal checks regarding whether the FROM address is valid and then only routes the emails.
Received: from n3.bullet.mail.ac4.yahoo.com (n3.bullet.mail.ac4.yahoo.com [76.13.13.29])
by mx.google.com with SMTP id d12si10680167and.24.2008.04.05.08.35.00;
Sat, 05 Apr 2008 08:35:01 -0700 (PDT)
Received-SPF: neutral (google.com: 76.13.13.29 is neither permitted nor denied by best guess record for domain of myYahooAddress) client-ip=76.13.13.29;
DomainKey-Status: good (test mode)
Authentication-Results: mx.google.com; spf=neutral (google.com: 76.13.13.29 is neither permitted nor denied by best guess record for domain of myYahooAddress) smtp.mail=myYahooAddress; domainkeys=pass (test mode) header.From=myYahooAddress
Received: from [76.13.13.26] by n3.bullet.mail.ac4.yahoo.com with NNFMP; 05 Apr 2008 07:31:40 -0000
Received: from [68.142.237.88] by t3.bullet.mail.ac4.yahoo.com with NNFMP; 05 Apr 2008 15:34:24 -0000
Received: from [216.252.111.166] by t4.bullet.re3.yahoo.com with NNFMP; 05 Apr 2008 15:34:24 -0000
Received: from [127.0.0.1] by omp101.mail.re3.yahoo.com with NNFMP; 05 Apr 2008 15:34:24 -0000
X-Yahoo-Newman-Id: 666616.8045.bm@omp101.mail.re3.yahoo.com
Received: (qmail 61052 invoked from network); 5 Apr 2008 15:34:24 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;s=s1024; d=yahoo.co.in;
h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID: Date:From:User-Agent:MIME-Version:To: Subject:Content-Type:Content-Transfer-Encoding;b=1zOo54htnYlA5Gy3kNjQQVpRD8fYyEbgwwejDXI4Jr/RZ32+QDvvwYLxJOdSkbwWyJhA3P5PfBVX+mGGYePhw3TXtmfqdVSUcu/BGnwpyONzF3umcYLylkOzLBu/URre6lF+6gdEnRPsfIE3isy25r9dfELJke0wDDwqEdCEYg= ;
Received: from unknown (HELO Why?are?spaces?replaced?by??BTW?if?you?read?this?you?are?a?G33K) (myYahooID@myIPAddress with plain)by smtp103.plus.mail.re1.yahoo.com with SMTP; 5 Apr 2008 15:34:24 -0000

BTW I had told this to the Engineering head of Yahoo Atlanta during my internship interview here and he was surprised by this. Unfortunately I couldn’t demo this for him as Yahoo had started fixing this problem starting that day only.

Now I faintly remembered receiving 2 scraps (which obviously looked like Spam) from my friends and that I had deleted them promptly. Could it be a case of Cross Site Scripting? A blog article that I read today confirmed by suspicions.

Now in my previous post I had emphasized my belief that “All input is evil” and even though Google seems to do a pretty good job with Blogger, filtering out bad HTML and unwanted scripts; it has failed to do that with Orkut. Especially when it keeps adding more and more features to make the UI richer and interactive, the importance of such measures increases.

Finally when I found yesterday that my account had been upgraded to their RC (Release Candidate version), I couldn’t help but try sending an SMS and guess what ISDN (it still doesn’t work!).

Then Microsoft came with their Windows Live Custom Domains. Even though the package was not as good as Google, a sense of loyalty to my company drove me towards using it. Using it was a no-brainer. Sign up with your Live ID and register your domains. Since I was already happy with Google Apps, I gave it a miss. But when they introduced support for sub-domains I was more than happy to try it out and my mail.smart-techie.com is hosted on it. Not a problem with that ever, yay Microsoft. BTW their support was just great!

Now enter AOL. Famous for its terrible ways (and how it was made to make everything on its site free!). For sometime, they didn’t even have free customer support. When they came with one, it was pathetic. Now, I registered my primary domain with them for their myeAddress service expecting it… to work. Big surprise, it didn’t (actually it wasn’t that much of surprise).

Finally I found a link to contact their live customer care. Live… must be able to solve problems quickly.

So I tried contacting one of them that their service failed to recognize that I had set up the MX records for my domain correctly. That guy had a pseudonym Leon and tried to help. But when things like MX records and mail servers and registrars came into the picture, it was apparent he was lost. He tried to begin at Step 1 for him which was the registrar. Since my registrar wasn’t one listed, he said I won’t be able to use the service. WTH, since when did the web start to discriminate people based on the registrar of their domain or was AOL so stupid that they checked the registrar’s site to get MX records (ROFL, are they doing that!). Anyway I persisted and finally brought some sense into that guy who agreed that my settings were indeed correct and promised to contact me after a day.

Hi! It’s me, Leon. We appreciate your patience with this matter. Please try setting up your My E-Address after 24-48 hours. I have already escalated this to my supervisor, and filed a report so the My E-Address development team would study this, and I asked for confirmation if your registrar is supported by My E-Address. Please let me know the result. You may send me an e-mail to this address. (AOLTECHLMP@AOL.COM)

Thank you so much.
Leon / AOLTechLMP
Customer Care Consultant
AOL LLC

When I didn’t get a reply after a day, I again fired the chat thingy on their support site. Now it is 4th July, the American Independence Day, so support guys in the US are on a holiday. Enter their Indian BPO offices… The first guy I get is Arun.

…

Me: I have access to the nameservers for my domain and had changed them myself

Me: the registrar is not involved in setting up these settings for me

Me: I am not using the registrar’s nameservers

TechLiveARM: Ok. So you are the domain owner is it ?

Me: right

Me: I have checked the MX record configuration on third party sites like dnsstuff.com and mxtoolbox.com and they are showing the updated settings

TechLiveARM: All right. Please Log in to your registrar’s website and go to the MX record maintenance page. And provide me that link please. I will check information on that.

What, didn’t I tell that guy that I have my own domain and nameservers?

Me: The registrar doesn’t maintain MX settings for me, that’s what I am telling here. He just has NS records pointed to my nameservers

Me: My nameservers mentioned in the NS records have the MX records with them

Crash course in DNS 101 to a tech support guy.

Me: You can use a site like http://www.mob.net/~ted/tools/mx.php3 or http://www.davidj.org/tools/whatmx.php to see my current settings as visible to computers on the Internet

TechLiveARM: This could be the problem. Because as per AOL requirement, The MX settings configuration has to be done by the domain registrar. And we don’t provide technical support on the same.

TechLiveARM: All the help information and configuration information are on the help pages given to you in the earlier chats.

Me: Hey I know what I am talking about here and the information can be retrieved from any computer and not specifically GoDaddy or any other domain registrar’s computer

Me: the computer called the NameServer takes care of these settings

Me: and it has been verified that the settings made by me are correct as per yesterday’s chats

Me: so it means you can see the correct settings from your end

Me: You can look up the chat transcript to see that the support person says that

TechLiveARM: Yes. I understand. But what i mean to tell is (he’s an Indian, look from the way he builds the sentence… can be directly translated in Hindi word-to-word), Although everything is set right, It could be still giving you that error because the MX is not maintained by the Registrar. And unfortunately we don’t provide troubleshooting for this issue.

TechLiveARM: I have seen the previous chat transcripts.

Me: it doesn’t matter if the MX record is maintained by anyone, just that the MX record should be retrievable by the computer trying to send mail.

TechLiveARM: Unfortunately AOL doesn’t mention that. AOL’s help pages say that it has to be Maintained by the registrar.

Me: can you point me to the location where it says that specifically?

TechLiveARM: Sure.

Me: that MX records have to be maintained by registrar else this won’t work?

TechLiveARM: It’s doesn’t say that anywhere. But it doesn’t say that it would work if it is not maintained by a non registrar too.

TechLiveARM: And therefore, Since there is no technical support on this, We would advice you to go with the help information.

Me: Your statement was "AOL’s help pages say that it has to be Maintained by the registrar."

Me: now you are backtracking on what you have said

Me: It is clear that there might be a problem with myeAddress registration service

Me: and its Lookups

TechLiveARM: Oh.. I am sorry. I apologize for that.

Sure you apologize for blaming the system for your stupidity.

Me: rather than the problem being communicated to the team,

Me: you are advertising the service as fully functional

Me: Also in the support mail, there was something mentioned about escalation

Me: can you say something on that?

And then the most classic thing, just like you say "hello… hello…" on the telephone line when you don’t want to talk to the other person, this person starts types in quick succession (actually 2 seconds, then after a mandatory pause by the system, the last line).

Not to rush you, but are you still with me?

Please send a message that you are still with me, or I will have to end this session to help the next person in line.

Unfortunately, we are not able to communicate for some reason. I will have to end this session now.

Not wanting to be outdone, I go to the chat again and guess what, it’s the same guy. As soon as he reads the transcript of the earlier chat, 3 lines pop up which have already been reproduced earlier for your reading pleasure.

AOL has started its aol.in portal, but with more morons posing as their tech support, its only time before they bow down to the likes of Microsoft.

Aftermath

Free IMAP server for your domain with unlimited storage is a big thing. So I kept trying to register at their site for 2 more months. Finally, they actually canceled my previous registration request and this time, their site actually worked! It accepted my registration and within an hour I was able to send and receive mail using AOL. Their service is a little buggy (you can’t put a name on your outgoing messages which forces me to use Google or Yahoo SMTP servers ) and their service intermittently goes down. But I think I can live with that. SO the moral of the story is "try, try and try again until you succeed even though the Tech Support says otherwise!".