MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2013

RE: SNDDST not working after V7 upgrade



fixed



Document Number: 562865621
Document Title:SMTP New Configuration Checklist, Short Version
Document Description:
This document is intended to identify the basic configuration elements for native SMTP server on the System i.
A.

Check the domain information:

Issue the CFGTCP command, press Enter, and select Option 12. There must be a host name and a domain name defined. In most cases, Host Name Search Priority should be *Local. Verify that the DNS addresses are correct. In the additional parameters, Port should be 53, Protocol should be *UDP. Retries and Time Interval are typically 2.

B.

Check the TCP interfaces:

Issue the CFGTCP command, press Enter, and select Option 1. Make note of each interface and verify that it is active. The 127.0.0.1 interface should be here, and should be active.

C.

Check the Host table:

Issue the CFGTCP command, press Enter, and select Option 10. Check for 127.0.0.1 with the names LOOPBACK and LOCALHOST. Check for the IP addresses from the TCP interfaces list. One of them should be listed here with the 'host.domain' name. If a mail router is being used, it must resolve with either the local host table or DNS resolution.

D.

Per II13869, verify that Restricted Rename and Unlink is *No for '/tmp':

Issue the WRKLNK '/tmp' command, and press Enter. Select Option 8 on /tmp, and press Enter. Page down two times. "Restricted Rename and Unlink" should be No. If not, change it to *No using the following command:

CHGATR OBJ('/tmp') ATR(*RSTDRNMUNL) VALUE(*NO)

In 61, this is corrected by a PTF SI36382. The informational APAR is just a work-around until the PTF is applied. 71 needs no PTF.

E.

Verify the SMTP subdirectories exist and check for old e-mail fragments:

Issue the WRKLNK '/QTCPTMM' command, and press Enter. Select Option 5 on /qtcptmm. There should be the following subdirectories: /ATTABOX, /DSN. /ENCODE, /FTRFILES, /LOCKBOX, /MAIL, /SMTPBOX, /TMP.

Select 2 on /ATTABOX. Check to see if there are old e-mail fragments. If so, remove them. Do the same for /SMTPBOX.

F.

Check the POP attributes:

Issue the CHGPOPA command, and press F4 to prompt. The Split Size should be *Nomax. The CCSID should typically be 00819.

G.

Check the distribution attributes if you are using the SNDDST command to send mail to an Internet address:

Issue the CHGDSTA command, and press F4 to prompt. Use MSF for Local should be *No. There should be a directory entry listed as the route to SMTP gateway. The most common is INTERNET GATEWAY.

H.

Check the directory entries if you are using SNDDST to send mail to an Internet address:

