Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management and AIOps products. 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 Future consideration
Created by Guest
Created on Nov 2, 2022

Allow Mailman Server to continue processing other servers after a failed server

Please refer to We have 20 servers under the control of a single Mailman server , Which processes the message queue. We had a failure on 1 server , which in turn caused ALL other server messages NOT to be processed. which eventually IWS believed that they all went "UNLINKED" Mailman Server code works on the server tcp timeout parameter, to calculate the timeout value. But in this case the server OS was broken and didnt respond to the TCP Timeout value. We believe that a seperate timer would alleviate this SINGLE point of failure and ensure that ONLY 1 broken server goes unlinked in the group , not ALL members in the group.

Idea priority Medium