Connection Information

This page documents general connection information for E-mail Server.

Connecting to a Proxy Server

Starting in release 8.5.1, E-mail Server can connect to a SOCKS or HTTP proxy server. To do this, you must create a section called [proxy] in the E-mail Server Application object, containing the following options:

useProxy
Default value: false
Valid values: true, false

Any value other than true means that no proxy will be used.

port
Default value: No default value
Valid values: Positive integer value smaller than 65535.

If the port number is absent or invalid, an IllegalArgumentException is thrown explaining the error.

host
Default value: No default value
Valid values: Alphanumeric string

Name or IP address of the proxy's host. Examples: 192.168.15.28, myProxyHost. If a bad value is provided or E-mail Server is for some reason not able to connect to the specified host on the specified port, a MailConnectException is thrown. If no host is provided, an IllegalArgumentException is thrown.

user
Default value: No default value
Valid values: Alphanumeric string

Optional user name to authenticate on the proxy. If this option is present, password must also be present.

password
Default value: No default value
Valid values: Alphanumeric string

Optional password to authenticate on the proxy. If this option is present, user must also be present.

socksVersion
Default value: 5
Valid values: Alphanumeric string

For SOCKS proxy only: version of the SOCKS proxy being used. Only version 5 is supported. This option is not needed for an HTTP proxy.

Connecting to Exchange Server with EWS

Starting in release 8.1.4, E-mail Server can connect to an Exchange Server running Exchange Web Services (EWS). By connecting to the corporate server using an HTTP connection, you gain flexibility in getting through the firewall, as HTTP ports are often already opened.

To do this, use the following options settings:

pop-client Section

Option Name	Setting
type	ews (new possible value in 8.1.4)
folder-path (new in 8.1.4)	(empty) The key must be present.
port	The port used for EWS. Common values are 80 for unsecured connections and 443 for secured connections
server	EWS url (see "Finding the EWS URI" below).
mailbox	User's adress, for example, JeffP@contoso.com

smtp Section

Option Name	Setting
server-type (new in 8.1.4)	ews
server	EWS url (see "Finding the EWS URI" below). For example, https://owa.example.com/ews/exchange.asmx

Important

The pop-connection-security and smtp-connection-security options have no effect when used with EWS. Secured or non-secured connection are used depending on the server's configuration. The connection is automatically done and negotiated using Apache's HTTP client, which handles TLS negotiation if needed.

Finding the EWS URI

Most of the time the EWS is published together with the OWA: If the OWA-URL is for example https://owa.example.com/owa, EWS is available at https://owa.example.com/ews/exchange.asmx. The EWS-URL can be tested in any browser (except Internet Explorer). The request should be forwarded to https://example.com/ews/Services.wsdl and a WSDL should be sent to the browser.

Specifying the From Header

When using the Forward object in a routing strategy, or any method that can specify a user to go in the From header, the corporate e-mail server might refuse to send the e-mail. To avoid this, you can configure the corporate server to allow sending e-mails on behalf of another user.

Here is an example for Microsoft Exchange using PowerShell:

Add -ADPermission "Bruce Wayne" -User "gotham\selinaK" -Extendedrights "Send As"

This allows selinaK to send e-mails on behalf of the user "Bruce Wayne."