A fix is available
APAR status
Closed as program error.
Error description
In CSSMTP, the Message-ID header line is automatically added by CSSMTP when it is missing from a mail message. CSSMTP also automatically generates the Receive header. In some circumstances this is undesirable. Need to provide users with the capability to disable automatic generation of Message-ID and Receive headers. Additional Symptom(s) Search Keyword(s):
Local fix
None for Receive header. CSSMTP will not generate Message-ID header if user includes their own within the mail message.
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release(s) 12 and 13: * * CSSMTP * **************************************************************** * PROBLEM DESCRIPTION: User information is automatically * * added to the Message-ID: header and * * the Received: header. In some * * circumstances this is undesirable. * **************************************************************** * RECOMMENDATION: * **************************************************************** User information is automatically added to the Message-ID: header and the Received: header. In some circumstances this is undesirable. A new configuration parameter has been added to control the information used in the Message-ID: header, the 'for' field in the Received: header, and the 'Id' field in the Received: header. The new parameter is UserInfo in the Header configuration statement. Header { Date Yes #Create the date: header (default) #Date No #Do not create the missing date header UserInfo Yes #Include user information in headers (default) #UserInfo No #Do not include user information in headers } +-------------------------------------------------------------+ + Please check our Communications Server for OS/390 homepages + + for common networking tips and fixes. The URL for these + + homepages can be found in Informational APAR II11334. + +-------------------------------------------------------------+
Problem conclusion
A new configuration parameter has been added to control the information used in the Message-ID: header, the 'for' field in the Received: header, and the 'Id' field in the Received: header. The new parameter is UserInfo in the Header configuration statement. Header { Date Yes #Create the date: header (default) #Date No #Do not create the missing date header UserInfo Yes #Include user information in headers (default) #UserInfo No #Do not include user information in headers } The following are the documentation updates: --------------------------------------------------------------- IP User's Guide and Commands, SC31-8780-09 and SC31-8780-10 8.5 DATA command: Define the following information as data Results: .... o If a Message-ID header is not explicitly specified in the mail message, the CSSMTP application adds one for this mail message. The Message-ID is a mail message identifier. For example: Message-ID: <TESTMAIL.SYS00006.CSSMTP1.mydomain.com. Sep302008.160454.541437.1> o The Message-ID header consists of the following: o TESTMAIL: The job name of the mail message of the JES spool file. This behavior can be modified with the Header statement in the configuration. See "31.x Header statement" in the "IP Configuration Reference". o SYS00006: The job identifier of the JES spool file This behavior can be modified with the Header statement in the configuration. See "31.x Header statement" in the "IP Configuration Reference". o CSSMTP1.mydomain.com: The fully qualified host name on which the CSSMTP application is running o Sep302008.160454.541437.1: The date and time when the mail message was processed. The value 160454 represents the time 16:04:54. o If this mail message cannot be delivered, the CSSMTP application appends a U to the end of the Message-ID into the undeliverable mail notification. For example: Message-ID: <TESTMAIL.SYS00006.CSSMTP1.mydomain.com. Sep302008.160454.541437.1U> --------------------------------------------------------------- IP Configuration Reference, SC31-8776-18 and SC31-8776-19 Chapter 31 Update section 31.3.1 CSSMTP configuration statements to add the UserInfo parameter to the Header statement in table 109. 31.3.1 CSSMTP configuration statements Table 109 lists CSSMTP configuration file statements. Configuration Required allowed file or by modify statement Default optional refresh Purpose --------------------------------------------------------------- .... Header * Date Yes Optional Yes Specifies the action to be * UserInfo Yes taken when creating RFC 2822 Mail headers. Update the section after section 31.7 that describes the Header statement added by PM74086. 31.x Header statement Use the Header statement to change the behavior of CSSMTP when creating RFC 2822 Mail headers. The mail headers are created when the JES spool file is processed. If the Header parameters are modified, mail headers that have already been created will not be altered. Syntax >>__Header__| Put Braces and Parameters on Separate Lines |_>< Put Braces and Parameters on Separate Lines: |__ _{______________________ _______________________________| |_| Header Parameters |_| |_}______________________| Header Parameters: _Date YES______ |__|_______________|________________________________________| |_Date__ _YES_ _| |_NO__| _UserInfo YES______ |__|___________________|____________________________________| |_UserInfo__ _YES_ _| |_NO__| Date Specifies if the Date: header is to be added by CSSMTP if it is missing. NO The Date: header is not inserted into the mail message by CSSMTP YES The Date: header is inserted into the mail message by CSSMTP. This is the default. UserInfo Specifies if user information is to be included in Mail headers created by CSSMTP. NO User information is not inserted into the mail message by CSSMTP. This applies to the following information: o The job name of the mail message of the JES spool file and the job identifier of the JES spool file will not be included in the Message-ID: header, if the Message-ID: header was generated by CSSMTP. o The CSSMTP JobName will be inserted in the 'for' field of the Received: header instead of the JES origin USER ID and the optional Notify USER ID o The job name of the mail message of the JES spool file and the job identifier of the JES spool file will not be included in the 'Id' field of the Received: header. YES User information is inserted into the mail message by CSSMTP. This is the default. * Cross Reference between External and Internal Names HHHMLCFG (EZAMLCFG) HHHMLCFP (EZAMLCFP) HHHMLCFG (EZAMLCFG) HHHMLCFP (EZAMLCFP)
Temporary fix
Comments
APAR Information
APAR number
PM76335
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1C0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-01
Closed date
2013-03-07
Last modified date
2013-05-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK92331 UK92332 PM87908
Modules/Macros
EZAMLCFP EZAMLEML EZAMLJSP EZAMLJSU HHHMLCFG HHHMLCFP
| SC31877619 | SC31878010 | SC31877618 | SC31878009 | SC31878009 |
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1C0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1C0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
06 May 2013