Security Settings
This section provides basic recommendations for the initial security configuration of the CommuniGate Pro Server.
Installing Security Certificates
Use certificates issued by a Certificate Authority trusted by client applications. The certificate must cover the DNS names that users and administrators use to connect to the Server. Renew certificates before they expire.
In the WebAdmin Interface, open the Domain Settings page and follow the Security link.
- Set
PKI ServicestoEnabled. - Generate or import a Private Key.
- Install the matching Domain Certificate in PEM format. If the Certificate Authority supplied intermediate certificates, add them to the Certificate Authority Chain (Optional) field and click
Set CA Chain.
In the Server-wide TLS settings on the Settings / General / Others page, set Oldest Accepted to at least TLSv1.2.
After installation, test connections to the secure ports in use from client applications. Make sure clients accept the certificate without warnings about its name, validity period, or certification chain.
Listener Settings
Determine which protocols your organization will use. In the Listener settings of the corresponding modules, keep only the required ports. Remove unused listener sockets.
For TCP ports that must establish TLS immediately after a client connects, set Init SSL/TLS to On.
Authentication and Login Protection
Configure password requirements through Server-wide or Domain Account Defaults. Set the minimum password length, set Password Complexity to letters and digits, and enable Prohibit reusing previous passwords.
For one-way password storage, select UB-crpt in Password Encryption. The default A-crpt setting allows the Server to recover the original password. Avoid U-crpt for new passwords because it uses only the first eight bytes of the password.
Before switching to UB-crpt, check which login methods your clients use. The Server stores each password in the new format the next time it is changed. Clients can then use PLAIN or LOGIN over TLS with that password. They cannot use CRAM-MD5 or other SASL methods that require the original password.
Set the number of failed attempts and the blocking interval in Failed Logins Limit. Enable Hide 'Account Unknown' messages so that Server responses do not reveal whether an Account exists.
Set Secure Only to Require TLS. The Yes setting allows some authentication methods over unencrypted connections. Before changing this setting, verify that you can access the WebAdmin Interface over HTTPS.
Enable Kerberos, LDAP/LDAPS, and External Authentication only for Accounts that need these login methods.
Configure Two-factor Authentication for the WebUser Interface and XIMSS. Define how users will receive one-time codes and how they can recover access if they lose their second factor.
Create a separate named Application-Specific Password for each mail client or device. Delete its password if the device is lost or the application is no longer used.
Administrator Accounts
Create individual administrator Accounts in the Main Domain and grant only the required access rights. Use postmaster for initial configuration and emergency recovery. Do not share an administrative login among staff members.
On the HTTPA listener, set Remote IP Address Restrictions to Grant and list the addresses of administrative workstations, the VPN, or the access gateway. On each Cluster Backend, also list the IP addresses that the Frontends use to connect to its WebAdmin Interface.
For remote administration, use HTTPS through a VPN or access gateway. Enable multi-factor authentication on the VPN or gateway. Do not expose the unencrypted port 8010 or the PWD module CLI on port 106 to external networks.
SMTP Security
Configure users' mail clients to send mail using SMTP AUTH over TLS. If all senders authenticate, set Relay to any IP Address to nobody in the Relay panel. Make sure Relay to Client IP Addresses is set to simple or no. Include only hosts allowed to relay without authentication in the Client IP Addresses list.
Disable Relay to Hosts We Backup if the Server does not perform this role. After configuration, check for open relaying from an external network without authentication.
In the SMTP receiving settings, enable Verify HELO for non-clients. Enable Verify Return-Path for senders whose SPF records the Server should check during MAIL FROM.
To check DMARC, set Check SPF records to with DMARC. The Server checks DMARC after receiving the message body. If the sender's Return-Path was not verified, DMARC can pass only with a valid DKIM signature aligned with the domain in the From header field. The Server skips SPF and DMARC checks for Client IP Addresses and White Hole Addresses.
Set limits on message size, recipients per message, and recipients per time period from a single IP address. Configure the required antivirus and anti-spam filters.
For domains that require delivery over TLS, select Always (high security) in the SMTP Host Profile. This mode requires STARTTLS and verifies the remote server's certificate.
If the remote server does not advertise STARTTLS or its response to this command is neither 220 nor 4xx, all messages in that host's queue are rejected immediately.
A 4xx response, TLS negotiation failure, or certificate verification failure leaves messages in the queue for further delivery attempts. A message is rejected if its next retry would exceed the delivery period set by for. Messages are not sent without encryption in this mode.
The Wherever possible (low security) mode does not verify certificates and may send mail without encryption. See Secure Mail Transfer for details.
Account and Outgoing Mail Restrictions
Use Classes of Service and Account Defaults to enable only the required Services. Disable Relay for Accounts that do not need to send mail through SMTP from external addresses.
In Outgoing Mail Transfer, configure Outgoing Mail Limit, Outgoing Recipients Limit, and Max Recipients per Message.
In the same section, set 'From' Address Restrictions and 'From' Name Restrictions to Strict if users must send mail only under their own names. Use Relaxed address restrictions when users need to send from aliases, groups, or delegated Accounts.
Sending on behalf of another Account requires the Delegate right granted by that Account or the administrative CanImpersonate right.
After enabling these restrictions, check mail forwarding rules. The Forward to action sends a message on behalf of the Account, while Redirect to and Mirror to preserve the original sender and may be rejected.
Set Allowed Mail Rules to All But Exec. If users do not need forwarding, select Filter Only.
Child Processes Manifesto
Check the Child Processes Manifesto in the Settings/ChildProcs.data file in the Server base directory. Keep only the external programs in use. The Manifesto also restricts CGI programs, PIPE module programs, and programs launched by the Execute rule action.
The Server checks the beginning of the command line, including the program path and any specified arguments. Do not use / or . entries, which allow arbitrary programs with these prefixes. Restrict OS permissions to modify the Manifesto and the executable files. Restart the Server to apply changes.
Logs and Event Monitoring
Enable Log Login/Logout for administrator Accounts. Review login logs, setting updates, authentication and TLS errors, and increases in outgoing mail from individual Accounts.
If needed, configure logging to a remote syslog server. Enable Detailed Logging only while troubleshooting and restrict access to log files.