System Services: Mail Server¶
System Services > Mail Server
This menu section in NodeWorx is where Server Administrators can manage their SMTP, POP3, and IMAP settings, as well as settings related to spam and virus scanning. This is also where the mail queue page is located.
While many tasks related to mail services can be completed via the GUI, there are many others that require configuration at the CLI, such as enabling greylisting or tarpitting, setting up custom SMTP relays, and defining specific outgoing IP addresses, per domain.
Detailed mail documentation can be found here.
Contents
MTA Settings¶
System Services > Mail Server > MTA Settings
The MTA Settings page allows Server Administrators the ability to manage SMTP settings over port 25. This SMTP port is managed by Qmail.
From the MTA Settings page, Server Administrators can easily manage:
The status of the SMTP service over port 25
MTA server settings
MTA bounce message settings
Inbound and Outbound SMTP settings
Detailed information on managing MTA settings can be found here.
SMTP logs can be found in the /var/log/smtp/ and /var/log/send/ directories.
Advanced Qmail configuration files can be found in the /var/qmail/control directory.
MDA Settings¶
System Services > Mail Server > MDA Settings
The MDA Settings page allows Server Administrators the ability to manage POP3 and IMAP settings over ports 143, 993, 110, and 995. These services are managed by Dovecot.
From the MDA Settings page, Server Administrators can easily manage:
The status of the POP3 and IMAP services
Dovecot server information related to POP3 and IMAP
Dovecot global settings related to POP3 and IMAP
Detailed information on managing MDA settings can be found here.
IMAP and POP3 logging can be found at /var/log/dovecot/dovecot.log.
Advanced Dovecot configuration files can be found in the /etc/dovecot directory.
MSA Settings¶
System Services > Mail Server > MSA Settings
The MSA Settings page allows Server Administrators the ability to manage Secure SMTP settings over ports 587 and 465. These services are managed by Dovecot. This allows users to use mail.{domain.com}, replacing {domain.com} with their domain, as the mail server in outside mail clients over ports 587 and 465, as long as their domain has a matching SSL with mail.{domain.com} listed as an alternate name.
From the MSA Settings page, Server Administrators can easily manage:
The secure SMTP ports
Secure SMTP settings
Documentation on managing MSA settings can be found here.
Spam Filtering¶
System Services > Mail Server > Spam Filtering
From the Spam Filtering page, Server Administrators can easily manage:
The status of the SpamAssassin service
Global whitelists and blacklists
SpamAssassin options
Bayesian scanning options
Advanced SpamAssassin custom options and spam preferences
Settings managed here are server-wide. SiteWorx accounts are able to manage their own, individual settings, as well. More information can be found here.
SpamAssassin logging can be found at /var/log/maillog.
Detailed information on managing SpamAssassin settings in NodeWorx can be found here.
Virus Filtering¶
System Services > Mail Server > Virus Filtering
Virus scanning via ClamAV only happens at the SMTP level. If a virus is detected, the message is automatically rejected. Because of this, if the ClamAV service is disabled, but SMTP Virus Scanning is enabled on the Virus Filtering page in NodeWorx, all mail service will be halted on the server until ClamAV is enabled, again.
The Freshclam service must be enabled in order for ClamAV virus definitions to be updated.
ClamAV also keeps its virus database in memory, and it is generally at least 1GB. This is one of the reasons it is required for all InterWorx servers to have both at least 2GB of RAM and a significant amount of swap. Otherwise, there is a serious risk of services being forced to stop due to a lack of memory, and the ClamAV service being unable to start. Information on the minimum requirements for InterWorx can be found here.
From the Virus Filtering page, Server Administrators can easily manage:
The status of the ClamAV service
The status of the Freshclam service
Whether SMTP scanning is enabled or disabled
ClamAV logging is found at /var/log/clamav/clamd.log
Freshclam logging is found at /var/log/clamav/freshclam.log
Detailed information on managing ClamAV settings can be found here.
Mail Queue¶
System Services > Mail Server > Mail Queue
From the Mail Queue page, Server Administrators can easily:
View and manage the contents of the mail queue
Send a test message directly from the server
Information on managing the mail queue can be found here.
Information on how to clear the mail queue can be found here.