When I set up sendmail for the sole purpose of using emails as a print destination for Infoprint IP Printway, there appears to be a conflict on port 25.
The problem I have now is that there is a conflict on port 25. The Redbooks publication z/OS V1R12 Communications Server TCP/IP Implementation: Volume 2 Standard Applications (SG24-7897-00) directs the user to reserve port 25 for sendmail with the following TCP/IP PORT parameters: 25 TCP OMVS
But port 25 is already reserved for SMTP with the following TCP/IP PORT parameters: 25 TCP SMTP
Regardless of which TCPIP PORT statement is specified, SMTP and sendmail cannot be brought up at the same time because of this conflict.
Can the port for sendmail be something else instead of 25? Or, is port 25 a requirement?
Resolving the problem
Infoprint uses sendmail client functions and not the sendmail server functions so there is no conflict with port 25. Port 25 is necessary only for the server function to open a listening port.
You do not need to start the sendmail listening daemon. Any undeliverable emails will be handled by SMTP. Because all the error messages you are seeing describe errors running the sendmail listening daemon, those messages should go away if you do not start the sendmail listening daemon.