If you want to set up a secure TCP-to-NJE gateway, you need to:
- Include the SECURE statement in the SMTP configuration data set.
- Create a security data set that contains a list of NJE users who are authorized to use the gateway.
- Create a mailfiledsprefix.SECURITY.MEMO data set. The contents data set are sent to unauthorized NJE users whose mail is rejected. See Rejected mail examples for sample contents of this data set. This data set must be defined as LRECL=255 and RECFM=VB. It will be dynamically allocated by SMTP when needed.
The SMTP security data set is pointed to by //SECTABLE DD statement. The security table data set must be allocated with LRECL=255 and RECFM=VB. Records whose first nonblank character is an asterisk (*) are treated as comments and are ignored.
Use the following format when creating the list of NJE users:
>>-NJE_userid--NJE_nodeid---------------------------------------> >--+----------------------------------------+------------------>< '-nickname--primary_nick?--primary_mbox?-'
- NJE_userid
- The NJE user ID of the authorized user.
- NJE_nodeid
- The NJE node ID of the authorized user.
- nickname
- The name by which this user is known on the TCP side of the gateway. This name must not contain any special characters, such as < > ( ) [ ] \ . , ; : @ and ".
- primary_nick?
- Either Y or N. If Y is specified, then mail addressed to nickname@smtp-gateway is automatically forwarded to NJE_userid at NJE_nodeid. Each nickname can have only one primary_nick? record set to Y.
- primary_mbox?
- Either Y or N. If Y is specified, then mail from NJE_userid at NJE_nodeid is converted to nickname@smtp-gateway before it is sent to the TCP recipient. Each NJE_userid, NJE_nodeid pair can have only one primary_mbox? record.