Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Created by Guest
Created on Jan 12, 2021

Queue SMTP Emails when SMTP Server is Unavailable

There are various scenarios in Maximo where email is sent explicitly from the various MXServer.sendEmail() methods. For example, the PM WOGEN cron task. If the email fails to send to the SMTP server (such as the SMTP server is down) it's gone forever. Depending on what tried to send the email would determine whether or not you see the error, but regardless, the email itself is not recoverable.

Emails can sometimes contain important information and customers shouldn't have to setup local relays to try and avoid cloud outages that may occur that would cause email to be lost. There is some functionality on communication templates for tracking failed emails, but we think a better solution would be to queue outbound emails for processing. We know there might be other email methods outside of MXServer.sendEmail where Maximo might create an explicit SMTP connection, but most scenarios (including communication templates) use the MXServer.sendEmail methods and simply addressing at that level would greatly improve reliability of email delivery.

Utilizing something like JMS/Kafka queues either to send all emails (which could then get processed via EJB) or track when emails failed to then reprocess seem like it'd be a net win. There is some functionality with email listener (for inbound emails) to utilize JMS as well. Adding one for outbound processing of emails would help ensure email messages are never lost.

Idea priority High
  • Guest
    Reply
    |
    Jan 13, 2021

    Putting the email in the standard sequential outbound queue could be problematic -- other outbound integrations would stop because SMTP is down. Maybe, instead, the message could be queued to the continuous inbound queue destined for COMMLOG. Take the idea or leave it...just getting ideas out there.

  • Guest
    Reply
    |
    Jan 12, 2021

    Email delivery and tracking is important. I would submit that any and all email, as it is processed through a queue, should also be logged in the COMMLOG table.