Hi Parmjit, I am suspecting the message removed to your Outlook client due to POP3 downloading feature. However, the decription is confusion: There are two accounts in users' Outlooks, one is Exchange account for Exchange mailbox resided in your ISP, the other is POP3 account for the SAME Exchange mailbox resided in your ISP, right? What does it mean by "the message does not go to the ISP server WHEN ..."? The message stucked in Outbox of Exchange account? or it was "Moved" to Inbox of your Pop3 account? Who did not receive messages on their mobile devices, the internal recipients or the message sender? Can you get message tracking log from your Exchange server, or disable POP service for a temp test? Thanks. Fiona Liao TechNet Community Support

Hello, I have a strange situation here. I am going to try to make it as concise and meaningful as I can. Please let me know if more information is required. I have a Windows Server 2008R2 64-bit with Active Directory and Exchange 2010 installed. The AD domain is set as .local. The real domain (.com) email is hosted by our ISP (for security and availability reasons). Windows7 workstations are part of .local domain. They are all configured with Exchange account as well as POP3 client for their .com email from ISP. Mobile devices (Blackberry, iPhones etc.) are set to pick emails from the ISP for the .com email. Exchange server is set to send/receive .com emails. Users have .com as their default email addresses in AD. The issue occurs when users send message to the internal staff; the message does not go to the ISP server WHEN their Outlook is left open on their workstations. Therefore, they do not receive messages on their mobile devices. When Outlook is closed, the messages do get delivered to ISP server as well as they show up in Outlook when opened later on. If anyone can suggest a resolution to this issue, itll be greatly appreciated. Best regards, ParmParmjit Singh BR Systems

Deliver all your mail to Exchange and have users run Outlook with just Exchange in their profiles.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I've never tried it, but adding/replacing your internal send connector to route all mail to the isp SMTP should do the trick. (be sure to test!) ...i wonder what happened to the POP3 connector for exchange in SBS2003? --that would allow you to just have one mailbox in outlook.

Or, better, route SMTP directly to the Exchange server and eliminate the great big POP3 connector kludge.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Lets get real crazy -- office365. If you have budget for exchange and office maybe it's worth looking into at the next upgrade cycle. ...but then again, if an unreliable connection at the office is the cause for the kludge, maybe not.

Deliver all your mail to Exchange and have users run Outlook with just Exchange in their profiles. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." Thank you for your response, Ed. I Think that I've managed to resolve the issue by setting POP3 account as the default account. Best regards, Parm :)Parmjit Singh BR Systems

Deliver all your mail to Exchange and have users run Outlook with just Exchange in their profiles. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." Thank you for your response, Ed. I Think that I've managed to resolve the issue by setting POP3 account as the default account. Best regards, Parm :)Parmjit Singh BR Systems

I've never tried it, but adding/replacing your internal send connector to route all mail to the isp SMTP should do the trick. (be sure to test!) ...i wonder what happened to the POP3 connector for exchange in SBS2003? --that would allow you to just have one mailbox in outlook. Thanks for the suggestion, James. I have that all set up as per your suggestion. I Think that I've managed to resolve the issue by setting POP3 account as the default account. Best regards,Parmjit Singh BR Systems

Hi Parmjit, I am suspecting the message removed to your Outlook client due to POP3 downloading feature. However, the decription is confusion: There are two accounts in users' Outlooks, one is Exchange account for Exchange mailbox resided in your ISP, the other is POP3 account for the SAME Exchange mailbox resided in your ISP, right? What does it mean by "the message does not go to the ISP server WHEN ..."? The message stucked in Outbox of Exchange account? or it was "Moved" to Inbox of your Pop3 account? Who did not receive messages on their mobile devices, the internal recipients or the message sender? Can you get message tracking log from your Exchange server, or disable POP service for a temp test? Thanks. Fiona Liao TechNet Community Support Hello Fiona, Thanks a lot for your response. I'd love to clear the confusion; however, I won't go into it as I've managed to resolve the issue. Best regards, Parm :)Parmjit Singh BR Systems

Good to know the issue is resolved. Have a nice day :)Fiona Liao TechNet Community Support

I wouldn't hold out a lot of hope for that. Outlook doesn't serve two masters well.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."