Aside from basic IP leaks, you can also test for other privacy leaks at: https://emailprivacytester.com/
Featured in: http://www.ghacks.net/2014/05/25/test-email-account-privacy-...
And send GoDaddy a DMCA takedown notice for this copycat site. It was just registered a few days ago and given that they shamelessly ripped your content off, I'd have serious reservations about trusting them with my data.
Seriously though, the presence of a privacy policy gives little comfort when both the website and the Privacy Policy are very careful not to identify who is hosting that domain with Godaddy.
The only real consequence would seem to be loss of good will - but if their goal was to gather as many email addresses as possible in a short time, then that wouldn't really matter.
Notice: This works when you have a separate MSA (submission) service listening on a separate port (587 by default), which is a proper approach; not when you send to MTA on port 25.
I have a self-hosted email, my MUA machine's IP was logged in headers (and there's no particular reason for it to be there), so I googled for a bit, found a satisfying solution among others, and decided to share it. Is there anything wrong with that?
With sendmail redefine RECEIVED_HEADER in sendmail.mc: define(`confRECEIVED_HEADER',`by $j ($v/$Z)$?r with $r$. id $i; $b')dnl
I've been using this to get around the spam filters when sending emails to my clients from my residential IP.
http://www.devside.net/wamp-server/removing-senders-ip-addre...
Sometimes simply registering at a website and looking at the registration confirmation email headers can reveal its real IP.
If they're using some form of artificial delays or greylisting, that's all well and good, but it's not really suitable for this sort of service. I imagine a lot of people would get bored of waiting and just leave.
Err, RFC 1918 anyone?
