I've created a service account mailbox in exchange 2010 that I need to use for a custom application. However, I don't want it to receive any emails. If I restrict the "Mailbox Settings => Storage Quotas => Prohibit send and receive at" to a small number as a workaround, will an "Undeliverable" message be sent to any user emailing to the global address list once the mailbox reaches its limit?
Does the “Undeliverable” message get sent if an email targets the global address list
exchangeexchange-2010
Related Solutions
I've seen errors similar to this one, but it wasn't related to Outlook SP2. It was related to removing the last vestiges of the Exchange 2003 routing groups after we fully completed the migration to Exchange 2007. What was happening is that Outlook was storing the names of the mailboxes internally using an AD syntax to describe where to find the mailbox. Exchange 2007 uses a different location for that. This caused havoc in things like Delegates, replying to old emails, and the frequently-mailed-contacts list.
What was happening was that each user that was migrated from Exch2003 had an attribute called "LegacyExchangeDN" that pointed to the old AD location. Users created fresh in Exch2007 didn't have it, and didn't need it. After opening an SR with Microsoft to figure out what the heck, the fix was to add a new X500 address to each mailbox to the value of the old LegacyExchangeDN. This allowed cached Outlook entries (and there are a LOT of them) to find the mailbox.
That's a system-level fault, and it may not be your problem. But your symptoms seem close to what I've seen.
Yes, those articles you mentioned pretty much take care of what you would need to do. How are you sending/receiving e-mail externally? Are you using an Exchange Edge server, or something else? I recently had to do something similar to this because I'm moving my company over to Exchange 2010 from a third-party e-mail system, and both have to exist at the same time for a while. I have a Barracuda spam filter for external mail, but you should be able to do the same with whatever you use. This will also be dependent on the Exchange 2010 server being able to handle the mail for both sides because I know Exchange 2010 has the features I needed to use.
Set the external SMTP server to relay all mail (both old domains and the new one) to the Exchange 2010 server. You can then use those articles to set up Exchange 2010 to have the 2003 old domain and the new domain as internal relay domains, and you can relay all mail using the Exchange 2003 old and new domains over to the 2003 server using a send connector. Using this article, you can set Exchange 2010 to allow your users to receive e-mail on their old domain, and set the default reply-to address to be the new address. This will allow for sent e-mails to show the new domain.
The last piece would be Exchange 2003, which I unfortunately don't have any experience with. Hopefully you can apply similar settings to have the 2003 server relay mail for the 2010 old domain over to the 2010 server, and use the correct e-mail addresses. You would also need to relay the new domain over to 2010 for accounts that don't exist on the 2003 server.
If your bonus question is because there is a possibility of upgrading 2003 to 2010 first, this might be the better way to go. However, I only say that because I am unfamiliar with 2003, so I'm not sure how possible my solution is in your situation.
Thanks, Paul
Best Answer
To answer your question directly, yes people (inside the organization) should get an undeliverable message if the message is rejected because of quota limits.
However, I would take a different approach. In Exchange 2010, your Exchange administrator can go into the EMC and create a transport rule which applies specifically to this mailbox with the actions of "send rejection message to sender with enhanced status code", or "Delete the message without notifying anyone".
This is something that, in the future, will be a lot easier for people to understand (assuming you and/or the exchange admin ever leave).