The Artica messaging system is a versatile system that can be configured to meet many needs.
Here are some examples of mail relay applications:
A single configuration can provide many or all of these services, but a complex interplay of settings may be required.
We consider that multiple instances may be a simpler way to configure a multifunctional MTA system.
With multiple instances, each instance has its own configurations, queues and data, but it shares all program files with the other instances.
The purpose of supporting multiple instances is not to force you to create multiple instances, but rather to give you a choice.
Multiple instances give you the freedom to tailor each instance to a single task that it does well and to combine the instances into complete systems.
Prerequisite: Multiple network addresses
The multiple instance mode of the SMTP relay does not really work like a web server or a reverse-proxy.
Indeed, a Web server can share several domains with a single network address.
In the case of the multiple relay, you will have to create one network address per instance.
It is then necessary to manage several network cards or several virtual addresses.
For this, Artica allows you to create Virtual Interfaces or you can also use IP aliasing
Notice on the current configuration
If you have already configured your Artica with one instance, you will lose its configuration.
In fact, the main configuration will be deactivated in favor of the child instances.
The SMTP core previously configured will only have to manage its children instances.
You will have to create another instance that will take over the parameters of the original SMTP configuration.
However, if you remove the multiple instances mode, you will get back your original configuration.
Send messaging events from your instance into a SIEM/Syslog