You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -153,7 +177,7 @@ Although you can configure non-SMTP address spaces on a Send connector in the Tr
153
177
154
178
```yaml
155
179
Type: MultiValuedProperty
156
-
Parameter Sets: Set1, (All)
180
+
Parameter Sets: AddressSpaces
157
181
Aliases:
158
182
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
159
183
Required: True
@@ -180,6 +204,29 @@ Accept pipeline input: False
180
204
Accept wildcard characters: False
181
205
```
182
206
207
+
### -CloudServicesMailEnabled
208
+
Note: We recommend that you don't use this parameter unless you are directed to do so by Microsoft Customer Service and Support, or by specific product documentation. Instead, use the Hybrid Configuration wizard to configure mail flow between your on-premises and cloud organizations. For more information, see Hybrid Configuration wizard (https://technet.microsoft.com/library/hh529921.aspx).
209
+
210
+
The CloudServicesMailEnabled parameter specifies whether the connector is used for hybrid mail flow between an on-premises Exchange environment and Microsoft Office 365. Specifically, this parameter controls how certain internal X-MS-Exchange-Organization-\* message headers are handled in messages that are sent between accepted domains in the on-premises and cloud organizations. These headers are collectively known as cross-premises headers.
211
+
212
+
Valid values are:
213
+
214
+
- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
215
+
216
+
- $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector.
217
+
218
+
```yaml
219
+
Type: $true | $false
220
+
Parameter Sets: AddressSpaces
221
+
Aliases:
222
+
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
223
+
Required: False
224
+
Position: Named
225
+
Default value: None
226
+
Accept pipeline input: False
227
+
Accept wildcard characters: False
228
+
```
229
+
183
230
### -Comment
184
231
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
185
232
@@ -233,6 +280,25 @@ Accept pipeline input: False
233
280
Accept wildcard characters: False
234
281
```
235
282
283
+
### -ConnectorType
284
+
The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Office 365. Valid values are:
285
+
286
+
- Default: The connector isn't used to send messages to Office 365. This is the default value.
287
+
288
+
- XPremises: The connector is used to send messages to Office 365.
289
+
290
+
```yaml
291
+
Type: Default | XPremises
292
+
Parameter Sets: AddressSpaces
293
+
Aliases:
294
+
Applicable: Exchange Server 2016, Exchange Server 2019
295
+
Required: False
296
+
Position: Named
297
+
Default value: None
298
+
Accept pipeline input: False
299
+
Accept wildcard characters: False
300
+
```
301
+
236
302
### -Custom
237
303
The Custom parameter specifies the Custom usage type. The usage type specifies the permissions and authentication methods assigned to the Send connector. If you use the Custom parameter, you can't use any of the following parameters:
238
304
@@ -416,6 +482,21 @@ Accept pipeline input: False
416
482
Accept wildcard characters: False
417
483
```
418
484
485
+
### -FrontendProxyEnabled
486
+
The FrontendProxyEnabled parameter routes outbound messages through the CAS server, where destination specific routing, such as DNS or IP address, is set, when the parameter is set to $true.
487
+
488
+
```yaml
489
+
Type: $true | $false
490
+
Parameter Sets: AddressSpaces
491
+
Aliases:
492
+
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
493
+
Required: False
494
+
Position: Named
495
+
Default value: None
496
+
Accept pipeline input: False
497
+
Accept wildcard characters: False
498
+
```
499
+
419
500
### -IgnoreSTARTTLS
420
501
The IgnoreSTARTTLS parameter specifies whether to ignore the StartTLS option offered by a remote sending server. This parameter is used with remote domains. This parameter must be set to $false if the RequireTLS parameter is set to $true. Valid values for this parameter are $true or $false.
421
502
@@ -488,7 +569,7 @@ The IsCoexistenceConnector parameter specifies whether this Send connector is us
488
569
489
570
```yaml
490
571
Type: $true | $false
491
-
Parameter Sets: Set1, Set2
572
+
Parameter Sets: (All)
492
573
Aliases:
493
574
Applicable: Exchange Server 2010
494
575
Required: False
@@ -503,7 +584,7 @@ The IsScopedConnector parameter specifies the availability of the connector to o
503
584
504
585
```yaml
505
586
Type: $true | $false
506
-
Parameter Sets: Set1, (All)
587
+
Parameter Sets: AddressSpaces
507
588
Aliases:
508
589
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
509
590
Required: False
@@ -538,7 +619,7 @@ When you use the LinkedReceiveConnector parameter, you can't use the AddressSpac
538
619
539
620
```yaml
540
621
Type: ReceiveConnectorIdParameter
541
-
Parameter Sets: Set2
622
+
Parameter Sets: LinkedReceiveConnector
542
623
Aliases:
543
624
Applicable: Exchange Server 2010
544
625
Required: False
@@ -766,6 +847,21 @@ Accept pipeline input: False
766
847
Accept wildcard characters: False
767
848
```
768
849
850
+
### -TlsCertificateName
851
+
The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is "\<I\>X.500Issuer\<S\>X.500Subject". The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command $TLSCert = Get-ExchangeCertificate -Thumbprint \<Thumbprint\>, run the command $TLSCertName = "\<I\>$($TLSCert.Issuer)\<S\>$($TLSCert.Subject)", and then use the value $TLSCertName for this parameter.
852
+
853
+
```yaml
854
+
Type: SmtpX509Identifier
855
+
Parameter Sets: AddressSpaces
856
+
Aliases:
857
+
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
858
+
Required: False
859
+
Position: Named
860
+
Default value: None
861
+
Accept pipeline input: False
862
+
Accept wildcard characters: False
863
+
```
864
+
769
865
### -TlsDomain
770
866
The TlsDomain parameter specifies the domain name that the Send connector uses to verify the FQDN of the target certificate when establishing a TLS secured connection.
771
867
@@ -846,93 +942,6 @@ Accept pipeline input: False
846
942
Accept wildcard characters: False
847
943
```
848
944
849
-
### -CloudServicesMailEnabled
850
-
Note: We recommend that you don't use this parameter unless you are directed to do so by Microsoft Customer Service and Support, or by specific product documentation. Instead, use the Hybrid Configuration wizard to configure mail flow between your on-premises and cloud organizations. For more information, see Hybrid Configuration wizard (https://technet.microsoft.com/library/hh529921.aspx).
851
-
852
-
The CloudServicesMailEnabled parameter specifies whether the connector is used for hybrid mail flow between an on-premises Exchange environment and Microsoft Office 365. Specifically, this parameter controls how certain internal X-MS-Exchange-Organization-\* message headers are handled in messages that are sent between accepted domains in the on-premises and cloud organizations. These headers are collectively known as cross-premises headers.
853
-
854
-
Valid values are:
855
-
856
-
- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
857
-
858
-
- $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector.
859
-
860
-
```yaml
861
-
Type: $true | $false
862
-
Parameter Sets: (All)
863
-
Aliases:
864
-
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
865
-
Required: False
866
-
Position: Named
867
-
Default value: None
868
-
Accept pipeline input: False
869
-
Accept wildcard characters: False
870
-
```
871
-
872
-
### -FrontendProxyEnabled
873
-
The FrontendProxyEnabled parameter routes outbound messages through the CAS server, where destination specific routing, such as DNS or IP address, is set, when the parameter is set to $true.
874
-
875
-
```yaml
876
-
Type: $true | $false
877
-
Parameter Sets: (All)
878
-
Aliases:
879
-
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
880
-
Required: False
881
-
Position: Named
882
-
Default value: None
883
-
Accept pipeline input: False
884
-
Accept wildcard characters: False
885
-
```
886
-
887
-
### -TlsCertificateName
888
-
The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is "\<I\>X.500Issuer\<S\>X.500Subject". The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command $TLSCert = Get-ExchangeCertificate -Thumbprint \<Thumbprint\>, run the command $TLSCertName = "\<I\>$($TLSCert.Issuer)\<S\>$($TLSCert.Subject)", and then use the value $TLSCertName for this parameter.
889
-
890
-
```yaml
891
-
Type: SmtpX509Identifier
892
-
Parameter Sets: (All)
893
-
Aliases:
894
-
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
895
-
Required: False
896
-
Position: Named
897
-
Default value: None
898
-
Accept pipeline input: False
899
-
Accept wildcard characters: False
900
-
```
901
-
902
-
### -ConnectorType
903
-
The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Office 365. Valid values are:
904
-
905
-
- Default: The connector isn't used to send messages to Office 365. This is the default value.
906
-
907
-
- XPremises: The connector is used to send messages to Office 365.
908
-
909
-
```yaml
910
-
Type: Default | XPremises
911
-
Parameter Sets: (All)
912
-
Aliases:
913
-
Applicable: Exchange Server 2016, Exchange Server 2019
914
-
Required: False
915
-
Position: Named
916
-
Default value: None
917
-
Accept pipeline input: False
918
-
Accept wildcard characters: False
919
-
```
920
-
921
-
### -Region
922
-
This parameter is reserved for internal Microsoft use.
923
-
924
-
```yaml
925
-
Type: NotSpecified | NAM | EUR | APC
926
-
Parameter Sets: (All)
927
-
Aliases:
928
-
Applicable: Exchange Server 2016, Exchange Server 2019
929
-
Required: False
930
-
Position: Named
931
-
Default value: None
932
-
Accept pipeline input: False
933
-
Accept wildcard characters: False
934
-
```
935
-
936
945
### CommonParameters
937
946
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
0 commit comments