none
Error 550 5.1.1 while OOF is activated

    Question

  • Hi all,

    One of our Exchange 2013 CU9 user systematically receives an error 550 5.1.1 when an incoming email arrives whereas OOF activated.

    This error is about an email deliver failure to a recipient that has been deleted.

    When I look for a possible email rule, I find nothing. In addition, this issue occurs only when OOF is activated.

    Any idea about that ?

    Thank you.


    FXE

    Tuesday, October 27, 2015 10:48 AM

Answers

All replies

  • Hi,

    Please can you send the NDR. Please also check the message tracking logs for any emails that were received from the deleted user email address before the error was received. It's possible that the user is still receiving emails from the deleted user email address if there is a server configured to send email as this user or if there are spoofed emails from the internet. Message tracking can help you find out where the emails are coming from if this is the case. 

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010, MCTS SQL 2012, MCTS SharePoint 2007, VCP4, VCP5, CCNA

    Blog: http://markgossa.blogspot.com LinkedIn:

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Tuesday, October 27, 2015 11:43 AM
  • Hi and thank you for your answer.

    Here the NDR received :

    Serveur de génération : MyExchangeServerFQDN
    En-têtes de message d'origine :

    Received: from MyExchangeServerFQDN (ExchangeServerIPAddress) by MyExchangeServerFQDN (ExchangeServerIPAddress) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 27 Oct 2015 10:30:21 +0100 Received: from MyExchangeServerFQDN (ExchangeServerIPAddress)by MyExchangeServerFQDN (ExchangeServerIPAddress)with Microsoft SMTP Server id 15.00.1104.000; Tue, 27 Oct 2015 10:30:21 +0100 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: User with OOF activated To: Deleted user <IMCEAEX-_o=Organisation+20MYORGANIZATION_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=user0193883c@MyDomain.local> Subject: TR : Test 3 Thread-Topic: Test 3 Thread-Index: AdEQmhZYM5+MJmjsRPmJfNNi+GaL4gAAAN4M References: e40482408ad143208fa5b0d1acb6a7ee@ExchangeServerFQDN In-Reply-To: <e40482408ad143208fa5b0d1acb6a7ee@ExchangeServerFQDN> X-MS-Has-Attach: X-MS-Exchange-Inbox-Rules-Loop: User with OOF activated email address

    X-MS-TNEF-Correlator: 74600c0f-50bc-47f5-bf43-d37d50941d46 MIME-Version: 1.0 Date: Tue, 27 Oct 2015 10:30:21 +0100 X-MS-Exchange-Transport-FromEntityHeader: Hosted Message-ID: <34adfc8f1ea046d5a6d9e8781902da06@ExchangeServerFQDN> X-MS-Exchange-Parent-Message-Id: <e40482408ad143208fa5b0d1acb6a7ee@ExchangeServerFQDN> Auto-Submitted: auto-generated X-MS-Exchange-Generated-Message-Source: Mailbox Rules Agent Return-Path: user with OOF activated email address

    Message tracking logs returns nothing about user0193883c@MyDomain.local.

    Regards,


    FXE

    Tuesday, October 27, 2015 12:52 PM
  • Hi,

    Please can you double check your rules in Outlook and on Exchange.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010, MCTS SQL 2012, MCTS SharePoint 2007, VCP4, VCP5, CCNA

    Blog: http://markgossa.blogspot.com   LinkedIn:

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Tuesday, October 27, 2015 1:18 PM
  • Hi Mark,

    Here the rules parameters user side :

    Here the transfer rule server side :

    Regards,


    FXE



    • Edited by FXE Tuesday, October 27, 2015 1:29 PM
    Tuesday, October 27, 2015 1:27 PM
  • Hi,

    Please can you also check the user's Outlook on their workstation.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010, MCTS SQL 2012, MCTS SharePoint 2007, VCP4, VCP5, CCNA

    Blog: http://markgossa.blogspot.com   LinkedIn:

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Tuesday, October 27, 2015 1:48 PM
  • Hi,

    No rule is set Outlook client side :

    Regards,


    FXE

    Tuesday, October 27, 2015 5:03 PM
  • Hi,

    Please can you check for issues in the application event log and run a New-MailboxRepairRequest if needed. More information is here: https://technet.microsoft.com/en-us/library/ff625226(v=exchg.160).aspx.

    You may also find that there is database corruption. In this case, you will need to migrate mailboxes into a new mailbox database (reduced downtime compared to an offline defrag).

    Another thing you can try is to recreate the problem mailbox. See a script to do this here: https://gallery.technet.microsoft.com/Recreate-mailbox-on-084b663f.

    Let me know how it goes.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010, MCTS SQL 2012, MCTS SharePoint 2007, VCP4, VCP5, CCNA

    Blog: http://markgossa.blogspot.com   LinkedIn:

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Thursday, October 29, 2015 9:55 AM
  • Hi Mark,

    Nothing about this user's mailbox issues in Aplication event logs.

    Is there a method for detecting any corruption on database or mailbox before make a repair ?

    Regards,


    FXE

    Thursday, October 29, 2015 10:52 AM
  • Ok I found the how to.

    So I ran the 4 corruption types New-MailboxRepairRequest against the mailbox, and no error was reported.


    FXE

    • Proposed as answer by David Wang_Moderator Thursday, October 29, 2015 1:39 PM
    • Unproposed as answer by FXE Thursday, October 29, 2015 2:38 PM
    Thursday, October 29, 2015 11:24 AM
  • Hi,

    In this case, before you try recreate the mailbox, move it to another database. If this doesn't work then try recreate the mailbox. 

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010, MCTS SQL 2012, MCTS SharePoint 2007, VCP4, VCP5, CCNA

    Blog: http://markgossa.blogspot.com   LinkedIn:

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Thursday, October 29, 2015 12:15 PM
  • Try running Clean-MailboxDatabase Databasename

    Also check if same is happening with the mailboxes created in a fresh new DB.


    Please mark as an answer if this answers your question .

    PREM RANA

    MCSE Exchange 2013, MCSA 2012 Server MCTS Exchange 2007,

    2010, MCITP Exchange 2007, 2010 MCSE 2003 Server,

    MCSA Exchange 2003 ITIL V3 Foundation

    https://ranaprem.wordpress.com/

    This posting is provided AS IS with no warranties and confers no rights.

    Thursday, October 29, 2015 12:33 PM
  • I moved this mailbox to another database, and the issue persists.

    The command Clean-MailboxDatabase databasename seems not exist.


    FXE

    Thursday, October 29, 2015 3:58 PM
  • Hi,

    This cmdlet doesn't exist in Exchange 2013. Use the Update-StoreMailboxState cmdlet instead. See here: http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/clean-mailboxdatabase-exchange-2013.html

    If you still have problems after this, try recreate the mailbox using the script I provided earlier.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010, MCTS SQL 2012, MCTS SharePoint 2007, VCP4, VCP5, CCNA

    Blog: http://markgossa.blogspot.com   LinkedIn:

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Thursday, October 29, 2015 4:48 PM