4 out of 5 rated this helpful - Rate this topic

New-InboundConnector

Exchange Online

Applies to: Exchange Online

Topic Last Modified: 2013-04-12

This cmdlet is available only in the cloud-based service.

Use the New-InboundConnector cmdlet to create a new Inbound connector in your cloud-based organization.

For information about the parameter sets in the Syntax section below, see Syntax.

New-InboundConnector -Name <String> -SenderDomains <MultiValuedProperty> [-AssociatedAcceptedDomains <MultiValuedProperty>] [-CloudServicesMailEnabled <$true | $false>] [-Comment <String>] [-Confirm [<SwitchParameter>]] [-ConnectorSource <Default | Migrated | HybridWizard>] [-ConnectorType <OnPremises | Partner>] [-DomainController <Fqdn>] [-Enabled <$true | $false>] [-Organization <OrganizationIdParameter>] [-RequireTls <$true | $false>] [-RestrictDomainsToCertificate <$true | $false>] [-RestrictDomainsToIPAddresses <$true | $false>] [-SafeListIPAddresses <$true | $false>] [-SenderIPAddresses <MultiValuedProperty>] [-TlsSenderCertificateName <TlsCertificate>] [-WhatIf [<SwitchParameter>]]

Examples

Example 1

This example creates the Inbound connector named Contoso Inbound Connector with the following properties:

It listens for incoming connections from the domain contoso.com and all subdomains.
It only accepts mail from contoso.com, and from the IP range 192.168.0.1/25. It rejects mail from contoso.com if it originates from any other IP address.

New-InboundConnector -Name "Contoso Inbound Connector" -SenderDomains *.contoso.com -SenderIPAddresses 192.168.0.1/25 -RestrictDomainstoIPAddresses $true

Example 2

This example creates the Inbound connector named Contoso Inbound Secure Connector and requires TLS transmission for all messages.

New-InboundConnector -Name "Contoso Inbound Secure Connector" -SenderDomains *.contoso.com -SenderIPAddresses 192.168.0.1/25 -RestrictDomainstoIPAddresses $true -RequireTLS $true -TlsSenderCertificateName *.contoso.com

Detailed Description

Inbound connectors accept email messages from remote domains that require specific configuration options.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Inbound and Outbound connectors" entry in the Feature Permissions in Exchange Online topic.

Parameters

Parameter	Required	Type	Description
Name	Required	System.String	The Name parameter specifies a descriptive name for the connector.
SenderDomains	Required	Microsoft.Exchange.Data.MultiValuedProperty	The SenderDomains parameter specifies the remote domains from which this connector accepts messages, thereby limiting its scope. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: `.contoso.com`. However, you can't embed a wildcard character, as shown in the following example: `domain..contoso.com`. You can specify multiple domains separated by commas.
AssociatedAcceptedDomains	Optional	Microsoft.Exchange.Data.MultiValuedProperty	The AssociatedAcceptedDomains parameter specifies the accepted domains that the connector applies to, thereby limiting its scope. For example, you can apply the connector to a specific accepted domain in your organization, such as contoso.com.
CloudServicesMailEnabled	Optional	System.Boolean	Set to `$true` to enable this connector to receive messages from the cloud service.
Comment	Optional	System.String	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"`.
Confirm	Optional	System.Management.Automation.SwitchParameter	The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.
ConnectorSource	Optional	Microsoft.Exchange.Data.TenantConnectorSource	The ConnectorSource parameter specifies how the connector is created. Valid input for this parameter includes the following values: `Default` The connector is manually created. `HybridWizard` The connector is automatically created by the Hybrid Configuration Wizard. `Migrated` The connector was originally created in Microsoft Forefront Online Protection for Exchange. The default value for connectors you create yourself is `Default`. It isn’t recommended that you change this value.
ConnectorType	Optional	Microsoft.Exchange.Data.TenantConnectorType	The ConnectorType parameter specifies a category for the domains that are serviced by the connector. Valid input for this parameter includes the following values: `Partner` The connector services domains that are external to your organization. `OnPremises` The connector services domains that are used by your on-premises organization. Use this value for accepted domains in your cloud-based organization that are also specified by the SenderDomains parameter.
DomainController	Optional	Microsoft.Exchange.Data.Fqdn	This parameter is reserved for internal Microsoft use.
Enabled	Optional	System.Boolean	The Enabled parameter enables or disables the connector. Valid input for this parameter is `$true` or `$false`. The default value is `$true`.
Organization	Optional	Microsoft.Exchange.Configuration.Tasks.OrganizationIdParameter	The Organization parameter is reserved for internal Microsoft use.
RequireTls	Optional	System.Boolean	The RequireTLS parameter specifies that all messages received by this connector require TLS transmission. Valid values for this parameter are `$true` or `$false`. The default value is `$false`.
RestrictDomainsToCertificate	Optional	System.Boolean	The RestrictDomainsToCertificate parameter, when set to `$true`, causes the connector to reject mail that originates from a namespace not specified by the SenderDomains parameter.
RestrictDomainsToIPAddresses	Optional	System.Boolean	The RestrictDomainsToIPAddresses parameter, when set to `$true`, automatically rejects mail from the domains specified by the SenderDomains parameter if the mail originates from an IP address that isn't specified by the SenderIPAddresses parameter. Valid input for this parameter is `$true` or `$false`. The default value is `$false`.
SafeListIPAddresses	Optional	System.Boolean	The SafeListIPAddresses parameter includes or exempts the IP addresses specified by the SenderIPAddresses parameter from anti-spam filtering. Valid input for this parameter is `$true` or `$false`. The default value is `$false`. This means that by default, the IP addresses specified by the SenderIPAddresses parameter are subject to anti-spam filtering.
SenderIPAddresses	Optional	Microsoft.Exchange.Data.MultiValuedProperty	The SenderIPAddresses parameter specifies the remote IP addresses from which this connector accepts messages. You enter the IP addresses using the following syntax: Single IP For example, `192.168.1.1`. CIDR IP You can use Classless InterDomain Routing (CIDR), for example, `192.168.0.1/25`. You can specify multiple IP address separated by commas.
TlsSenderCertificateName	Optional	Microsoft.Exchange.Data.TlsCertificate	The TlsSenderCertificateName parameter specifies the certificate used by the sender’s domain when the RequireTls parameter is set to `$true`. Valid input for the TlsSenderCertificateName parameter is an SMTP domain. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: `.contoso.com`. You can't embed a wildcard character, as shown in the following example: `domain..contoso.com`.
WhatIf	Optional	System.Management.Automation.SwitchParameter	The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

Input Types

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

Return Types

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)