Maximo hands every e-mail to one mail (SMTP) server named in System Properties. If that server is not set, templates, escalation notifications and workflow e-mails are created but never delivered.
Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that the same mail properties, default values, template settings, the SEND_FAILED action and all the messages below are present (17 November 2026), after reading the same on Maximo 7.6.1.2 (4 November 2026). Both checks were read-only: neither system has a mail server, so we have not sent or failed an e-mail on either version.
IBM’s page: IBM’s current Maximo Manage documentation says: “a communication log lists the inbound and outbound communications for a record, such as a ticket or work order.”
Last checked: 17 November 2026
The mail properties on the lab system (names and descriptions as Maximo stores them):
| Property | What it does |
|---|---|
mail.smtp.host | The name of the SMTP mail server. Empty = no mail. |
mail.smtp.port | Mail server port. |
mail.smtp.ssl.enable, mail.smtp.starttls.enable | Encryption to the mail server. |
mxe.smtp.user, mxe.smtp.password | Mail server login, if the server needs one. |
mxe.smtp.connectiontimeout, mxe.smtp.timeout | Time-outs in milliseconds (default 180000). |
mxe.adminEmail | The Maximo administrator’s address, also the fallback sender. |
mail.smtp.sendpartial | Send to the valid addresses when some are invalid. |
mxe.email.content.type, mxe.email.convertToPlainText | HTML or plain text. |
mail.debug | JavaMail debug output. |
The communication log. When a template has Comm Log Entry ticked (it is ticked on every delivered template), each send writes a log row against the record, with recipients, subject, message and date. It shows on the record’s Communication Log tab.
Failed messages. With Track Failed Messages ticked on the template, a failed send is kept in the communication log and marked as failed. Maximo does not retry by itself. IBM’s documented way is an escalation that runs the delivered action SEND_FAILED on records with failed log rows. That action is delivered on both systems we read; only the escalation has to be built. No delivered template had tracking on.
Remember: a communication log row proves that Maximo created the e-mail, not that it was delivered.
mail.smtp.host, and the port, encryption, user and password if your server needs them. Set mxe.adminEmail.mxe.adminEmail. Message BMXAA9507E describes the order: the user’s address, then mxe.adminEmail, else no communication.mail to DEBUG and create a COMMTEMPLATE logger at INFO if it is missing. Attach an appender, Apply Settings, and read the server log. On Maximo Application Suite the server log is a container log; IBM’s APIs for administrative utilities page describes how to download log files.mxe.adminEmail), or BMXAA0258E “Please enter a sender e-mail address”.On a Maximo 7.6.1.2 lab system we read the mail properties and their values, the communication log, the logger table, the SEND_FAILED action and the message texts, all with read-only queries. We then read the same on a Maximo Application Suite 9.1 system. Neither system has a mail server, so nothing was sent and nothing was changed.
Not tested: setting a mail server, a failed send, and the SEND_FAILED retry.
This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.