Before you are able to use our management console, you must first enable it through the configuration file. After this, you can set it up to use a secure connection.
The management console can be enabled in MailerQ's configuration file. The following variables should be used:
www-port: 8485 (default: 8485) www-ip: 18.104.22.168 (default: 0.0.0.0) www-password: admin (empty by default) www-dir: /usr/share/mailerq/www (default: /usr/share/mailerq/www) www-connections: 10
www-port variable holds the port number for the management console;
8485 is the default. If you use port 80, you do
not have to include the port number in the URL and you can access the
management console with using a browser via address
If you assign a different port number (like 8080), you have to include
the port number in the URL:
In its default setting of
0.0.0.0, the management console is accessible via
all IP addresses that are assigned to the server on which MailerQ runs. If you
only want to make it accessible via one specific IP, you can set the
variable. Of course, the IP address that you assign must be bound to the server.
The management console is protected with a password to prevent anyone from
accessing it. This password can be set with the
variable. Besides setting a password, we also recommend to put the
management console behind a firewall so that you will not have to worry
about people breaking into it.
console are automatically installed into the
directory. If you want to run the console from out of a different
location, you can change this directory with the
To limit the number of resources that can be used by the built-in HTTP server, you can use the "www-connections" variable to limit the number of simultaneous HTTP connections that can be handled. This number includes active web sockets.
If is a good idea to secure your management console, as it will also used to manage private DKIM keys; by definition, these should not be transferered over interceptable non-secure HTTP connections.
The following configuration file variables are relevant for enabling HTTPS support:
www-port: 0 www-secure-port: 443 (empty by default) www-certificate: /path/to/certificate.crt (empty by default) www-privatekey: /path/to/privatekey.key (empty by default) www-ciphers: !aNULL:!eNULL:!LOW:!SSLv2:!EXPORT:!EXPORT56:FIPS:MEDIUM:HIGH:@STRENGTH (empty by default)
If you enable HTTPS, switch off the regular HTTP
interface by setting the
www-port to zero. This prevents that users
will connect to the old unsecure interface by accident. The
holds the port number for the HTTPS connections (443 is the default for
this, so that you won't have to include the port number in URLS). The
certifate and key files, and the supported ciphers can be set using
Once enabled, the encrypted management console can be accessed using
https://hostname.of.your.server if you use default port 443,
https://hostname.of.your.server:port for any other port.
In this blog post, we will dive deeper into the world of bounces, one of the most important - and maybe most frustrating - terms in un...
One of our favourite tools in MailerQ is tags. With tags, you can do a lot on an individual delivery level - or on any level ...