Hola, perd�n pero olvid� el mail de quien estaba presentando un problema de
CPU con el SMTP.
Favor verificar los sgtes. documentos "p�blicos":
#24965728 y #20910904, en la base de conocimientos de IBM.
Document Title
SMTP Mail is Looping on the iSeries
Document Description
High CPU on both the QTSMTPCLTP and QTSMTPSRVP jobs indicate that mail is
looping on the iSeries. This can occur for the following reasons:
o Mail may loop because the iSeries is trying to deliver a nondelivery
message and cannot send it back to the originator. When this occurs, the
iSeries builds its own NONDELIVERY message to [EMAIL PROTECTED] of
the iSeries. If the fully qualified name (host.domain from CFGTCP,
Option 12) of the iSeries is not in the Local Host Table, mail loops
between the server and the client. Adding the fully qualified name to
the Local Host Table (CFGTCP, Option 10) eliminates looping of mail.
Nondelivery messages can be retained if a NONDELIVERY profile is
created. You can keep these messages if you create a NONDELIVERY profile
using the following steps.
- On an OS/400 command line, type the following:
CRTUSRRPRF USRID 'NONDELIVER'
Press the Enter key.
- On the OS/400 command line, type the following:
ADDDIRE USRID(NONDELIV RCHASBDS) USRD('NONDELIVERY MAIL') +
USER(NONDELIVER)
Press the Enter key.
- Run the WRKDIRE command for NONDELIVER, and select Option 2 to change.
Page down four times to the following:
Mail Service Level - 2
Preferred Address - 3
- Press F19.
- SMTP user ID - NONDELIVERY
- SMTP DOMAIN - HOST.DOMAIN (Fully qualified name from Option 12 of
CFGTCP command.)
-Make sure the fully qualified name is in the LHT associated with the IP
address of the OS/400 system.
o Similarly, mail loops on the iSeries if the CHGSMTPA Mail Router
parameter is configured to be the name of the iSeries.
o Recently it has been discovered that several domains have publicly
registered their MX records to the A record of loopback. For additional
information, refer to Rochester Support Center knowledgebase document
20910904.
If the problem persists, Rochester Support Center for further assistance.
*************
Problem:
There is high CPU on client and server jobs for SMTP.
Action Taken:
NETSTAT Option 3 found all SMTP connections connecting to loopback. Flight
recorders were run and determined '[EMAIL PROTECTED]' over and over again in
QTSMTPCLT and QTSMTPSVR. PINGed 'me.com' and came back with a
216.200.197.161. This was added to the local host table associated with
me.com, and SMTP is no longer looping.
me.com appears to be pointing to 0.0.0.0 for an MX record. This problem can
be easily re-created on test systems. When an MX record of all zeros is
received, we will connect with loopback.
Saludos/Atte...
J@
Jos� Antonio Roa C.
_____________________________________________________
Forum.HELP400 es un servicio m�s de NEWS/400.
� Publicaciones Help400, S.L. - Todos los derechos reservados
http://www.help400.es
_____________________________________________________
Para darte de baja, env�a el mensaje resultante de pulsar
mailto:[EMAIL PROTECTED]?body=LEAVE
