If you were trying to send me an email yesterday you might have received a nice returned mail transcript. That’s because I fucked up the MX record when “outsourcing” my mail to Google Apps. Since Dreamhost is having major issues relaying their emails to Google I was annoyed that I can’t use my Gmail to get my comment confirmations. The pleasant, but not very effective folks from DH tech support group recommended that using Google Apps will let me keep the Gmail interface, solve the issue of delayed comment confirmations (at least for me, not necessarily for the commenters) and help them by easing the load on the Gmail forward queue.
So I went and signed app for the Apps account, set it up and then set up a custom MX record pointing to aspmx.l.google.com via Dreamhost’s CPanel. Only I fucked it up.
Now, usually when you are trying to transfer an important piece of information from one text box to another without typos, you copy and paste. You pretty much can’t go wrong with pasting, unless of course you mess up the crucial step of HIGHLIGHTING the text to be copied. It should be easy, right? Apparently not. My MX ended up pointing to aspmx.l.google.co. If you don’t notice the difference, look again. I ate the m in .com.
As the result all the email set to me was going directly into the void. Sigh… I just can’t win.
If you were sending me an email, and getting bounced all day please keep trying or send it to my gmail address. That one works normally – only the @terminally-incoherent.com address was affected by my apparent inability to copy and paste properly.
It may take up to 48 hours for the records to propagate all over the internets. Knowing my luck it will take exactly 48 hours and not a second less. :P Anyways, what I’m trying to say that my email might be funky for the next day or two. Use the gmail account if you need to contact me.
[tags]mx record, dreamhost, google apps, google[/tags]
I did a similar thing the other day at work while moving hosting providers, but instead of chopping off a character, I copied a space in front of the database server’s IP address :mrgreen:
Heh…
Well, good news is that it seems to be working now. Wohoo!