Issue the WRKDIRE command, and press Enter. There should not be a *ANY/*ANY directory entry. There should not be a *ANY entry with the address of this partition/system.

Select 5 on the directory entry from the distribution attributes (INTERNET GATEWAY). Check the first five lines; they should look like the following:

User ID/Address . . . . : INTERNET GATEWAY
Description . . . . . . : SMTP routing entry
System name/Group . . . : INTERNET
User profile . . . . . :
Network user ID . . . . : INTERNET GATEWAY
On the second to last page, it should look like this:
Locally-defined . . . . : Yes
Indirect user . . . . . : No
Mail service level . . : User index
Preferred address . . . : NETUSRID *IBM
Address type . . . . : ATCONTXT

If you have to create this directory entry, Mail Service Level is 1, Preferred Address is 9. Then press F4 to prompt for ATCONTXT for "address type" and and NETUSRID *IBM for "preferred address".

I.

Check the SMTP attributes:

Issue the CHGSMTPA command, and press F4 to prompt. On the first page, "Automatic Registration" should be *No. On the second page, if you want to use a Mail Router, it should be the name of the IP address for the mail router, "Firewall" should be *Yes if there is a mail router defined, and "Process all mail through MSF" should be *No. On the fourth page, check for Real Time Black Hole List (this can cause delays in outbound and inbound e-mail), and check the Filter Mail for Virus (this can cause 'lost' e-mail). The Allow Relayed Mail parameter should not be *All. *All is an 'Open Relay' and is a major SPAM exposure. The Allow Relayed Mail parameter should be *None if you will only be using the iSeries to originate the e-mail (no clients sending mail), or *POPWDW if hosting POP3 mail clients, or *List if you want to include specific IP addresses for your clients. On the last page, last parameter, "Forwarding Mailhub Server" should be the same as the mail router from page 2.

J.

Verify that the exit point programs are registered for SMTP and QMSF:

Issue the WRKREGINF command, and press Enter. Go down to QIBM_QZMFMSF_*. Compare the registered exit programs for each exit point with a working system if possible. If any are missing, refer to Rochester Support Center knowledgebase document 545506546, How to Register Missing Exit Point Programs Needed by QMSF and SMTP: [cid:image001.gif@01CEFCBC.47A68670] <notes://SCDBSRV1/8625680A007CA5C6/00E42B791A3DAB7B862565C9004EC1AF/09AD8DD28476928A8625768E006E1730> .

K.

Check for bindings:

You can check the bindings by looking at the SMTP properties with iSeries navigator or by using the STRPDM command and pressing Enter, then selecting Option 2 Work with Objects. Use the following information:

Library: QUSRSYS
Object Name: QATMI*
Type: *ALL
Attribute: *ALL

and press Enter.

Select 12 on QATMIFCLST, and press Enter. To check the client binding, select 5 on CLNTBNDIP. To check the server binding, select 5 on SVRBNDIP. To make changes to the bindings, issue the RMVSMTPLE and ADDSMTPLE commands.


Related information
o

For information on Authentication and SSL configuration for SMTP, refer to Rochester Support Center knowledgebase document 519611543, Configuring SMTP Authentication: [cid:image001.gif@01CEFCBC.47A68670] <notes://SCDBSRV1/8625680A007CA5C6/00E42B791A3DAB7B862565C9004EC1AF/109F0D47F8446AB986257586004A316C> .

o

For information on Dual Stack configuration, refer to Rochester Support Center knowledgebase document 522178744, Setting up Dual Stack for SMTP to Run Native and Domino SMTP: [cid:image001.gif@01CEFCBC.47A68670] <notes://SCDBSRV1/8625680A007CA5C6/00E42B791A3DAB7B862565C9004EC1AF/81DECF437806C711862575A00043693A> .

o

For information on SMTP and QMSF tracing, refer to Rochester Support Center knowledgebase document 542565415, Traces Needed to Debug SMTP and MSF When E-Mail Fails: [cid:image001.gif@01CEFCBC.47A68670] <notes://SCDBSRV1/8625680A007CA5C6/00E42B791A3DAB7B862565C9004EC1AF/1453CD0A9577C07A862576700071F1E4> .

o

For information on Forwarding e-mail, refer to Rochester Support Center knowledgebase document 533286549, Forwarding Internet Mail to Another E-Mail Address: [cid:image001.gif@01CEFCBC.47A68670] <notes://SCDBSRV1/8625680A007CA5C6/00E42B791A3DAB7B862565C9004EC1AF/2D872EE2D271EBF48625761100628E62> .

o

For information on creating a non-delivery mailbox, refer to Rochester Support Center knowledgebase document 28281855, Creating a Nondelivery Mail Box: [cid:image001.gif@01CEFCBC.47A68670] <notes://SCDBSRV1/8625680A007CA5C6/00E42B791A3DAB7B862565C9004EC1AF/A3D3D957A941F18486256C48005412CA> .






-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Thursday, December 19, 2013 12:46 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: SNDDST not working after V7 upgrade





Hi Folks, I’m still having issues with SNDDST but...We can use usrprf QSECOFR to successfully snddst to our home email address (aol, etc.) but QSECOFR still not SNDDST to our internal outlook.



Thanks for the info on this and here’s the answers to the questions that you’ve raised in this thread;

QALWOBJRST is always *ALL on our systems

The consultant who did the work saved and restored from a SAV21 and that brought us up to V6 and then upgraded to V7. He said he did an unload reload to a different system, then upgrade.

Should I try to get any more info than that?

Should I try to get any more info than that?

Should I try to get any more info than that?

Regarding /QTCPTMM…I’m assuming that it was saved during the sav21 and restored when the rst of the SAV21 was done…right?...and here’s how it is now;



Work with Object Links



Directory . . . . : /QTCPTMM



Type options, press Enter.

2=Edit 3=Copy 4=Remove 5=Display 7=Rename 8=Display attributes

11=Change current directory ...



Opt Object link Type Attribute Text

. DIR

.. DIR

ATTABOX DIR

DSN DIR

ENCODE DIR

FTRFILES DIR

LOCKBOX DIR

MAIL DIR

SMTPBOX DIR

TMP DIR







Any other ideas?



Thanks, Frank











-----Original Message-----

From: CRPence <CRPbottle@xxxxxxxxx<mailto:CRPbottle@xxxxxxxxx>>

To: midrange-l <midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>>

Sent: Thu, Dec 19, 2013 11:24 am

Subject: Re: SNDDST not working after V7 upgrade





On 19-Dec-2013 05:57 -0800, rob@xxxxxxxxx<mailto:rob@xxxxxxxxx> wrote:

Paul,



Maybe you're right...

http://www.ibm.com/support/docview.wss?uid=nas27a11ff9db49db7f586256ea900714552

http://www.ibm.com/support/docview.wss?uid=nas28f129bd920f1fd4a86256eb0003cadcc



FWiW [for the archives, per the APARs\links will surely be purged oon enough] those v5r3 APARs, SE16086 and SE15891 [one a sysroute\copy f the other], suggest that the directories _under_ the /QTCPTMM are not aved, *except* its MAIL directory; i.e. not an issue with the Can Be aved (*ALWSAV) attribute of that directory itself, but some\most of its ubdirectories.

SE15891 - TCPIP-SMTP-MSGCPFA09C CPFA09C WHEN SENDING MAIL AFTER A FULL YSTEM SAVE AND RESTORE. DIRECTORIES FOR QTCPTMM ARE MISSING.

E16086 - TCPIP-SMTP-MSGCPFA09C CPFA09C WHEN SENDING MAIL AFTER A FULL ...

Problem Summary_

System SAV/RST does not save QTCPTMM directories, except for MAIL. All thers are suppose to be recreated once touched. This is not happening.

SF doesn't have authority.

..."

But with regard to the scenario as described by the OP whereby "the NDDST command runs with no error but does not send to the email ddress", that issue from the APARs seems unlikely to be an origin.

urely the OP would be happier to have such an obvious failure :-) And hat those directories could be the origin for the issue for the OP is urther diminished in likelihood, by the fact that the side effects from he unsaved subdirectories were to have been _resolved by_ the PTFs for hose APARs back in v5r3m0. The changes\fixes were to ensure that the issing directories would be automatically created by POP and SMTP, ather than only by MSF [server startups presumably], if\when the issing directories condition was detected, and that the owner and uthorities for those since-created directories would be properly stablished, irrespective the user [QMSF or QTCP] established for the rocess as provided in changes to the service program QTCP/QTMSUTL.

--

egards, Chuck

-

his is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list o post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> o subscribe, unsubscribe, or change list options,

isit: http://lists.midrange.com/mailman/listinfo/midrange-l

r email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> efore posting, please take a moment to review the archives t http://archive.midrange.com/midrange-l.



--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,

visit: http://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact