I believe he has already stated elsewhere that he uses Gmail. See here.
Disallowing catch alls would be fine by me. I tell all my clients that they’re crazy if they use them. I can think of only one that has ever set up a catch all. To my knowledge, he quickly disabled it after receiving tons of spam.
Tim
I have a customer who is using catch-all to have all mail delivered to a server, and that server is spreading the mail over his organisation.
Also some customers like to have catch-all enabled, a good spam-filter nowadays should be able to get out the bulk-spam (with antispam delays etc).
So my advice would be not to system-wide disable catch-all, let it be the choice of the customer, and respect the customer who wants it enabled!
Jan-Pieter
That is an interesting scenario. If the client has a mail server, why not just point the MX record there?
Another great benefit if you repoint your MX is that you do not use up any Jodo bandwidth (big benefit, in my opinion).
We are indeed aware of such needs and this is one reason catch-alls are still there, but we need to consider what is in benefit of most. With the new dspam based mail setup we may be able to continue with catch-alls for some time as the issue isn’t as serious at the moment since our deployment of new gateway.
I really wish if there is justification based catch-all possible with Hsphere, where we may know the reason for its usage (some just use it to collect mails and also forward a copy to some unused ISP account) and limit overall abuse of this feature.
It is mostly due to unavailability of a static IP or required infrastructure(server, anti-spam/anti-virus, etc). But I agree, if possible actual server must be used for MX.