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
The SenderDomains parameter specifies the source domains that the connector accepts messages for. A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, \*.contoso.com), but you can't embed the wildcard character (for example, domain.\*.contoso.com is not valid).
95
+
The SenderDomains parameter specifies the source domains from which a Partner type connector accepts messages, thereby limiting its scope. A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all its subdomains (for example, `*.contoso.com`). However, you can't embed the wildcard character (for example, `domain.*.contoso.com` is not valid).
96
96
97
97
You can specify multiple domains separated by commas.
The ConnectorType parameter specifies the category for the source domains that the connector accepts messages for. Valid values are:
228
228
229
229
- Partner: External partners or services.
230
-
- OnPremises: Your on-premises email organization. Use this value for accepted domains in your cloud-based organization that are also specified by the SenderDomains parameter.
230
+
- OnPremises: The connector services domains that are used by your on-premises organization. OnPremises connectors are used to grant special rights to an email that matches the connector and additional requirements, such as allowing relaying through the tenant to internet destinations, promoting emails from on-premises or other environments as internal (in a hybrid configuration), or enabling other more complex mail flows.
The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the connector. Valid values are:
377
+
The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the connector.
378
+
379
+
**Note**: This parameter is only applicable to a Partner connector type.
376
380
377
381
- $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value.
378
382
- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value.
The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses. Valid values are:
398
+
The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses.
399
+
400
+
**Note**: This parameter is only applicable to a Partner connector type.
395
401
396
402
- $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter.
397
403
- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value.
The SenderIPAddresses parameter specifies the source IPV4 IP addresses that the connector accepts messages from. Valid values are:
435
+
The SenderIPAddresses parameter specifies the remote IPv4 IP addresses from which this connector accepts messages.
436
+
437
+
**Note**: This parameter is only applicable to a Partner connector type and only if [RestrictDomainsToIPAddresses](#-restrictdomainstoipaddresses) is enabled.
430
438
431
439
- Single IP address: For example, 192.168.1.1.
432
440
- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. Valid subnet mask values are /24 through /32.
0 commit comments