Stop Exchange 2007 from sending email
Environment - Windows 2008 SP2 with Exchange 2007 SP3 Roll #1. Have accounts used for upper management - if these accounts get full or have an issue, exchange sends a message back to the sender stating such a problem. Is there any way NOT to send these emails back to the sender for these particular email accounts? Thanks in advance
November 30th, 2010 10:17am

Please clarify ,, what is meant by ? Have accounts used for upper management - if these accounts get full or have an issue, exchange sends a message back to the sender stating such a problem
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2010 2:15pm

If one from the upper management has a full mailbox i think he/she would want to know. If the upper management should not have limits for some reason then just remove it from them, then they won't receive any of these mails. Regarding other issues I am with Khoj, we need a bit more information to answer that part. /MartinExchange is a passion not just a collaboration software.
November 30th, 2010 2:24pm

Is there any way NOT to send these emails back to the sender for these particular email accounts? You're confused. I don't want the email going to the "sender" stating the upper management email is full or experiencing issues. How do I stop exchange from sending such a message back to the "sender".
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2010 3:08pm

Hi, Under the limits tab on either the specific mailbox or the mailbox database you can deselect the limit saying "prohibit receivng mail" that will solve the problem. /MartinExchange is a passion not just a collaboration software.
November 30th, 2010 3:20pm

This is Exchange 2007 - their is no limits tab on a specific mailbox and I don't want to do this on a database. Come to think of it, wouldn't this stop all email from being received by the specific mailbox - I only want to stop the email generated by exchange for certain conditions and apply this to certain mailboxes.
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2010 3:31pm

Hi, Here is how to set the limits in 2007, and it can be done on a single mailbox. http://technet.microsoft.com/en-us/library/aa998353(EXCHG.80).aspx I am not sure what other conditions you are refering to so I only answered regarding the limit you don't want the sender seeing. /MartinExchange is a passion not just a collaboration software.
November 30th, 2010 4:17pm

I don't want email going to the "sender" stating the upper management email is full or experiencing issues. How do I stop exchange from sending such a message back to the "sender"?
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2010 4:21pm

You clearly don't understand what I'm asking for. Maybe this will help - I don't want the sender to get this message or similiar - sender being nancy ******************************************************************************* -----Original Message----- From: Mail Delivery System Sent: Monday, November 29, 2010 7:38 PM To: Nancy Subject: Warning: could not send message for past 4 hours =============================================== THIS IS A WARNING MESSAGE ONLY YOU DO NOT NEED TO RESEND YOUR MESSAGE =============================================== A temporary error occured while delivering to the following address(es): itlarc@xyz: Connect to host itlpax.com:/mxl/var/sockets/mta_outbound failed: Connection refused.com I will continue trying to send the message until it is delivered or expires. ***************************************************************************** The sender doesn't know who itlarc@xyz.com is - its a bogus email account which emial is copied for security reasons and for backup purposes.
November 30th, 2010 4:27pm

Hi, Like the article shows. The sender will only get that error if the mailbox limit "Prohibit send and receive at (KB)" is set. This is normally only done on the Mailbox Database, but you can override that with removing the limit on the individual mailbox. /Martin Exchange is a passion not just a collaboration software.
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2010 4:31pm

What am I not making clear - Sender "A" sends an email to receiver "A". All is fine. Also, behind the scenes - sender "A"s email is copied to receiver "B" - which sender "A" has NO idea this is done. When Receiver "B" email has issue like one stated above, how do I stop a return email to Sender "A" like one stated above. Overriding the limit size is NOT the answer - I still need this in place for Receiver "B".
November 30th, 2010 4:39pm

Hi, Now I at least understand, I didn't read anything about it being a forward mail that was set on the mailbox by the administrator. Unfortunently I do not have an answer to that issue, as far as I know this is by design and the sender should get an error report for these errors. If you try to remove them with a transport rule you will also remove other error reports that you would want to get to sender "A". /MartinExchange is a passion not just a collaboration software.
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2010 4:46pm

Correct a transport rule would not be effective is this type of situation. Would think there would be some way of controlling these messages.
December 1st, 2010 8:05am

It is kind of hard controlling them because Exchange won't know the difference of a valid error message and a error not wished. The full mailbox has to sent out the information to others who needs to know it is full, and the person who you don't want to receive a message on a specific mailbox still wants to get an error message when he sents to other users with a mailbox limit on. /MartinExchange is a passion not just a collaboration software.
Free Windows Admin Tool Kit Click here and download it now
December 1st, 2010 9:10am

Yeah, now that I think about it - it's a catch 22 - can't win either way. Thanks for the info and help.
December 1st, 2010 9:39am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics