News Stay informed about the latest enterprise technology news and product updates.

Sending and receiving e-mail on the 400

Sending and receiving e-mail on the 400

1. Distribution services:

a. Add a host table entry for your local e-mail server.

b. CHGSMTPA RTYDAY(0 0) RTYHOUR(0 0) USRIDDELIM('?') MAILROUTER('sam- sheepdog.dimins.com') FIREWALL(*NO) DIALSCD(*NO)

[Insert your mail router information in MAILROUTER parameter]

c. ADDDIRE USRID(INTERNET GATEWAY) USRD('Internet mail gateway')

d. There should be a directory entry for each user to whom e-mail will be sent.

Set up SMTP (TCP/IP) mail

Before setting up e-mail on the iSeries 400 system, you need to answer the following questions:

1. What will my e-mail addresses look like?
2. What is the address of my Name Server (DNS)?
3. Do I have a firewall?
4. Do I have a Mail Proxy, Mail Router or Mail Relay?
5. If the answer to 3 or 4 is "yes", what is the IP Address of each?

In order to configure the iSeries 400 system as an Internet or intranet e-mail server, you need to decide or determine the format of your Mail Addresses, and have your Name Server(s) configured appropriately. For example, if you want your Mail Addresses to look like:

john.doe@mycompany.com and jane.roe@mycompany.com

You need to have your Name Server (DNS) provider configure the Name Server to identify your iSeries 400 system as the Mail Server for "mycompany.com". This is known as creating an MX Record.

Receiving Mail

In order for the iSeries 400 system to receive mail, it must be able to recognize the recipient's SMTP Domain (the part of the e-mail address to the right of the '@') as its own. This is done by configuring the LOCAL HOST TABLE as follows, again assuming that our e-mail addresses look like "john.doe@mycompany.com":

1. Enter the following command from an OS/400 command line:
CFGTCP
2. Select Option 1.z 3. Record all of the IP Addresses there (ignore 127.0.0.1; it is a dummy address) and press F3.
4. Select Option 10.
5. For each IP Address recorded in Step 3, if the address already exists in the table, use Option 2 to add the name mycompany.com to the name(s) already associated with that address. If the address is not in the table, use Option 1 to add it, again associating the name mycompany.com with the address.
6. Return to the CFGTCP menu, and select Option 12.z 7. If there is nothing specified in the HOST NAME field, enter the iSeries 400 System Name.
8. If there is no value in the DOMAIN NAME field, enter mycompany.com.
9. If at V4R2 or higher, enter *LOCAL for HOST NAME SEARCH PRIORITY, enter the address(es) for your Name Server(s), press Enter, and skip to Step 12.
10. Select Option 13.
11. Enter the address(es) for your Name Server(s), enter *LOCAL in the last parameter field (Searched First) and press Enter.
12. At this point, you should be back at the CFGTCP menu, and you have the basics set up for receiving mail. Subsequent steps will depend on the types of Mail Users you have.

Receiving Mail for POP Users

Even if they never sign on to the iSeries 400 system, each POP mail user is considered an iSeries 400 user, and must have a user profile. If the user normally signs on to the iSeries 400 system, that is not a problem; he/she already has a user profile. If that is the case, simply skip to the section on Directory Entries. Otherwise, just use the CRTUSRPRF command to create a user profile. Most of the defaults can be used, but the following parameters require attention:

PWDEXP

Setting this parameter to *YES is a bad idea, since it forces the user to change the password, and he/she would have to sign on to the iSeries 400 system to do that. It is best to code this parameter as *NO.

INLMENU

Setting this parameter to *SIGNOFF will prevent this User Profile from being used to sign on to the iSeries 400 system. If the user does not need to sign on to the iSeries 400 system, this is a good idea.

LMTCPB

This should be set to *YES for security purposes.

PWDEXPITV

Password Expiration Interval; related to PWDEXP. If the user does not sign on to the iSeries 400 system, this should be set to *NOMAX. Otherwise, when the password expires, the user will no longer be able to see his/her mail.

The user profile and password configured here are the same ones that are configured on the POP Client as UserID, ACCOUNT, or similar parameter. Often, for security reasons, the User Profile is not the same as the e-mail user. For example, if the e-mail address for the user is jane.roe@mycompany.com, the User Profile name might be ROE or JROE. Using that example, the command would be:

