You could try using OpenDNS instead of your local DNS to help sort out if it's a DNS problem. But it does sound more like heavy-handed filtering.
I did find this interesting bit of information which might be related: http://emaildeliveryjedi.com/email-blog/ "Email Delivery and Your Email Reputation: Don't Call Yourself a Spammer June 7, 2008 – 9:13 am How could you possibly ruin your Email Delivery and mark your own email IP address as sending spam? Yes you really can be clicking the "This is Spam" button on yourself. It happens quite easily and you may have already done this yourself. The problem is that an automated spam filter is simply unable to determine what is spam and what is a forward. Here's a break down of the problem using Comcast as an example. You setup an auto forwarder from your domain to your Comcast email account. This also occurs often when you forward email from your work email account. You are forwarding mail from [email protected] to [email protected]. When your customers send emails to [email protected] the email gets forwarded to [email protected] One day you receive some spam at [email protected], which was auto forwarded directly from [email protected]. You open your [email protected] mail box and see the spam, so you click to "Mark it as SPAM" and add it to your Comcast spam filter . You have just entered a spam complaint against your own email server! Comcast's spam filter does not register the originator of the email as the spammer - instead, it registers the last place the email came from as the Spammer and in this case and the last place the email came from is your email server which is the outgoing email server for hosts [email protected]. Comcast will then blacklist the entire mail server so that no one can send email to any Comcast email accounts. They will then contact your host and ask that your domain be deleted. Until then Comcast will block all email from the outgoing SMTP servers associated with your server (thru reverse DNS). Solution: What do I need to do you ask? You need to login to your email admin on your domain and go through your email accounts and take off any forwarding that forwards email to any account or any other ISP. Also check to make sure your email Alias is not forwarding to any email account or any other ISP. Although it might be an inconvenience to many, I think this decision is necessary to protect our mail servers from being blacklisted by ISPs in this way. Verizon, Comcast or AOL certainly do nothing to investigate the source of the spam and would rather shut down a server than take a minute to check it out. Please note, this does not mean you cannot send emails to Verizon, Comcast, AOL or other ISP based email accounts. This simply means you should not set your email account to auto forward emails. You will still be able to compose your own email to ISP users, and you will be able to forward an email to those users from your mailbox manually." Richard P. On Sat, Dec 13, 2008 at 9:20 AM, Mike Sloane <[email protected]> wrote: > Thanks, Mike. I agree with you 100%, and that is why I also have Yahoo and > Gmail accounts for those reasons. But I was wondering if any other members > of this group had encountered the same problem, or is it something related > to my verizon ID. Or maybe a local DNS problem (I am in NJ). > > Mike (S) ************************************************************************* ** List info, subscription management, list rules, archives, privacy ** ** policy, calmness, a member map, and more at http://www.cguys.org/ ** *************************************************************************
