We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Create Catch-all account for Exchange 2007

Dennis Janson
on
Medium Priority
687 Views
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)
Comment
Watch Question

Site Reliability Engineer
CERTIFIED EXPERT
Most Valuable Expert 2011
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Commented:
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
http://technet.microsoft.com/en-us/library/bb691132.aspx
Alan HardistyCo-Owner
CERTIFIED EXPERT
Top Expert 2011

Commented:
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?
tigermattSite Reliability Engineer
CERTIFIED EXPERT
Most Valuable Expert 2011

Commented:

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.

-Matt
Alan HardistyCo-Owner
CERTIFIED EXPERT
Top Expert 2011

Commented:
Good point - well made.
Dennis JansonIT Manager

Author

Commented:
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?
Alan HardistyCo-Owner
CERTIFIED EXPERT
Top Expert 2011
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
Dennis JansonIT Manager

Author

Commented:
Thank you for your fast and clear answers.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.