Same here - we get high CPU on SMTP when there are bad emails in a large batch we send. Sometimes it clears up on its own., sometimes we end and restart SMTP and MSF and it ends

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Monday, March 05, 2012 1:17 PM
To: Midrange Systems Technical Discussion
Subject: Re: High CPU usage

Jeff,

We have seen this happen on client systems. The job in question is the
SMTP server. This could be an indication that a spammer has locked on to
your system and is routing spam through you. Or, it could be that an
email has been sent through your system that has a bad domain name
associated with it. We've seen this drive up SMTP utilization too.

SMTP journalling should help you.

Rich Loeber - @richloeber
Kisco Information Systems
[1]http://www.kisco.com
SDG

--------------------------------------------------------------------------

On 3/5/2012 1:08 PM, Jeff Young wrote:

All,
I have a client that is experiencing a high (for them) CPU usage ranging from 40 to 60 %.
They have identified a system job named QTSMTPTCTP as a possible cause.
Does anyone know what this job does? It runs in QSYSWRK and there are about 8 jobs of that name active.

Thanks,

References

Visible links
1. http://www.kisco.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: 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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].