Settings


General Settings
Enter the URL this service can be reached from
Enter the email address that will be used as "from" for system messages
Enter Google Analytics tracking code
HTML code shown in the front page header section
Campaign defaults

SMTP Settings

These settings are required to send out e-mail messages

Advanced SMTP settings
The count of maximum simultaneous connections to make against the SMTP server (defaults to 5)
The number of messages to send through a single connection before the connection is closed and reopened (defaults to 100)
Maximum number of messages to send in an hour. Leave empty or zero for no throttling. If your provider uses a different speed limit (messages/minute or messages/second) then convert this limit into messages/hour (1m/s => 3600m/h).
VERP bounce handling

Mailtrain is able to use VERP based routing to detect bounces. In this case the message is sent to the recipient using a custom VERP address as the return path of the message. If the message is not accepted a bounce email is sent to this special VERP address and thus a bounce is detected.

To get VERP working you need to set up a DNS MX record that points to your Mailtrain hostname. You must also ensure that Mailtrain VERP interface is available from port 25 of your server (port 25 usually requires root user privileges). This way if anyone tries to send email to someuser@{{verpHostname}} then the email should end up to this server.

VERP usually only works if you are using your own SMTP server. Regural relay services (SES, SparkPost, Gmail etc.) tend to remove the VERP address from the message.

{{#if verpEnabled}}
VERP bounce handling server hostname. This hostname is used in the SMTP envelope FROM address and the MX DNS records should point to this server
{{else}}

VERP bounce handling server is not enabled. Modify your server configuration file and restart server to enable it

{{/if}}
GPG Signing

Only messages that are encrypted can be signed. Subsribers who have not set up a GPG public key in their profile receive normal email messages. Users with GPG key set receive encrypted messages and if you have signing key also set, the messages are signed with this key.

Do not use sensitive keys here. The private key and passphrase are not encrypted in the database.

Only fill this if your private key is encrypted with a passphrase
This value is optional. if you do not provide a private key GPG encrypted messages are sent without signing.