Re: Analyzing output of TRCTCPAPP APP(*SMTPCLT)

The IBM i SMTP client will try numerous times to connect with and deliver
email to an endpoint, or to a relay-point, depending on whether it was
configured to be a relay or to deliver directly to endpoints. IBM i
applications that send mail don't wait for the SMTP client to complete its
processing, so there is no way for them to log downstream errors. If a
relay or endpoint is unreachable after a number of retries, the SMTP client
will stop trying.

An SMTP client trace will capture the protocol used as it attempts to
communicate with a relay or endpoint. But the trace is so verbose, and the
things that get spooled are so different depending on the endpoint that the
SMTP client is communicating with, that it would be terribly difficult to
digest it.

I wonder if output from the WRKSMTPEMM command might be more helpful. The
command reference in the Knowledge Center suggests that it can reference an
*ERR queue.

If WRKSMTPEMM doesn't work out for you, then I'd recommend taking a look at
a different email client.






On Tue, Jan 16, 2018 at 9:16 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

I am at IBM i 7.3.
I am using
CHGSMTPA DIRTYPE(*SMTP)
which kills using the email journals to troubleshoot.
It is recommended that I use TRCTCPAPP APP(*SMTPCLT) to track when
things
go awry.
Are there some string samples to scan the resultant spool file for
failures?
The developers find it tough to say exactly when a failure occurred.
Normally an email failure is used as an excuse as to why someone is late
paying and that can be rather long after the failure occurred. This is
why I am trying to be proactive on the failures.
Yes, I am aware there are alternatives to using IBM's smtp and while I
realize that some need opportunities to put out a shameless plug for
their
products I'd rather continue to work on this if for no other reason than
"because I said so".

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
[1]http://www.dekko.com

References

Visible links
1. http://www.dekko.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD