RE: SMTP V5R1 - QTSMTPSRVP and QTSMTPCLTP

Dennis -

If the system should not be relaying mail, make sure CHGSMTPA
ALWRLY(*NONE) is set.  It's possible you're being used unwittingly as an
email relay for a spammer.

We don't do email on our 400s so perhaps others who do can speak to this
better than I.

- John

-----Original Message-----
From: Dennis Lovelady [mailto:dlovelady@xxxxxxxx] 
Sent: Thursday, June 26, 2003 8:05 AM
To: Midrange Systems Technical Discussion
Subject: SMTP V5R1 - QTSMTPSRVP and QTSMTPCLTP


Hi, Midrangers:

On our V5R1 Development system, we've started to notice that the jobs
QTSMTPSRVP and QTSMTPCLTP are consuming, between them, about 50% to 60%
of the CPU.  We're not doing any major SMTP mail (that we're aware of,
anyway), and consequently do not understand why these jobs may be
consuming so much resource.

The next three jobs down in order of CPU consumption are:
   AMGR         QNOTES      BCI     3.6
   EVENT        QNOTES      BCI     1.3
   SERVER       QNOTES      BCI     1.2

Rather suspiciously also indicating some sort of e-mail activity, I
*THINK* but we're also not running any agents we're aware of..... This
particular NOTES instance has been installed (long ago) for support of a
proposed application, but it's not in place.

Can any of you shed any light on this anomoly?

Thanks,
Dennis


_______________________________________________
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This e-mail is for the use of the intended recipient(s) only.  If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not use, disclose 
or distribute this e-mail without the author's prior permission.  We have taken 
precautions to minimize the risk of transmitting software viruses, but we 
advise you to carry out your own virus checks on any attachment to this 
message.  We cannot accept liability for any loss or damage caused by software 
viruses.