Create Catch-all account for Exchange 2007

Posted on 2009-07-09
Medium Priority
Last Modified: 2012-06-27
I am trying to create a catchall account for Exchange 2007. I read where I had to disable Recipient Filtering on the EDGE server and create a Transport Rule. By doing this I was catching all emails coming in for the company.

All I want to do is catch emails sent to my domain BUT the mailbox name does not exist. (e.g. Bob Smith's email is bsmith@mydomain.com will go right to his inbox but if a message is sent to bobsmith@mydomain.com then have it sent to the catcall account)
Question by:GMSMRM
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
LVL 58

Accepted Solution

tigermatt earned 1600 total points
ID: 24818216

A catch-all account will cause you nothing but problems. It has an administrative overhead to check that mailbox - any email sent to a wrong address will still be accepted, so someone must check that email and process it accordingly.
A catch-all account will also act as a massive spam and virus trap. It is common for abandoners to try simple addresses - e.g. bob@yourdomain.com. All the addresses on their list will be accepted by the server and delivered to the catch-all.

A better solution would be to leave all the standard anti-spam features enabled. This means any email to users who do not exist on the network will automatically be rejected, and an NDR sent to the sender by their mail server. The sender will then know IMMEDIATELY that their message failed, and will take corrective action to ensure it reaches the intended recipient the second time.

Having taken that on board, if you still need a catch-all mailbox, the procedure is at http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/c8fba4d7-4ddb-40ec-b77e-d198da86173f. If you don't have an Edge server, Recipient Filtering is disabled on the Hub Transport server instead.


Expert Comment

ID: 24818350
Are you sure you are configuring the Transport rule for catch-all on Edge server, because it wont work on HUB as it does categorization.

You can follow the link
LVL 76

Expert Comment

by:Alan Hardisty
ID: 24818358
I could not agree more with tigermatt's comments.
Purely on a statistical basis - 97% of all emails are spam (http://news.bbc.co.uk/1/hi/technology/7988579.stm)
So for every 100 good messages your company gets a day, with a catch-all account, you are going to get on average 3,333 spam messages per day.
Over the course of a year, that equates to 1,216,666 messages that are spam.
Do you really want to look through all that for the ocassional message that might be worth reading?
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

LVL 58

Expert Comment

ID: 24818383

To echo Alan's point, consider the disk I/O load that will place the server under. Those emails have to be committed to transaction logs and then to the databases. If you get a sudden burst of spam, you could bring the server to its knees as transaction logs fill the disk.

Email should always be rejected AS SOON as you can tell something is wrong with it. With recipient filtering enabled, this means it is rejected as soon as the sending server mentions a recipient with the wrong email address. The actual email is never exchanged, so the only real load on the server for the spam email dropped this way is a little network activity.

LVL 76

Expert Comment

by:Alan Hardisty
ID: 24818413
Good point - well made.

Author Comment

ID: 24841398
I followed the procedure for creating the catch-all account as suggested, but not suggested, and it works great. However I do consistenatly get emails for employees who are no longer with the company. I added a transport rule to try and drop them but it does not seem to work. Is the catch-all settings overriding this rule?
LVL 76

Assisted Solution

by:Alan Hardisty
Alan Hardisty earned 400 total points
ID: 24841430
A catch-all is simply that - a catch-ALL.
You will receive ALL mail destined to your server no matter what.  Nothing you can do about the old users.

Author Closing Comment

ID: 31601821
Thank you for your fast and clear answers.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
In-place Upgrading Dirsync to Azure AD Connect
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Suggested Courses

801 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question