Skip to content

8 EMM Start/Stop

Before starting EMM services you should first make sure that the DBMS server with the EMM database is already up and running.

To have all EMM services automatically start and stop at server startup and server shutdown in the correct sequence, you have to execute global script /root/bin/agnitas.sh on each EMM server with option start, stop or restart (stop + start). Option status shows the current status of all EMM services installed on the server.

If you want to start all EMM services automatically at boot time, have a look at section Configuration files.

8.1 Troubleshooting: EMM Does Not Send Emails

The most “popular” problem of EMM is, that no emails are sent out. Therefore, we have compiled a checklist with the most common reasons why EMM does not send emails:

  1. The mailing or the choosen target group has no recipients.
  2. The merger service has not been started. Check on the appropriate server with script /root/bin/agnitas.sh status and start with /root/bin/agnitas.sh start.
  3. The mailer service has not been started. Check on the appropriate server with script /root/bin/agnitas.sh status and start with /root/bin/agnitas.sh start.
  4. Postfix' mail log file in /var/log/maillog shows errors.
  5. Packages postfix and sendmail-milter are not installed on servers with mailer service installed.
  6. Postfix has not been started on servers with mailer service installed. Check with command systemctl status postfix and start with systemctl start postfix.
  7. Postfix is no longer running on servers with mailer service installed. Check with ps aux | grep postfix/master.
  8. Postfix' mailqueue at /var/spool/postfix does not exist (solution: re-install Postfix).
  9. The wrong MTA is active on servers with mailer service installed (Sendmail, qmail, Exim, etc.).
  10. Port 25 has not been opened in the firewall.
  11. Service cron is disabled. Check with systemctl status crond.
  12. SELinux is enabled.
  13. The server running the mailer service uses a virus scanner that prevents the start of the XML RPC backend process (see file backend.log in directory /home/mailout/log/ for an entry like "Error: Could not find or load main class org.agnitas.backend.MailoutServerXMLRPC")
  14. For reverse lookups, no PTR records do exist for the IP addresses of the servers with mailer service installed (so that mails are blocked as spam by mailbox providers on the receiving end).