Hi, My organization is running Exchange 2003 Server. A user of our AD who is travelling abroad wants to access his Exchange account through POP3 protocol because of problems of latency with VPN. In the ESM I've enabled the Default POP3 Virtual Server. In the AD, in the user's account, under Exchange Features, I've enabled POP3. The e-mails sent in our organization's Windows domain are also received by Exchange. The external e-mails are caught by a third party software called POPCon from our provider. My questions are : are there anything else to modify in my windows 2003-Exchange 2003 to make it run? How are caught the internal e-mails when the user is abroad, connecting from WAN? How do I have to set up the Outlook client particularly the incoming mail server? Thanks for your answer.

Why not use OWA instead? POP Connectors are a kludge and sure to break. And the end user will need access to a SMTP server to send messages.

Hi Santille, Can you let us know why you would like to use pop3? If there are no specific reasons, I would suggest you use OWA or RPC over HTTP which are more powerful instead. Best Regards, Tyler

Hi Santille, Can you let us know why you would like to use pop3? If there are no specific reasons, I would suggest you use OWA or RPC over HTTP which are more powerful instead. Best Regards, Tyler

Thank you for your answer, Tyler. Of course there is the OWA but the user in question and he is the boss(!!) wants to use his Outlook client abroad. RPC over HTTP has been already suggested to me but I don't know to set up it at all : do you know a good tutorial to do this by the client's and the server's side? seb

RPC over HTTP is definitely the way to go. It's more secure and has more features. In addition to the Petril.il link check out http://www.msexchange.org/tutorials/Implementing-RPC-over-HTTPS-single-Exchange-Server-2003-environment.html and http://www.msexchange.org/tutorials/outlookrpchttp.html It's incredibly easy - and if I were you I would close down POP and even IMAP in favor of this (as well as Activesync).Lanwench [MVP - Exchange] ** Do not fold, spindle or mutilate. Fill in the box completely and erase any stray marks. Use only a #2 pencil.

Please have a look on this http://www.petri.co.il/how-can-i-configure-rpc-over-https-on-exchange-2003-single-server-scenario.htm Sathya

RPC over HTTP is definitely the way to go. It's more secure and has more features. In addition to the Petril.il link check out http://www.msexchange.org/tutorials/Implementing-RPC-over-HTTPS-single-Exchange-Server-2003-environment.html and http://www.msexchange.org/tutorials/outlookrpchttp.html It's incredibly easy - and if I were you I would close down POP and even IMAP in favor of this (as well as Activesync).Lanwench [MVP - Exchange] ** Do not fold, spindle or mutilate. Fill in the box completely and erase any stray marks. Use only a #2 pencil.

Ok, thanks for your answers : I will try it and let you know.