Sender settings (OpmConfig | senderConfig)
XML Tag |
Description |
Comments |
---|---|---|
<isSenderEnabled> |
Enable the sender.
Values :true: Turn on sender (default) false: Turn off sender. |
Sender and receiver cannot be turned off at the same time. |
<bufferSizePerConn> |
The buffer size in bytes per connection.
Default : 5000Range : 1,000 – 100,000 |
— |
<failOverMode> |
Specifies whether the relay server is set failover or parallel mode.
Values :true: Failover mode; use the high order relay until it is down then fail-over to the next relay false: Parallel mode; use all the enabled relays in parallel. |
For more information about how to configure relay servers for failover or parallel mode, see Configure failover mode or parallel mode. |
<failOverTimeOut> |
The number of failure tries on establishing connection to relay before claiming it down.
Default : 1 |
Change only when directed by BlackBerry AtHoc customer support or implementation. |
<sendingRetries> |
The number of times OPM retries send an email, if non-system errors occur.
Default : 2 |
Change only when directed by BlackBerry AtHoc customer support or omplementation. |
<sendTimeOut> |
SMTP send session timeout (in seconds)
Default : 60 |
New in OPM 2.2. |
<startTlsmode> |
Specifies the TLS behavior on the OPM Sender level.Values :none : Indicates as the default value and does not use TLS.optional : Try StartTls and handshaking, if TLS is not supported or fails, log a warning but fall back to none TLS mode (plain SMTP) and continue sending.must : Try StartTls and handshaking, if TLS is not supported or fails, display a new "TlsFailure" error, shut down the relay server and stop the operations (similar to AuthFailure error). |
STARTTLS is a standard (RFC 3207) way to upgrade SMTP connections to SSL/TLS optionally. It is widely used by many email servers today, including our cloud email delivery provider Dyn. Starting from this version, OPM supports STARTTLS as SMTP client (sender), on either port 25 or 587.TLS 1.2 version is enforced in the app server system level, not application level. |