Exchange 2013 CAS Vs Exchange 2010 CAS
*** If I am not wrong In Exchange 2010 , any email you send or receive Internally goes through CAS server, before it reaches the destination mailbox. Also when receiving email from external users it should go through CAS before you receive it in you mailbox. Sending out email does not have to go through your internal CAS.
Well, am I correct on my above statement? correct me if I am wrong.
****Now for Exchange 2013. If an internal user sends an email to an internal user , does the email have to go through CAS(Front End Server) then to the mailbox server of another internal user ?
***I believe if external user sends email to an internal user, it should come through CAS(Front End server), before it reaches internal user mailbox.
***the same as for OWA, if internal user wants to check their email using OWA , I believe the process of checking, should go through CAS(front end server) to determine where the user mailbox is, then redirect the user to their mailbox.
Any Exchange expert to clarify the confusion ?
Thanks
Well, am I correct on my above statement? correct me if I am wrong.
****Now for Exchange 2013. If an internal user sends an email to an internal user , does the email have to go through CAS(Front End Server) then to the mailbox server of another internal user ?
***I believe if external user sends email to an internal user, it should come through CAS(Front End server), before it reaches internal user mailbox.
***the same as for OWA, if internal user wants to check their email using OWA , I believe the process of checking, should go through CAS(front end server) to determine where the user mailbox is, then redirect the user to their mailbox.
Any Exchange expert to clarify the confusion ?
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Exchange 2010 and 2013 use cas to send emails
But in 2013 and only for mailboxes which exist internally it just go across mailbox transport service not cas
But in 2013 and only for mailboxes which exist internally it just go across mailbox transport service not cas
ASKER
OK:
<<in 2013 and only for mailboxes which exist internally it just go across mailbox transport service not cas>>
So for external emails(going out and coming in) will have to go through CAS Front end ?
what about just login through OWA, does CAS front end server authenticate users and redirect them to their mailbox ?
<<in 2013 and only for mailboxes which exist internally it just go across mailbox transport service not cas>>
So for external emails(going out and coming in) will have to go through CAS Front end ?
what about just login through OWA, does CAS front end server authenticate users and redirect them to their mailbox ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In exchange 2010 , emails sent and received go through CAS server I believe .
CAS is used for availability and connectivity to mailboxes via different protocols. The Transport Role is what actually routes the mail where it needs to do, not CAS.
Will.
ASKER
Will Szymkowski
IN Exchange 2010 even when email is sent internally from one mailbox to another mailbox while both mailboxes are in the same server and in the same database they still have to go through CAS server, which is the one that locate the destination mailbox.
In Exchange 2013. Mailbox server has both Transport Services as well as Mailbox Transport service, if I am not mistaken it also has Client Access Protocol (I could be wrong on this). So there should be a service or protocol that determines where the destination mailbox resides before the Transport Service or the MB Transport service routes the email to the destination mailbox.
IN Exchange 2010 even when email is sent internally from one mailbox to another mailbox while both mailboxes are in the same server and in the same database they still have to go through CAS server, which is the one that locate the destination mailbox.
In Exchange 2013. Mailbox server has both Transport Services as well as Mailbox Transport service, if I am not mistaken it also has Client Access Protocol (I could be wrong on this). So there should be a service or protocol that determines where the destination mailbox resides before the Transport Service or the MB Transport service routes the email to the destination mailbox.
Why are you continually referencing the CAS SERVER!
there are 4 internal roles.
CAS - client access
Hub Transport - routing and policies
Mailbox - mailbox databases
UM - unified messaging
Exchange 2010
When an email is sent it does NOT go through CAS. Mailbox Role sends the email to the submission queue the Hub Transport Role categorizes the email and sends it to the appropriate connector the email if internal it is then send to the appropriate mailbox for delivery. If it is external then it will use either External DNS or a smart host to route the email on the internet.
I think what you might be referring to is "CAS persistent connection" to the mailbox. This does not mean the email goes through CAS. It means that the client needs to have a connection at "all times" to the mailbox database where the mailbox resides.
In Exchange 2013
The hub transport role is on the mailbox server routes all of the mail internally. If an email is sent out to an external source then the mailbox routes the email but it does still "pass through" the Front End Transport on the CAS server.
This is the same idea if a piece of email is coming from an External source it goes through Front End Transport first but "DOES NOT" route the message. It sends it to the exchange server that holds the mailbox role. The mailbox role has Back End Transport service which then categorizes the email and route it to the appropriate mailbox.
Will.
there are 4 internal roles.
CAS - client access
Hub Transport - routing and policies
Mailbox - mailbox databases
UM - unified messaging
Exchange 2010
When an email is sent it does NOT go through CAS. Mailbox Role sends the email to the submission queue the Hub Transport Role categorizes the email and sends it to the appropriate connector the email if internal it is then send to the appropriate mailbox for delivery. If it is external then it will use either External DNS or a smart host to route the email on the internet.
I think what you might be referring to is "CAS persistent connection" to the mailbox. This does not mean the email goes through CAS. It means that the client needs to have a connection at "all times" to the mailbox database where the mailbox resides.
In Exchange 2013
The hub transport role is on the mailbox server routes all of the mail internally. If an email is sent out to an external source then the mailbox routes the email but it does still "pass through" the Front End Transport on the CAS server.
This is the same idea if a piece of email is coming from an External source it goes through Front End Transport first but "DOES NOT" route the message. It sends it to the exchange server that holds the mailbox role. The mailbox role has Back End Transport service which then categorizes the email and route it to the appropriate mailbox.
Will.
For external emails
Mailbox server send it directly to internet without send it to cas first
If you want to send it to cas server you should edit send connector and check box proxy to cas server
Mailbox server send it directly to internet without send it to cas first
If you want to send it to cas server you should edit send connector and check box proxy to cas server
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you Guys!
ASKER