REF: Exchange 2010 - Intra-organization Send Connector

-

 

組織內傳送連接器  Intra-organization Send Connector

組織內傳送連接器是隱含且隱藏的傳送連接器，是由 Exchange Server 2007 自動計算而來，而且會讓相同組織中的 Hub Transport Server 彼此轉送郵件，而不需要使用明確的傳送連接器。因為 Edge 訂閱的 Active Directory 中內含具有 Active Directory 站台關聯的組態物件，所以也可以使用組織內傳送連接器將郵件轉送至該 Edge Transport Server。

只有位在已訂閱 Edge Transport Server 之相同 Active Directory 站台中的 Hub Transport Server，才可以直接與已訂閱 Edge Transport Server 進行電子郵件的傳送及接收。如果您擁有多站台樹系，而且 Exchange 2007 已部署在多個站台中，則非訂閱站台中的 Hub Transport Server 會將輸出電子郵件路由傳送至已訂閱站台。已訂閱站台中的 Hub Transport Server 會將輸出電子郵件路由傳送至 Edge Transport Server。

下圖顯示來自 Exchange 組織中之非訂閱 Active Directory 站台的輸出郵件流程。具有兩個站台的 Active Directory 樹系就已經建立 Edge 訂閱與站台 A 的關聯。如果郵件是從站台 B 傳送給網際網路收件者，則會先將郵件轉送至站台 A。而站台 A 中的接收 Hub Transport Server 會使用組織內傳送連接器將該郵件轉送至 Edge Transport Server。Edge Transport Server 接著會將郵件路由傳送至自動建立的 EdgeSync - Site-A to Internet 傳送連接器，以傳遞至收件者網域。

image

 

Blog Extended Reading

1. REF: Exchange 2010 - Upgrading from Exchange 2003 Transport (Part1)
2. REF: Exchange 2010 - Upgrading from Exchange 2003 Transport (Part2)

 

More Information & Reference

1. Upgrading from Exchange 2003 Transport
2. EdgeSync and Send Connectors


Radiohead22_thumb53

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c79921331         Last attempt @ 2013-12-19 17:
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Section EnableSerializationDataSigning -Parameters @("Enabled=true&qu
Read more

E14–Bulk Create Mail Contact & Set-Contact

-
Image
  http://community.office365.com/en-us/w/exchange/579.aspx     Get-Contact | Export-Csv c:\temp\contact.csv Get-MailContact | Export-Csv c:\temp\Mailcontact.csv   [PS] Import-Csv .\Contact_Source.csv | % {New-MailContact -Name $_.Name -DisplayName $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Alias $_.Alias -PrimarySmtpAddress $_.PrimarySMTPAddress -OrganizationalUnit "Contacts" -WhatIf }   [PS] >$Contacts = Import-Csv .\Contact_final.csv [PS] >$Contacts | foreach {Set-Contact $_.Name -Company $_.Company -Department $_.Department -Office $_.Office -Phone $_.Phone }
Read more