DNS ADMINS at godaddy need a lesson in RFC's. host -t mx godaddy.com godaddy.com mail is handled by 0 smtp.secureserver.net. godaddy.com mail is handled by 10 mailstore1.secureserver.net. host -t a smtp.secureserver.net smtp.secureserver.net is an alias for smtp.where.secureserver.net. smtp.where.secureserver.net has address 208.109.80.149
That earned them (rightly so) a blacklist entry in bogusmx.rfc-ignorant.org But then again, this is the bunch that blacklisted MY WHOLE CLASS C when a vendor plugged an infected laptop into our conference room jack on the outside of our firewall (vendors are now forbidden from connecting to our network. If they don't have a evdo card they are without internet access) It wasn't until I put a specific RDNS on THE ONE IP ADDRESS IN QUESTION, that they unblacklisted our class c (and they were our registrar. Until they refused to unblacklist us). The ONE IP they had a problem with was 204.89.241.6 (you can check the rdns.. That RDNS made them happy ;-) For anyone who wants to check, the class c in question has been ours since 1994. Portable, owned by us, never EVER registered as dynamic IP addresses, but for ONE IP, godaddy blacklisted the whole class c. So, godaddy, you use SpamAssassin? You read this group? Fix your MX records. -- Michael Scheidell, CTO >|SECNAP Network Security Winner 2008 Network Products Guide Hot Companies FreeBsd SpamAssassin Ports maintainer Charter member, ICSA labs anti-spam consortium _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(tm). For Information please see http://www.spammertrap.com _________________________________________________________________________
