How can you stop POP3 from proxying to a specific CAS server?
-
30 aprilie 2012 13:52
Hi,
If have ex2k7/2k10 in coexistence where our ex2k7 mailboxes proxy through our ex2k10 CAS servers for POP/IMAP. We have a couple ex2k7 servers configured for CAS, but have POP/IMAP disabled. We're seeing in our ex2k10 CAS logs that there are clients trying to connect to ex2k7 CAS servers that have the POP/IMAP disabled. As a result, the connection gets refused and the client gets an error. How can you configure a CAS server not to proxy to a ex2k7 POP/IMAP server that has the POP/IMAP service disabled?
Patrick de Rover
Toate mesajele
-
30 aprilie 2012 17:14
Understanding Proxying and Redirection
See the section on POP and IMAP proxying
If you have mailboxes on 2007, you will need to enable the POP3 and IMAP4 service on the 2007 CAS.
-
30 aprilie 2012 17:29
There are a number of 2007 CAS servers that have POP/IMAP running, but not all of them.
According to technet: Client Access servers trying to proxy to another Active Directory site don't check whether the POP3 or IMAP4 service is actually running on the remote Client Access server. It's important, therefore, to not only ensure that the services are running on every Client Access server in the remote Active Directory site, but to consider using a load balancer for the service.
What I'll have to do is enable pop/imap on all cas servers to prevent clients from getting intermittent error messages.
Patrick de Rover
- Marcat ca răspuns de patrick derover 30 aprilie 2012 17:29
-
30 aprilie 2012 17:42
There are a number of 2007 CAS servers that have POP/IMAP running, but not all of them.
According to technet: Client Access servers trying to proxy to another Active Directory site don't check whether the POP3 or IMAP4 service is actually running on the remote Client Access server. It's important, therefore, to not only ensure that the services are running on every Client Access server in the remote Active Directory site, but to consider using a load balancer for the service.
What I'll have to do is enable pop/imap on all cas servers to prevent clients from getting intermittent error messages.
Patrick de Rover
Yep, pretty much what I said! -
30 aprilie 2012 22:12On Mon, 30 Apr 2012 17:42:22 +0000, A_D_ wrote:>>>There are a number of 2007 CAS servers that have POP/IMAP running, but not all of them.>>According to technet: Client Access servers trying to proxy to another Active Directory site don't check whether the POP3 or IMAP4 service is actually running on the remote Client Access server. It's important, therefore, to not only ensure that the services are running on every Client Access server in the remote Active Directory site, but to consider using a load balancer for the service.>>What I'll have to do is enable pop/imap on all cas servers to prevent clients from getting intermittent error messages.>>>Patrick de Rover Yep, pretty much what I said!Oh, but you said it so much better! ;-)---Rich MatheisenMCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP -
1 mai 2012 03:04What I was really trying to get at was, I have about a dozen CAS servers that handle pop/imap/owa etc. I also have a dedicated web-based OAB server that handles 1000+ OABs. When 2k7 mailboxes proxy through the 2k10 CAS servers, they also hit the OAB server which has POP/IMAP disabled. I was looking for a solution that would prevent 2k10 from using the Web OAB server as potential POP/IMAP endpoint. Unfortunately, Exchange isn't smart enough to figure out that the pop/imap service has been disabled and also cause the end-user to receive an error message. Nor is it smart enough to silently redirect the proxy to another CAS server with pop/imap without returning an error. I was also trying to avoid having to enable pop/imap service on the web oab server.
Patrick de Rover
-
1 mai 2012 22:09On Tue, 1 May 2012 03:04:27 +0000, patrick derover wrote:>What I was really trying to get at was, I have about a dozen CAS servers that handle pop/imap/owa etc. I also have a dedicated web-based OAB server that handles 1000+ OABs. When 2k7 mailboxes proxy through the 2k10 CAS servers, they also hit the OAB server which has POP/IMAP disabled. I was looking for a solution that would prevent 2k10 from using the Web OAB server as potential POP/IMAP endpoint. Unfortunately, Exchange isn't smart enough to figure out that the pop/imap service has been disabled and also cause the end-user to receive an error message. Nor is it smart enough to silently redirect the proxy to another CAS server with pop/imap without returning an error. I was also trying to avoid having to enable pop/imap service on the web oab server.Is everything in one AD site? Maybe you can create a site for the CASthat serves the OABs? If cross-site proxying for IMAP/POP isn'tenabled that should stop it.---Rich MatheisenMCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP
.png)
