"Wanna" ransomware outbreak. Please see this Sophos article sophos.com/kb/126733 for advice on how to protect your organization. Immediate action recommended.
An abort entry in the PureMessage log (typically the /opt/pmx/var/log/pmx_log file) means that sendmail informed PureMessage that it was no longer processing the connection. This causes the ABORT callback to be called in PureMessage, which then logs the corresponding message in the log file.
An abort message could be triggered in two ways:
This type of abort is part of everyday SMTP traffic problems and can usually be ignored. The abort could result in delayed delivery of mail processed on the affected connections.
To discover what is triggering the abort, find the queue ID of the aborted message reported in the PureMessage log, and check the same queue ID in /var/log/maillog (or the corresponding sendmail log on your server). The maillog will show what happened to the aborted message.
When sendmail aborts a connection with PureMessage, it usually logs a reason. The lines that provide information about such aborted connections can be identified by looking for "milter_" in the maillog. If the reason was 'timeout', usually the message took too long to process by PureMessage, and sendmail therefore ended its side of the connection. To prevent this, increase the sendmail Milter timeouts.
Such timeout errors in the maillog could mean that PureMessage wasn't running, or that it was not listening on the port that sendmail thinks PureMessage can be reached at.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.