Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Change SMTP Configuration

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Change SMTP Configuration

    Rick, We are using the SMTP server on many different iSeries boxes and it works great. It's very easy to setup. Here's some info from IBM that should help you get started... http://www-912.ibm.com/supporthome.n...ument/10000051 Enjoy... Document Title: Configuring OS/400 SMTP Document Description: Latest SMTP and MSF PTFs: o MF24922 o MF25210 o SF63411 5769TC1 1000 o SF63688 5769TC1 1000 E-mail Consult Line Versus Support Line Definition: Refer to Rochester Support Knowledgebase document 14813916. To link to 14813916 immediately, click here . http://as400service.ibm.com/supporth...ument/10000051 Refer to Rochester Support Knowledgebase document 14654719 for instructions on collecting SMTP Flight Recorders (Section 1 and Section 1.5), Communications Trace (Section 4), and SMTP Cold and Warm Start (Section 1.75). To link to 14654719 immediately, click here . Refer to the IBM Redbook, AS/400 Electronic-Mail Capabilities (SG24-4703-00), for information on IBM OS/400 SMTP Server E-mail. Forwarding Internet Mail: Pages 188 and 189 of the AS/400 Electronic-Mail Capabilities Redbook. Rochester Support Knowledgebase document 11274322 -- To link to 11274322 immediately, click here . http://as400service.ibm.com/supporth...ument/10000051 Additional Rules for SNDDST Subject Line Page 198 Restricting Mail Relay and Spamming Rochester Support Knowledgebase document 16664138 -- To link to 16664138 immediately, click here . http://as400service.ibm.com/supporth...ument/10000051 Refer to PTF SF54014 Cover Letter -- To link to SF54014 cover letter immediately, click here . http://as400service.ibm.com/supporth...ument/10000016 E-mail Problem Determination: AS/400 Mail: Multiple SMTP Domains Behind a Firewall (SG24-5643-00) Chapter 7, pages 253 - 292 SMTP Journaling: http://www.as400.ibm.com/tstudio/tec...al/indexfr.htm Also, refer to pages 267 to 277 of the IBM Redbook, AS/400 Mail: Multiple SMTP Domains Behind a Firewall (SG24-5643-00) The following information is required to configure SMTP/POP on OS/400: 1 Are you using a filtering firewall or a mail relay? Examples: o Filtering Firewall Example: Linux Firewall or Cisco PIX with SMTP Port 25 TCP Open and DNS Port 53 UDP/TCP Open. NAT is being used. o Mail Relay Firewall Example: IBM Secure Way Firewall. The SMTP and DNS conversations are made directly with the mail relay on the firewall. The firewall or mail server makes a separate connection to an SMTP Server on the Internet. What is the IP Address of the firewall and/or mail relay? 2 Do you manage your own DNS Servers or does your ISP manage your DNS? What are the IP Addresses of the DNS Servers? Example: 192.168.1.254 192.168.2.154 3 What is the SMTP Domain Name that OS/400 will service mail for? Note: You always will receive mail if you attempt to send mail because you will receive undeliverables. Example: company.com 4 What interface and associated IP Address will be the IP Address that mail is received on OS/400? Example: 192.168.1.5 Step 1 Configure the Mail Domain Step 1a From an OS/400 command line, type the following: CFGTCP Press the Enter key. Step 1b Select option 12. Step 1c Fill in the following parameters: Host name server1 Domain name company.com Host name search priority *LOCAL Domain name server: Internet Address 192.168.1.254 192.168.2.154 Step 2 Receiving Mail for an SMTP Domain The iSeries 400 server will receive mail for SMTP Domains that are associated with an iSeries 400 server IP Interface; for example, you want to have the iSeries 400 server accept mail for SMTP Domain company.com. Step 2a From an OS/400 command line, type the following: CFGTCP Press the Enter key. Step 2b Select option 10. Step 2c Select 1=Add to add the 192.168.1.5 IP Address. Step 2d Define the SMTP Domain that the SMTP Mail Server will accept mail for. In the example, the SMTP Domain equals company.com. Define the Fully Qualified Domain Name of the Mail Server. Associate both the SMTP Domain and the Fully Qualified Domain Name (CFGTCP Option 12, Domain Name concatenated onto the Host Name). Note: If you wanted to receive mail for a second SMTP Domain named mail2.company.com, mail2.company.com would also be associated with the Interface 192.168.1.5. Step 3 A directory entry (WRKDIRE) of INTERNET SMTPRTE is required. Step 3a Does the following directory entry exist? User ID: INTERNET Address: SMTPRTE To find out if the directory entry INTERNET SMTPRTE exists, do the following: o Issue the WRKDIRE command. o Press F19 (Shift F7). o The Position to parameter appears. o Type in INTERNET. o Press the Enter key. If an entry exists for INTERNET SMTPRTE with the USRID(INTERNET SMTPRTE), USRD('UserID to send to Internet'), SYSNAME(INTERNET)USER, and PREFADR(NETUSRID *IBM ATCONTXT), skip to step 4 below. Otherwise, if INTERNET SMTPRTE is not an entry in the System Distribution Directory (WRKDIRE), go to step 3b Step 3b Add the directory entry INTERNET SMTPRTE. Issue the following command with the parameters shown: ADDDIRE USRID(INTERNET SMTPRTE) USRD('UserID to send to Internet') USER(*NONE) SYSNAME(INTERNET) PREFADR(NETUSRID *IBM ATCONTXT) Step 4 Configure the route to SMTP gateway parameters named User ID and Address. Step 4a On an OS/400 command line, type the following: CHGDSTA Press F4 to prompt. Step 4b Fill in the User ID and Address parameters under Route to SMTP gateway. Step 5 Configuring or not configuring a mail relay -- you have to decide! The iSeries 400 server is configured in CFGTCP Option 10 to accept mail for company.com. What happens with mail destined for all other domains that are not company.com? Two scenarios exist: Scenario 1: Filtering Firewall Example: Linux Firewall Cisco PIX Firewall IBM NWAYS Router A filtering firewall will allow Port 25 SMTP Traffic to pass through the firewall. Typically, some form of NAT (Network Address Translation) is also configured. Scenario 2: Mail Relay Firewall Example: AIX Secure Way Firewall Check Point Firewall A mail relay firewall has SMTP code that listens for inbound mail and accepts the mail. This inbound connection is closed and then the SMTP code on the firewall makes a new connection with the destination Internet mail server or firewall. IBM e-Server => connection 1 => AIX Secure Way Firewall => connection 2 => Internet Mail Server Two separate SMTP connections are made. The initial connection (connection 1) is between iSeries 400 server SMTP and the SMTP code residing on the AIX secure way firewall. After the AIX firewall receives the e-mail, the SMTP connection is closed. Then the SMTP code on the AIX secure way firewall opens a separate SMTP conversation (connection 2) to the Internet mail server. Step 5a Configure the parameters for retries by minute, retries by day, and retries by hour by issuing the following command: CHGSMTPA Press F4 to prompt. Step 5b Retries by minute: Number of retries 3 Time interval 1 Retries by day: Number of retries 0 Time interval 0 Retries by hour: Number of retries 0 Time interval 0 Step 5c Page down. If a mail relay firewall is being used, proceed to Step 6. If a filtering firewall is being used, do not perform Step 6. Instead, proceed to Step 7. Step 6 Using a Mail Relay Firewall (Scenario 2: Mail Relay Firewall) Configuring the Mail Router parameter and the Firewall parameter to *Yes tells the SMTP server to send all mail that is not for domain company.com to the mail relay named mailrelay. Step 6a Configure the Mail Router = mailrelay. Step 6b Configure the Firewall = *YES. Note: The Mail Router parameter must be an alphanumeric name and not an IP Address. Also, an entry must be made in the host table of the server to associate the name mailrelay to the IP Address 192.168.5.254. Step 6c Configure a Host Table Entry for 192.168.5.254 mail relay. Step 6d On an OS/400 command line, type the following: CFGTCP Press the Enter key. Step 6e Select Option 10. Step 7 Using a Filtering Firewall Scenario 1: Filtering Firewall SMTP (Port 25) TCP traffic is allowed inbound and outbound through the firewall. The SMTP code on the iSeries 400 server performs DNS lookups to the ISP's DNS server. DNS (Port 53) UDP/TCP traffic is allowed to flow inbound and outbound to the ISP's DNS Server. Step 7a Configure the Mail router parameter. Mail router = *NONE Step 7b Configure the Firewall parameters. Firewall = *NO Step 7c Press the Enter key. Step 8 Configure a Mail Account Create a mailbox for user1. Note: User1 must already have user profile (CRTUSRPRF). Step 8a On an OS/400 command line, type the following: DSPNETA Press the Enter key. Look at the system name defined in the Current system name parameter. For illustration purposes, assume that the system name is SystemA. Step 8b On an OS/400 command line, type the following: WRKDIRE Press the Enter key. Step 8c Select 1=Add to create a directory entry as shown below: Work with Directory Entries Type options, press Enter. 1=Add 2=Change 4=Remove 5=Display details 6=Print details 7=Rename 8=Assign different ID to description 9=Add another description Opt User ID Address Description 1 USER1 SYSTEMA Step 8d Press the Enter key. Step 8e Fill in the following: Step 8f Page down three times to the parameters Mail service level and Preferred address. Step 8g For a POP Mailbox, configure Mail service level = 2. Step 8h and Preferred address = 3. Step 8i Press F19. F19 takes you to the CHGSMTPA screen where the SMTP address is configured for user1. Step 8j SMTP user ID = user1 Step 8k SMTP domain = company.com Step 9 Ensure that MSF and the SMTP servers are active. Step 9a Issue the WRKACTJOB SBS(QSYSWRK) command. Step 9b Ensure that the MSF jobs are active. Step 9c The MSF job logs should not contain diagnostic or escape messages. Step 9d Ensure that the SMTP servers are active in subsystem QSYSWRK. Issue the following command: WRKACTJOB SBS(QSYSWRK) Step 9e Ensure that no diagnostic or escape messages exist in the following: QTSMTPBRCL QTSMTPBRSR QTSMTPCLTD QTSMTPSRVD Step 10 Use SNDDST to send an e-mail to user1@company.com. Step 10a Page down. Step 10b Press the Enter key. Note: Send distribution completed successfully only means that the SNDDST command passed the e-mail to MSF. This has nothing to do with whether the recipient received the message. A communications trace would be required if the recipient was remote to the iSeries 400 server. Step 11 The mail message should reside in '/qtcptmm/mail/user1'. Step 11a Issue the WRKLNK '/QTCPTMM/MAIL' command. Step 11b Press the Enter key. Step 11c Type 5 Display next to the MAIL Object Link. Step 11d Type 5 next to USER1 Object Link to look at the messages in the mailbox of USER1. Step 12 View the e-mail. Step 12a Use EDTF to view the message. Step 12b edtf '/QTCPTMM/MAIL/USER1/JW175980.NOT' Helpful Hints: o If you have two separate mail server platforms that are not serviced by a common global address book, for example, OS/400 SMTP on one system and SendMail on a RISC 6000 system, the mail domains should be different, meaning CFGTCP Option 12 Domain should be different if you have two separate mail servers handling SMTP Mail. Two mail servers cannot be serviced by a single MX record if no global name and address book (like in Domino) exists to correlate which mail server the mail user resides on. IBM would be able to assist with this scenario under a Consult Line Contract. o OS/400 SMTP will receive mail for any domains that are associated with an active interface on the OS/400 Platform. These domains are associated with the OS/400 Server IP Interfaces in CFGTCP Option 10. 10.10.10.1 company.com secondcompany.com thirdcompany.com OS/400 SMTP will receive mail for Domains company.com, secondcompany.com, and thirdcompany.com. Note: When OS/400 SMTP is configured correctly and the latest SMTP code is applied for MSF, SMTP, and POP, inbound e-mail issues will most likely be related to issues external to OS/400 SMTP. Issues may exist with either the firewall configuration or DNS MX and A Record configuration. IBM would be able to assist with this complex mail scenario under a Consult Line Contract. o OS/400 support provides assistance to specific SMTP Questions. OS/400 SMTP Support includes evaluating one communications trace to determine if OS/400 SMTP is properly sending out SMTP Mail as configured. Once a determination has been made by the IBM Software Engineer that OS/400 SMTP is sending mail properly, support will be complete. Determining why a user on another physical mail server (Domino, Exchange, Sendmail, OS/400) does not receive the mail will require a Consult Line Contract. Issues with DNS not resolving correctly within your intranet or on the Internet will require a Consult Line Contract. Issues with filter rules on a firewall will require a Consult Line Contract. Troubleshooting of proper MX and A Records on an ISP DNS Server or on your DNS Server will require a Consult Line Contract. For a detailed description of what e-mail issues are covered under Support Line and what e-mail issues are covered under Consult Line, refer to: E-mail Consult Line Versus Support Line Definition: Refer to Rochester Support Knowledgebase document 14813916. To link to 14813916 immediately, click here . http://as400service.ibm.com/supporth...ument/10000051
    Tags: None
  • #2
    Change SMTP Configuration

    Scott, thanks for the information. We will go thru it. I guess our basic question is this: we currently route AS/400 email to the pc-based mail server (Novell's Groupwise). It works good. But is the AS/400 capable of "replacing" this server and route the AS/400 mail to the internet. Our AS/400 is not yet accessible on the internet, and is this an obstacle?

    Comment

    • #3
      Change SMTP Configuration

      Hello Rick, Yes, you can route your email through the AS/400 instead of the Novell box. I'll assume a few things... You have internet access to your office already and your users use Outlook or Outlook Express for email. There are a few simple TCP/IP configuration changes that will allow your AS/400 to send/receive email to the internet. You may have some firewall issues to address. Your email users simply have to point their smtp server account info to your AS/400 IP address. If you plan on using the AS/400 as your inbound email server you will have to setup your users with smtp accounts. The previous email should address those item. IBM's web site (www.as400.ibm.com, click on Support and then click on knowledge base) is a excellent source of info on this subject. Hope this helps...

      Comment

      • #4
        Change SMTP Configuration

        We are currently running SMTP, routing all email from the AS/400 to our pc-based mail server. Management is wanting to know if the AS/400 can send its email directly and not use the mail server. If this is possible, perhaps you can pass along what we need to do to change our current configuration, or point us to some documentation that will indicate what needs to be modified... Thanks!

        Comment

        • #5
          Change SMTP Configuration

          Hello I setup every thing like: CFGTCP. WRKDIRE. CHGDSTA. CHGSMTP. do all steps and i tried many time to send email from my as400. but i receive messages like: SNDDST TYPE(*LMSG) TOINTNET(('kbenmamar@yahoo.com')) LONGMSG('this is themessagetest') Description of document not correct. demand distribution of QSECOFR is failed. Demand of sending distribution is failed. I hope i translate good from French. Thanks in advance.

          Comment

          Previous template Next
          Working...
          X