none
Outlook returns email from user not in Active Directory RRS feed

  • Question

  • Outlook 2007.  User sends email to a group in the GAL.  User receives back a message that the "account does not exist."  The account in question is not a member of the GAL Group, Active Directory and is not in Outlook Contacts.  What could be triggering this returned email?  or what is sending this email to this account?

    The bounced user was an employee at one time, but have since left the company. 

     

     

    • Edited by bill4343 Thursday, November 17, 2011 9:55 PM
    • Moved by Max Meng Friday, November 18, 2011 1:53 AM Moving to a more appropriate forum (From:Outlook IT Pro Discussions)
    Thursday, November 17, 2011 9:33 PM

Answers

  • On Fri, 18 Nov 2011 17:19:08 +0000, bill4343 wrote:
     
    >but wouldn't the undeliverable message come from the user who had delegated rights?
     
    No, the sender remains the same. The message isn't forwarded, it's
    redirected (well, not exactly, but that's the easiest way to explain
    it).
     
    >This person is not a delegate for the sender.
     
    Of course not. But it may have been a delegate on one of the
    recipients, or one of the recipients has a redirect rule.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Friday, November 18, 2011 10:13 PM
  • On Mon, 21 Nov 2011 20:17:15 +0000, bill4343 wrote:
     
    >
    >
    >Looking at this kb http://support.microsoft.com/kb/312433 it refers to this not currently a domain user being a delegate somewhere. But it also suggests
    >
    >To identify a delegate rule and remove the delegate rule from a mailbox, follow these steps: 1. Make sure that Outlook is not currently running on the workstation. 2. Start the Mdbvu32.exe utility, and then click OK in the first dialog box, to log on. 3. On the MDB menu, click OpenMessageStore. 4. Click the relevant mailbox, and then click Open to start the store. 5. On the MDB menu, click Open Root Folder. 6. Double-click Top of Information Store in the Child Folders area. 7. Double-click Inbox in the Child Folders area to view the properties of the Inbox folder. 8. Locate the Associated Message in FLD: pane of the MAPI_FOLDER-Inbox window. Notice the items that start with *pb EF 00 00 00 19 82 62. Each of these is a rule that is set up on the Inbox. The user can set up some of the rules. Other rules are for things like using the Out of Office Assistant or forwarding meeting responses to a delegate. 9. Double-click each of the rules in turn, to open the rule and examine the rule to
    >determine which rule is the delegate rule. Check the Message Property 0x65EB. The delegate rule should have the Schedule + EMS Interface for this property. 10. When you find the corresponding rule, check the message property 0x65EF, which is a long, double-byte string of characters. If the string starts with 02, the rule states, "Send meeting requests and responses only to my delegates, not to me." If the string starts with 01, the rule states, "Delegate receives copies of meeting-related messages sent to me." If either of these options is set in Outlook, and there is no message or rule under Associated Message in FLD:, the rule no longer exists, which explains why the requests and responses are not being forwarded. You can also delete the delegate rule from here. 11. After you identify the delegate rule, select the rule in the Associated Message in FLD: pane of the MAPI_FOLDER-Inbox window. 12. In the Operations available box, click lpFld->DeleteMessages(), and then click Call
    >Function. 13. When the MAPI_FOLDER-Inbox->DeleteMessages() window appears, click OK to delete the message. 14. Quit Mdbvu32.exe by closing all windows until you return to the MDB Viewer Test Application window. 15. On the MDB menu, click Store Logoff, and then click OK. 16. Click OK in the LOGOFF_COMPLETE window. 17. Close the MDB Viewer Test Application window.
     
    That's one way to do it.
     
    MDBView may not work, though. Using MFCMapi may be necessary. It's
    pretty much the same set of instructions.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Monday, November 21, 2011 10:28 PM
  • Hello,

     

    Is there any updates?

     

    Thanks,

     

    Evan Liu

     

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

     

    • Marked as answer by bill4343 Thursday, December 15, 2011 9:41 PM
    Friday, November 25, 2011 1:29 AM
    Moderator

