2013-04-15

Repair OOF

How to clean Out of Office Rules using MFCMAPI - Slipstick Systems: http://www.slipstick.com/general/clean-out-of-office-rules-using-mfcmapi/

Exchange 2010 External Out of Office messages not going External: http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/87a815bb-c136-428c-8c69-dc3a69fdfd7f/

Clear OOF Rule in the mailbox:
========================
1. Turn off OOF on a problem user and close Outlook
2. Use MFCMapi tool to logon the problem user’s mailbox (by using Online Mode profile)
3. Expand Root Container->Top of Information Store
4. Right click Inbox folder and click Open Associated contents table
5. Delete following messages if exist:

a. Message class == IPM.Rule.Message
0x65EB001E == Microsoft Exchange OOF Assistant
0x65EC001E == Microsoft.Exchange.OOF.InternalSenders.Global

b. Message class == IPM.Note.Rules.OofTemplate.Microsoft

c. Message class == IPM.Rule.Message
0x65EB001E == MSFT:TDX OOF Rules

d. Message class == IPM.Rule.Message
0x65EB001E == Microsoft Exchange OOF Assistant
0x65EC001E == Microsoft.Exchange.OOF. AllExternalSenders.Global

e. Message class == IPM.Note.Rules.ExternalOOFTemplate.Microsoft

f. Message class == IPM.ExtendedRule.Message
0x65EB001E == Microsoft Exchange OOF Assistant
0x65EC001E == Microsoft.Exchange.OOF.KnownExternalSenders.Global

6. After that, please start Outlook and configure OOF for the user. Please check whether the issue persists.

New-MailboxRepairRequest: Exchange 2010 Help: http://technet.microsoft.com/en-us/library/ff625226(v=exchg.141).aspx

Out of Office not sending replies: http://exchangeserverpro.com/forums/exchange-server-2010/1551-out-office-not-sending-replies.html

Download MFCMapi from Official Microsoft Download Center: http://www.microsoft.com/en-us/download/details.aspx?id=2953

Microsoft Exchange Server MAPI Editor: http://technet.microsoft.com/en-us/library/bb508857(EXCHG.65).aspx

2013-04-01

Convert NDR to LegacyExchangeDN / x500 Custom Address

To create an X500 proxy address for the old LegacyExchangeDN attribute for the user, make the following changes based on the recipient address in an NDR:

IMCEAEX-_O=EXCH_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FHSDHJF23GHYED+29_CN=RECIPIENTS_CN=RON+[email protected]

Convert _ to /

/O=EXCH/OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FHSDHJF23GHYED+29/CN=RECIPIENTS/CN=RON+[email protected]

Next

/O=EXCH/OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FHSDHJF23GHYED+29/CN=RECIPIENTS/CN=RON+2E[email protected]

•Replace any underscore character (_) with a slash character (/)

•Replace "+20" with a blank space

•Replace "+28" with an opening parenthesis character

•Replace "+29" with a closing parenthesis character

•Replace "+2E" with a period

•Delete "IMCEAEX-"

•Delete "@domain.com"

•Add "X500:" at the beginning.

X500:/O=EXCH/OU=EXCHANGE ADMINISTRATIVE GROUP (FHSDHJF23GHYED)/CN=RECIPIENTS/CN=RON.Mayers

 

IMCEAEX non-delivery report when you send email messages to an internal user in Office 365: http://support.microsoft.com/kb/2807779

1.       Clear the auto-complete cache file

2.       Create an X500 proxy address for the old LegacyExchangeDN attribute for the user

Mystery of adding X500’s – What an amazing thing to know…!!! « MSExchangeGuru.com: http://msexchangeguru.com/2012/03/15/x500/

Fixing IMCEAEX NDRs - Missing X500 Addresses: http://www.righthandedexchange.com/2013/02/fixing-imceaex-ndrs-missing-x500.html

Exchange 2010 AutoDiscover - DNS Configuration - SRV Record

You can use Nslookup against a public dns server to verify if the record is correctly configured. 

1)      In the command prompt type nslookup

2)      Type set type=srv

3)      Type _autodiscover._tcp.tenant1.com

 

Server:  hostname.anydomain.com

Address:  10.0.25.5

 

Non-authoritative answer:

_autodiscover._tcp.tenant1.com      SRV service location:

          Priority       =  0

          Weight       =  0

          Port             =  443

          svr hostname  = mail.contoso.com

 

mail.contoso.com internet address = 10.0.25.6

 

Exchange 2010 Multi-Tenant AutoDiscover and DNS Configuration:

http://social.technet.microsoft.com/wiki/contents/articles/5787.exchange-2010-multi-tenant-autodiscover-and-dns-configuration.aspx