CRTUSRPRF USRPRF(JROE)
PWDEXP(*NO)
INLMNU(*SIGNOFF)
LMTCPB(*YES)
PWDEXPITV(*NOMAX)

Each user also requires a Directory Entry. The Directory Entry is where the e- mail address gets matched with the User Profile. If the user does not already have a directory entry, we need to add one. Let us use the example of jane.roe@mycompany.com to add a new Directory Entry, using the User Profile from the example above:

ADDDIRE USRID(JANEROE SYSNAME)
USRD('Jane Roe - POP3 User')
USER(JROE)
SYSNAME(*LCL)
MSFSRVLVL(*SYSMS)
PREFADR(*SMTP)

Note: If the user already has a Directory Entry, use the following command:

CHGDIRE USRID(JANEROE SYSNAME) MSFSRVLVL(*SYSMS) PREFADR(*SMTP)

Once we have created the Directory Entry, we need to use the command WRKDIRE USRID(JANEROE SYSNAME). We then select Option 2 to change the Entry. On the next screen, press F19. This will present a confirmation message at the bottom of your screen; just press enter to get the following screen, and enter the information as shown:

Add Name for SMTP

Type choices, press Enter.

User ID . . . . . . . . : XZY1404
Address . . . . . . . . : RCHASBDS

SMTP user ID . . . . . . jane.roe_______________
SMTP domain . . . . . . . mycompany.com_______________________ __________________________________________________________________

SMTP route . . . . . . . ___________________________________ _________________________________________________________________

You will need to press Enter a couple of times to get back to the WRKDIRE screen.

Receiving mail for OV/400 users

OfficeVision/400 users will already have a User Profile and a Directory Entry. All you need to do is add the e-mail address to the Directory Entry. To do that, just enter WRKDIRE to show all of the Directory Entries. Then for each user do the following:

Select Option 2 to change the entry. On the next screen, press F19. This will present a confirmation message at the bottom of your screen; just press enter to get the following screen, and enter the information as shown:

Add Name for SMTP

Type choices, press enter.

User ID . . . . . . . . : XZY1404
Address . . . . . . . . : RCHASBDS

SMTP user ID . . . . . . jane.roe_______________
SMTP domain . . . . . . . mycompany.com___________________________

__________________________________________________________________

SMTP route . . . . . . . _______________________________________ _________________________________________________________________

You will need to press Enter a couple of times to get back to the WRKDIRE screen.

Receiving Mail for Domino Users

No additional OS/400 configuration is required to allow DOMINO/400 users to receive mail; see the Lotus documentation for required Domino configuration steps. The following is a link to a page where you can download an Adobe Acrobat file.

Sending Mail

No additional configuration is required to allow POP or Domino users to send mail. In order to allow OV/400 users to send mail, you need to:

ADDDIRE USRID(INTERNET GATEWAY)
USRD('Allow OV/400 to send INTERNET Mail')
SYSNAME(INTERNET)
MSFSRVLVL(*USRIDX)
PREFADR(NETUSRID *IBM ATCONTXT)

And:

CHGDSTA SMTPRTE(INTERNET GATEWAY)

If You Have a Firewall and/or a Mail Proxy:

CHGSMTPA MAILROUTER(MAIL.ROUTER.NAME) FIREWALL(*YES)

Then, make sure that mail.router.name is either in the iSeries 400 Host Table (CFGTCP Option 10) or resolvable via your Name Server (DNS).

After all configurations are complete, do the following:

1. ENDTCPSVR *SMTP
2. ENDMSF
3. STRTCPSVR *SMTP
4. STRMSF
5. WRKACTJOB SBS(QSYSWRK)
6. In the display that results from Step 5, verify that there are:

- Three jobs named QMSF running
- A job named QTSMTPBRCL running
- A job named QTSMTPBRSR running
- A job named QTSMTPCLNT running
- A job named QTSMTPSRVR running

If Mail Does Not Work

If mail does not work, after following the instructions above, you can do some preliminary troubleshooting by looking at the job logs for the QMSF jobs, and for QTSMTPBRSR, QTSMTPBRCL, QTSMTPCLNT AND QTSMTPSRVR. If any of these jobs is not running, we definitely need the job logs. Most error messages that would be found in those logs will either have a workable recovery procedure, or will lead to a PTF.

Dig Deeper on iSeries managed email and groupware

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataCenter

Close