Catch-all Forward Disabling Postponed, Dedicated and GMail Exempted

We appreciate the feedback/concern that has been sent in via support over the weekend regarding the catch-all forwarding change. I’m sorry if we caused anyone to panic! We are simply eager to resolve the blacklisting problems we’ve had as quickly as possible.

We’re going to postpone the actual disabling of external catch-all forwarding until next Monday (June 19th) to give some of you who need to coordinate with your own clients more time to do so. You still can’t add new ones in the panel, but existing catch-all forwards will not be disabled until the 19th.

Further, since it seems a *lot* of people are forwarding catch-alls to GMail to use their fancy filtering, and the fact that Google hasn’t been causing us problems with blocks, we’re going to exempt forwards to GMail from the disabling. It is not feasible to offer this to all domains except those that we know are blocking us regularly (such as AOL) because many email providers employ realtime blacklists (RBLs: http://en.wikipedia.org/wiki/DNSBL) that do spam checks, and some of these tend to ‘ding’ us for forwarded spam as well, and contribute to mail getting blocked in a whole slew of mail systems around the internet.

So, less-wordy summary:

-Catch-all forwarding will be disabled next Monday, June 19th.
-You can still forward catch-alls to GMail accounts.
-[Edit] Almost forgot: Dedicated Servers will not be affected, even though they got the initial notices.

As usual, thank you for your feedback and patience.

Comments are closed.