All replies

  • On Thu, 17 Nov 2011 21:33:24 +0000, bill4343 wrote:
     
    >
    >
    >Outlook 2007. User sends email to a group in the GAL. User receives back a message that the "account does not exist." The account in question is not a member of the GAL Group, Active Directory and is not in Outlook Contacts. What could be triggering this returned email? or what is sending this email to this account?
    >
    >The bounced user was an employee at one time, but have since left the company.
     
    Someone may have a rule in their Inbox that refers to that missing
    user. It may also be a similar situation with a missing user still
    being used as a delegate on someone's mailbox.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Friday, November 18, 2011 4:52 AM
  • but wouldn't the undeliverable message come from the user who had delegated rights?  This person is not a delegate for the sender. 
    bill westman
    Friday, November 18, 2011 5:19 PM
  • On Fri, 18 Nov 2011 17:19:08 +0000, bill4343 wrote:
     
    >but wouldn't the undeliverable message come from the user who had delegated rights?
     
    No, the sender remains the same. The message isn't forwarded, it's
    redirected (well, not exactly, but that's the easiest way to explain
    it).
     
    >This person is not a delegate for the sender.
     
    Of course not. But it may have been a delegate on one of the
    recipients, or one of the recipients has a redirect rule.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Friday, November 18, 2011 10:13 PM
  • I also suggest you try to check whether there is any transport rule that copy (or redirect) email to the problem account.

     

    Thanks,

     

    Evan Liu

     

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

    Monday, November 21, 2011 6:29 AM
    Moderator
  • Looking at this kb http://support.microsoft.com/kb/312433 it refers to this not currently a domain user being a delegate somewhere. But it also suggests

    To identify a delegate rule and remove the delegate rule from a mailbox, follow these steps:

    1. Make sure that Outlook is not currently running on the workstation.
    2. Start the Mdbvu32.exe utility, and then click OK in the first dialog box, to log on.
    3. On the MDB menu, click OpenMessageStore.
    4. Click the relevant mailbox, and then click Open to start the store.
    5. On the MDB menu, click Open Root Folder.
    6. Double-click Top of Information Store in the Child Folders area.
    7. Double-click Inbox in the Child Folders area to view the properties of the Inbox folder.
    8. Locate the Associated Message in FLD: pane of the MAPI_FOLDER-Inbox window. Notice the items that start with *pb EF 00 00 00 19 82 62. Each of these is a rule that is set up on the Inbox. The user can set up some of the rules. Other rules are for things like using the Out of Office Assistant or forwarding meeting responses to a delegate.
    9. Double-click each of the rules in turn, to open the rule and examine the rule to determine which rule is the delegate rule. Check the Message Property 0x65EB. The delegate rule should have the Schedule + EMS Interface for this property.
    10. When you find the corresponding rule, check the message property 0x65EF, which is a long, double-byte string of characters. If the string starts with 02, the rule states, "Send meeting requests and responses only to my delegates, not to me." If the string starts with 01, the rule states, "Delegate receives copies of meeting-related messages sent to me." If either of these options is set in Outlook, and there is no message or rule under Associated Message in FLD:, the rule no longer exists, which explains why the requests and responses are not being forwarded. You can also delete the delegate rule from here.
    11. After you identify the delegate rule, select the rule in the Associated Message in FLD: pane of the MAPI_FOLDER-Inbox window.
    12. In the Operations available box, click lpFld->DeleteMessages(), and then click Call Function.
    13. When the MAPI_FOLDER-Inbox->DeleteMessages() window appears, click OK to delete the message.
    14. Quit Mdbvu32.exe by closing all windows until you return to the MDB Viewer Test Application window.
    15. On the MDB menu, click Store Logoff, and then click OK.
    16. Click OK in the LOGOFF_COMPLETE window.
    17. Close the MDB Viewer Test Application window.

    bill westman
    Monday, November 21, 2011 8:17 PM
  • On Mon, 21 Nov 2011 20:17:15 +0000, bill4343 wrote:
     
    >
    >
    >Looking at this kb http://support.microsoft.com/kb/312433 it refers to this not currently a domain user being a delegate somewhere. But it also suggests
    >
    >To identify a delegate rule and remove the delegate rule from a mailbox, follow these steps: 1. Make sure that Outlook is not currently running on the workstation. 2. Start the Mdbvu32.exe utility, and then click OK in the first dialog box, to log on. 3. On the MDB menu, click OpenMessageStore. 4. Click the relevant mailbox, and then click Open to start the store. 5. On the MDB menu, click Open Root Folder. 6. Double-click Top of Information Store in the Child Folders area. 7. Double-click Inbox in the Child Folders area to view the properties of the Inbox folder. 8. Locate the Associated Message in FLD: pane of the MAPI_FOLDER-Inbox window. Notice the items that start with *pb EF 00 00 00 19 82 62. Each of these is a rule that is set up on the Inbox. The user can set up some of the rules. Other rules are for things like using the Out of Office Assistant or forwarding meeting responses to a delegate. 9. Double-click each of the rules in turn, to open the rule and examine the rule to
    >determine which rule is the delegate rule. Check the Message Property 0x65EB. The delegate rule should have the Schedule + EMS Interface for this property. 10. When you find the corresponding rule, check the message property 0x65EF, which is a long, double-byte string of characters. If the string starts with 02, the rule states, "Send meeting requests and responses only to my delegates, not to me." If the string starts with 01, the rule states, "Delegate receives copies of meeting-related messages sent to me." If either of these options is set in Outlook, and there is no message or rule under Associated Message in FLD:, the rule no longer exists, which explains why the requests and responses are not being forwarded. You can also delete the delegate rule from here. 11. After you identify the delegate rule, select the rule in the Associated Message in FLD: pane of the MAPI_FOLDER-Inbox window. 12. In the Operations available box, click lpFld->DeleteMessages(), and then click Call
    >Function. 13. When the MAPI_FOLDER-Inbox->DeleteMessages() window appears, click OK to delete the message. 14. Quit Mdbvu32.exe by closing all windows until you return to the MDB Viewer Test Application window. 15. On the MDB menu, click Store Logoff, and then click OK. 16. Click OK in the LOGOFF_COMPLETE window. 17. Close the MDB Viewer Test Application window.
     
    That's one way to do it.
     
    MDBView may not work, though. Using MFCMapi may be necessary. It's
    pretty much the same set of instructions.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Monday, November 21, 2011 10:28 PM
  • If you want to delete the delegate’s rule, MFCmapi is a better choice. The Microsoft® Exchange Server MAPI Editor Tool, which is a sample MAPI client, replaces the Information Store Viewer (MDBVu32).

     

    You can know more information about MFCmapi from this document:

     

    Microsoft Exchange Server MAPI Editor

    http://technet.microsoft.com/en-us/library/bb508857(EXCHG.65).aspx

     

    You can download this tool here:

    http://mfcmapi.codeplex.com/

     

     

    Thanks,

     

    Evan Liu

     

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

    Tuesday, November 22, 2011 2:34 AM
    Moderator
  • Hello,

     

    Is there any updates?

     

    Thanks,

     

    Evan Liu

     

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

     

    • Marked as answer by bill4343 Thursday, December 15, 2011 9:41 PM
    Friday, November 25, 2011 1:29 AM
    Moderator