Just upgraded from Exchange 2003 to Exchange 2013.  Now the remote Outlook clients, configured with POP are getting multiple copies of their emails.  Seems to run in cycles, where it shoves another copy off on them every 4 or 5 hours.  Have not found the issue, but wonder if I have a mis-configuration on send/receive connectors.  (Total noob on Exchange past 2003).  I have installed a UCC certificate, doesn't look like it is being used in the original receive connectors that Exchange created.  Couldn't determine if I was supposed to remove the original connectors and replace them with ones that I created, or just add the extras in.  Not sure if this is the correct location to post this - my apologies if not.  Thanks for any guidance, and/or pointing me to the correct group and or groups to post this in, as it seems like I may have multiple issue

Stop using POP and deploy Outlook Anywhere.

Ed, that is not helpful, as I cannot get Outlook Anywhere to work, (probably should have thrown that in there at the beginning), which was why I was falling back to Outlook.  Which brings me back to the thought that I have one of my connectors or something else not configured correctly.  I had previously run the analysis tool, which said that OA was ok, with a minor error, but that it passed. Thanks anyhow.

Hi,

I understand your outlook clients are receiving multiple copies of a message when using POP3.

Based on my knowledge, leaving a copy of the message on the server may cause you to receive the same message more than once. We can try to unchecked the option on the account setting.

We can also create a new receive connector to test.

Regards,

David

Thank you David. I did finally get the Outlook Anywhere working, but think I still might have something incorrect, unless I misunderstand how it is supposed to make the connection.  I had to create a VPN to the office in order to get the mailbox authentication to work. After it authenticated, then I was able to remove the VPN connection and it still works.  For some reason, I was thinking that this would be able to find and establish the connections without going through the extra step of the VPN while creating the configuration. Any pointers is much appreciated.  There was one more issue that I had, which perhaps is related to the Outlook emails receiving multiple messages, but unsure. I have had to request delisting from Microsoft.  When I have tested at mxtoolbox.com I do not show up as a an open relay, not listed on blacklists there.  Let me know if this should go to another group.  Thanks again.  Rita

Hi,

I understand your outlook clients are receiving multiple copies of a message when using POP3.

Based on my knowledge, leaving a copy of the message on the server may cause you to receive the same message more than once. We can try to unchecked the option on the account setting.

We can also create a new receive connector to test.

Regards,

David

• Proposed as answer by David Wang_Microsoft contingent staff 6 hours 6 minutes ago

If all is configured properly and the firewall cooperates, an external user should be able to connect by virtue of Autodiscover.  This requires that you have your InternalUrl and ExternalUrl properties configured properly on the various virtual directories and the ExternalHostName and InternalHostName properties properly set in Outlook Anywhere.  You also need a proper certificate and DNS properly configured.  And there are other things that may factor into this.

What I can say is that perhaps I was being impatient with the certificate, as the first 1.5 days, authentication would not work, and I had to make a VPN connection first to get everything to authenticate.  After that time period, the clients are able to authenticate without too many issues, except for the users that are on dialup speed or slower connections. This really makes this a poor solution for them, but they don't want to use webmail, so they will have to live with it, I guess.  I'd say that this is a wrap.

Please feel free to mark answers as helpful and/or the answer as appropriate.