Sign in
 
HomeOnline201020072003LibraryForumsPartnersEHLO Blog
Exchange Server TechCenter > Exchange Server Forums > Transport > messages, being retrieved via POP3, are having their alias being replaced by its primary smtp address

Unanswered messages, being retrieved via POP3, are having their alias being replaced by its primary smtp address

    •  
      Thursday, July 05, 2007 8:21 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      We use a CRM tool (Deerfield's VisNetic Mailflow) that POP's into Exchange 2007 to access their mailboxes.  Senders of email to this mailbox use one of many alias' assigned to the mailbox.  The issue we are having is that the alias (ie secondary address) is being replaced by the mailbox's primary address.

      NB When I perform a test without POP'ing  (ie send\receive testing directly between a private external email address and my Exchange mailbox, back and forth), I am successful in retaining the secondary address.

      Any idea what is causing the address to change from the alias (ie secondary) to the primary address when POP'ing?  POP does seem to be the variable here...just not sure what I should be looking at in order to fix this issue.

      Regards,

       

      Andrew

       

    All Replies

    • Friday, August 17, 2007 3:30 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Following up on Andrew's post we're seeing some confirmation of a behaviour change in Exchange 2007:

       

      Dear Colin,

       

      Based on our lab test, it is confirmed that the behavior has changed in Exchange 2007. If a mail is received by Exchange 2007 store, the To field will remain as the intended recipient if you view the mail in Outlook 2003/2007. But the To header will always be changed to primary address if you view the mail in Windows Mail, Outlook Express via POP3 or IMAP. This is the reason that the same copy of a mail will exhibit the different address in header. In Exchange 2007, the real P2 address will be written to email to header only when it is transferred to MAPI format.

      Below is the final test report in our lab

       

      1: Exchange 2003 situation:

       

      Mailbox Name: Test1, Test2.

      Primary email address: Test1@gell.com, Test2@gell.com

      Secondary email address: Test1@e2k3test.com, Test2@e2k3test.com

       

      Use the Test1’s primary email address to send the message to its secondary email address and Test2’s secondary email address, then no matter which type of method we use to open these two mailboxes, the secondary email address will be listed in “to” field in this message’s message header. In the other word, the email address in the “to” field will not be changed to the recipient’s primary email address.

       

      2: Exchange 2007 situation:

       

      Mailbox Name: AA,BB.

      Primary email address: aa@feng.com, bb@feng.com

      Secondary email address: aa@e2k7test.com, bb@e2k7test.com

       

      use aa’s primary email address to send the message to its secondary email address and bb’s secondary email address, then if we use pop3 method to open the message, then we will see the recipient’s Primary email address in the “to” field in this message’s message header. However, if open the message by using Outlook MAPI method, then the recipient’s secondary email address in the “to” field in the message’s message header.

       

      In Exchange 2003 , if send the message to recipient’s secondary email address, then this secondary email address will be shown in the message’s message header without any change.

       

      However in Exchange 2007 situation, once you send the message to the recipient’s secondary email address, then open and view this message’s message header by Outlook MAPI, then the recipient’s secondary email address will still be shown in the “to” field. If we open and view this message’s message header by the POP3 or IMAP method, then the recipient’s primary email address will be shown in the “to” field in Message header instead of its secondary email address. This behavior is the new change in Exchange 2007 situation.

       

      Meanwhile, I have reviewed your replies again and I know that we open the message to your tickets message from the General delivery mailbox using Windows Mail on Vista and an IMAP connection. However, you opened the message to your person mailbox using Outlook 2007 on Vista using a MAPI connection. Hence, we will encounter two different behavior in “to” list in the message header.

       

      I understand that the VisNetic MailFlow application is probably a critical application in your organization. However, it seems this application work with POP3 or IMAP4 method. If so, it may not be able to get the secondary email address in the message’s message header. I am wondering if there is a MAPI versions of this utility so that it can recognize the original header.

       

      I hope my explanation can clarify this issue more explicitly. If you have any question about my explanation, please let me know.

       

      Thanks.

       

      Best regards,
      Jeff Zeng
      Microsoft Messaging Support Service

       
    • Tuesday, August 21, 2007 2:01 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi Andrew,
          Any idea whether Exchange can connect to external Pop3 mailbox?
      Is it possible for Exchange 2007  to send and receive email using 3rd party email hosting?
      And internal users can make use of Exchange address book and calendar?
      Thank you.

      Best regards,
      Sweelong
       
    • Tuesday, August 28, 2007 4:36 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I have a PSS case confirming that this is a bug.  The unfortunately part is that it could take months (post-SP1) before we see a hotfix.

      Sweelong - Exchange Server doesn't have support as far as I'm aware (the Windows SBS drop might).  There are a bunch of third party products that will cover that scenario.  You will need to check with them to see if there is support for E2K7.
       
    • Thursday, November 01, 2007 8:01 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      We are using outlook and have no pop or imap enabled and the "To:" field gets changed to the primary smtp address rather than showing as the secondary smtp address. Can anyone shed some light on what may be causing this?

       
    • Thursday, June 26, 2008 2:58 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Has this issue been resolved, or has anyone found a workaround for this? We have recently upgraded to 2007 and have an application which relies on the alias email address to route documents. Thanks!

       
    • Wednesday, November 11, 2009 2:53 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      this appears to still be happening as at 11nov 2009

      i have an sp1 exchange 2007 server (sbs 2008) which still does this.

      Does anyone know if it can be resolved?

       
    • Wednesday, June 09, 2010 1:36 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      hi,

      with exchange 2010 this "behavoiour" is still the same. for me that is a big productivity problem because we have to use silly workarounds like outlook rules moving different alias receipients to different folders :(

      will this ever be fixed??

       
    • Wednesday, December 08, 2010 4:29 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Has anyone discovered a solution to this?

      We are retrieving messages via IMAP and the same thing is happening.
      It is changing the alias to the primary email account in the header.

      ~ RealManage IT

      ~ RealManage IT
       
    • Wednesday, December 29, 2010 4:59 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I am also having the same issue - has any one found a work around?

      I've just installed 2007 sp3 rollup - didn't fix this bug

       
    • Thursday, April 12, 2012 12:16 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      We have the same issue with exchange 2007. is there any fix for this?

      Thx