Re: Hunting email origins

["sjl" <sjl_abc@xxxxxxxxxxx>]

Chris -

Perhaps a search of your Control Language source code for the SNDDST command 
or use PRTCMDUSG CMD(SNDDST) to analyze the program objects will help narrow 
it down to the program which is sending the emails.

- sjl


Chris wrote:
Our email administrator (non iSeries) has come to me with a problem: There 
is some process on our iSeries that is spitting out emails every few minutes 
to a fat-  fingered address. I'm new to the system and have not found 
anything in the usual places (job scheduler, Robot, etc). The iSeries isn't 
running the SMTP service, so I can't check any logging from that side.

In order to track this down, I was thinking of doing a communications trace 
on our iSeries. I realize that the trace may or may not give me the actual 
job that's producing the emails, but I'm hoping that I can get pointed in 
the right direction based on the content of the email. However, it's a 
production system and I've never done a trace before, so I wanted to get a 
sense of the impact that this would have on the system. Will a trace of all 
traffic destined to port 25 of a singe IP address have adverse effects on 
system performance? If so, are there less detrimental ways of finding out 
where these emails are coming from?