IBM Z Software
Hide about this portal
This portal is to open public enhancement requests against IBM Z Software 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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
You live and learn. We no longer need this enhancement. Most email servers have an option to use port 465 that is always encrypted. We configured it in Communication Server as always encrypted and then changed the port to 465 in MFA. It is working fine.
Joe
I do not see anywhere what type of additional information that you needed. However, I do see that the status was changed to Future consideration. Below is additional information that I came up with before seeing the status change.
Instead of connecting to port 25 on a mail server via TCP/IP and sending a format email, you put the email in the JES2 Spool. You put it in a specific sysout class and give it a writer name. You then close the spool file so it is freed.
CSSMTP then picks it up out of the JES2 spool. It validates a few things in the email. It then opens a TCPIP connection to port 25 on the mail server. It sends the mail to the mail server and deletes it from the JES2 spool. If it cannot connect to the mail server, it leaves the mail in the JES2 spool. Then after a period of time, it tries to send it again.
You need to allow for customization of two things, the writer name and the sysout class.
CSSMTP can be configured to invoke Communications Server’s AT-TLS to encrypt the traffic.
The other option to provide encrypted communication is to change your connection to port 25 to support encryption. That "may be" easier for you to implement but we are attempting get all of our email communications to go through CSSMTP.