I'm making this announcement because, while we've had the problem for a long time, there's been a lot more of it since we moved servers recently.
If your mail provider (the organization which manages what comes after the @ sign in your protected email address) refuses to accept mail from our server, it's bad for you, because you won't get any mail through us, and it's bad for us, because all your mail goes into a queued error state and starts mucking up our server, and it's bad for you, because the ultimate bounce error message may include your protected address.
By the way, the IP address of our mail server is currently 216.75.62.102
Realize: There's nothing we can do about this!!!! -- the fastest way to solve the problem is to start using a different protected address with a service that doesn't block our server. Contrary to popular belief, you do *not* have to confirm anything on the old address in order to change -- you merely have to confirm the new address using the link in the confirmation email that's sent to it.
The other (and ultimately better) way is for you to convince your service provider to unblock our IP address. They're more likely to listen to you than they are to us, since you're their customer, but if you need us to contact the administrator also, we're generally happy to do so. Remember, they think we're a spammer or they wouldn't have blocked us, so it can be an uphill climb convincing them otherwise.
What's worse, if you contact us and ask us to contact the administrator (like they'll probably tell you to do), it's likely that: a) our email to the administrator will bounce, because they're not accepting mail from our server, and b) our attempt to let you know what happened will also bounce, because they're not accepting mail from our server! (kind of frustrating, to say the least)
Did I mention that the IP address of our server was currently 216.75.62.102?
It sucks to be treated like a spammer when you're running a spam fighting service for free, but there you go.
Here are ones we believe (or know) are blocking us - I'll try to keep this list up to date:
speakeasy.net
mindspring.com (lots of secondary domains, like radiks.net use these servers)
optonline.net (they've pretty much always blocked us - not sure what their issue is)
(took cox.net off the list based on subsequent post)