Temporarily re-enabling catch-all domains
by George RobertsWe’re temporarily re-enabling the domains that have catch-alls or are not properly rejecting unknown users during the SMTP transaction to give our customers some time to get the issue fixed. Please remember that you can log into the Account Manager and go to the Tools tab to see the catch-all report so you know which domains you need to fix.
We will be re-running the disable process this weekend, so get these fixed before the end of the week. We will be running the disable process at 11:59pm central US time on Saturday, February 28th.
For more information on catch-alls and why we don’t allow them, see this knowledgebase article and this knowledgebase article. For Exchange users, please see this knowledgebase article on how to properly configure Exchange to reject invalid users at the SMTP transaction level.



February 25th, 2009 at 5:48 pm
I just installed a new Exchange 2007 server for this client: greyandgrey.com
How do I turn off catch-all’s to this version of Exchange.
Your procedure does not include this version.
In the Exchange Management Shell, I ran the command:
Set-RecipientFilterConfig -RecipientValidationEnabled:$true
Is this all I need to do?
Thanks!
Anthony
February 25th, 2009 at 7:14 pm
As far as I can tell, Exchange 2007 by default enables SMTP transaction level rejection of messages to non-existant users. If you’d like us to test the server to see if it’s working properly, please send an email to support@easyantispam.com with the hostname or IP address of the Exchange 2007 server and we’ll run a quick test.
February 26th, 2009 at 10:05 am
In these last “few hours”, would it be possible for you to have your report generate every hour instead of every week? I am scrambling to notify all of the domains that are listed in your report (thank you for providing that by the way), but would really like to know if our clients are fixing them.
February 26th, 2009 at 2:10 pm
Travis, that’s a good idea. I’ll have to change our testing script to only check those that are currently marked as having catch-alls, though, as the full check takes about 24 hours to go through all of the domains.