25 pts.
 can you remove an old recipient from 1st admin grp in 2007?
We have a very odd issue here. We migrated from 2003 to 2007 on a new server in Feb. Since then the 2003 exchange server has been retired. Emails being sent to one user are coming back with an NDR trying to deliver a message to a delegate that no longer exists. The delegate's account had been deleted over a year ago, but it had not been removed as the user's delegate first. This caused this issue to happen, but I was able to fix it in 2003 after using LDIFDE. The problem went away for months. Now it's showing up again on the 2007 server. When I look in the message log, I see an entry after the one for the email to the orginal user: IMCEAEX-_O=RBFUELS_OU=First+20Administrative+20Group_cn=Recipients_cn=awhitford@RBFUELS.COM rbfuels.com is the domain, awhitford is the user that had been deleted. awhitford does not show as a delegate for mailbox in any OU, (ran LDIFDE on each one). I can view the admin group in ASDIEdit, but can't see any recipients or anything showing awhitford. That admin group has the folder heirarchy, so my understanding is that I can't just delete the entire thing. IS there a command in EMC that can remove the bad recipient? Is there a way to remove

Software/Hardware used:
ASKED: July 28, 2009  6:46 PM
UPDATED: August 20, 2009  3:30 PM

Answer Wiki:
Completely Removing a Mailbox Enabled User's Mailbox If an object is a mailbox enabled user with a valid mailbox, the "Delete Mailbox" option will be available only if there is a mailbox (so a distribution list would have a "Remove email address" option instead). The "Remove Exchange Attributes" option is available for ANY type of recipient object, mail enabled or not. This option is extremely useful when there is a need to "clear" the attributes in case that some of them were damaged or not valid for some reason. Let's say there is a mailbox enabled user that had some of his attributes changed by some process, and because of that, you cannot use the "Delete Mailbox" option. You can always run AdSearch and "clear out" the values so you can start fresh with mailbox enabling that user again. Remove Exchange Attributes removes the following attributes as long as they actually exist as available attributes of that schema object: You can use ADSearch to report the status of each attribute by copying the list below and adding it to the objects attribute properties. adminDisplayName altRecipient authOrig autoReplyMessage (ILS Settings) deletedItemFlags delivContLength deliverAndRedirect displayNamePrintable dLMemDefault dLMemRejectPerms dLMemSubmitPerms extensionAttribute1 extensionAttribute10 extensionAttribute11 extensionAttribute12 extensionAttribute13 extensionAttribute14 extensionAttribute15 extensionAttribute2 extensionAttribute3 extensionAttribute4 extensionAttribute5 extensionAttribute6 extensionAttribute7 extensionAttribute8 extensionAttribute9 folderPathname (Outlook Web Access Server) garbageCollPeriod homeMDB (Exchange Mailbox Store) homeMTA internetEncoding legacyExchangeDN mail (E-Mail Address) mailNickname (Alias) mAPIRecipient mDBOverHardQuotaLimit mDBOverQuotaLimit mDBStorageQuota mDBUseDefaults msExchADCGlobalNames msExchControllingZone msExchExpansionServerName msExchFBURL msExchHideFromAddressLists msExchHomeServerName (Exchange Home Server) msExchMailboxGuid msExchMailboxSecurityDescriptor msExchPoliciesExcluded msExchPoliciesIncluded msExchRecipLimit msExchResourceGUID protocolSettings proxyAddresses (Proxy Addresses) publicDelegates securityProtocol showInAddressBook submissionContLength targetAddress textEncodedORAddress unauthOrig In addition to removing the attributes above, the Delete Mailbox option also removes the mailbox information from the dsaccess cache. Note that this actually leaves the mailbox in place with the expectation that the mailbox cleanup task will take care of it at the appropriate time. So the mailbox is actually NOT deleted (purged) from the Information Store as part of this process. Although it will be purged by the mailbox cleanup task later, or as specified by the "Deletion settings" for mailboxes on the database's Limits tab in ESM.
Last Wiki Answer Submitted:  August 1, 2009  4:38 am  by  Exchange server 2007   605 pts.
All Answer Wiki Contributors:  Exchange server 2007   605 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

It does not show in AD anywhere.

How do I see the recipient in ADSIEdit? I don’t see it with the normal view.

Thanks.

 25 pts.

 

hi ,
please see the link i hope this will help you out to solve .
http://adsearch-winzero.blogspot.com/2008/09/completely-removing-mailbox-enabled.html

thanks


 

 

ADSearch has not helped with this.

The delegate’s account was deleted from AD prior to the upgrade from 2003 to 2007, so I cannot delete it, and the user’s account that this account is delegate to does not show a delegate in it’s properties.

 25 pts.

 

Kev, go into the properties of the mailbox owner’s mailbox who is generating the bounceback for the missing delegate on the Exchange server and then go to the Mail Flow Settings tab, click “Delivery Options” and click “properties”. Is the deleted account or any account listed under “send on behalf of”? If so delete the user there.

 56,975 pts.