CCMS Monitor for SMTP-Service via ICM SMTP-Plugin

Dear all,
we configured our SAP System for sending emails with the help of transaction SCOT. We are using the SMTP-Plugin brought in by the ICM. Everything works fine. Now we want to report how many emails are sent through that connection. For that we want to connect the SMTP-Plugin to the CCMS. Since I havn't found any documentation of that (the existing documentation is discussing how to configure an ordinary SCOT connection for CCMS), I'd like to ask somebody for help.
thanks in advance
best regards
Thomas Wetzler

http://www.spamhaus.org says:
Mail servers only run spam filters such as Spamhaus PBL on port 25, so if you find you are being blocked by the PBL when you try to send mail to your mail server that means you are not communicating with the mail server on the 'authenticated' port 587 but you're still on port 25. This means your 'SMTP Authentication' is not working correctly.
http://wiki.gandi.net/en/mail/standard-settings#smtp-account says:
SMTP Account
Name server : mail.gandi.net
Port : 25, 465 (with SSL) or 587 (try one or the other)
TLS or SSL: yes
SMTP Authentication : yes, using the same settings as for the POP / IMAP account
I was trying to use the same settings I have used for several years with Thunderbird and Apple Mail, ie SSL on port 465.
Is there something wrong with my settings which could be preventing mailx from using port 465?
A few debug tips would be appreciated.
Your link causes me to ask: Does the mailx on Leopard support SMTP directly?

Similar Messages

Monitoring for Cisco Service Portal on WebLogic

Hello Support Community,
Our team is looking at enabling monitoring for Cisco Service Portal 9.4 + patch 4d on a WebLogic Server 10.3.5.0 environment.
We currently have this setup:
RequestCenter is active/active on HostA & HostB
RequestCenter is accessed via VirtualHostA (reqctr_cluster)
ServiceLink is active/passive on HostC & HostD
ServiceLink is accessed via VirtualHostB (svclnk-cluster)
What is the recommended way to monitor RequestCenter and ServiceLink in this WebLogic environment?
Do let me know if a TAC case needs to be opened.
The physical architecture diagram is available upon request.
Thanks
Mark Rameshwar
San Jose, CA

Hello Support Community,
Our team is looking at enabling monitoring for Cisco Service Portal 9.4 + patch 4d on a WebLogic Server 10.3.5.0 environment.
We currently have this setup:
RequestCenter is active/active on HostA & HostB
RequestCenter is accessed via VirtualHostA (reqctr_cluster)
ServiceLink is active/passive on HostC & HostD
ServiceLink is accessed via VirtualHostB (svclnk-cluster)
What is the recommended way to monitor RequestCenter and ServiceLink in this WebLogic environment?
Do let me know if a TAC case needs to be opened.
The physical architecture diagram is available upon request.
Thanks
Mark Rameshwar
San Jose, CA

CCMS monitoring for adapter engine

Hi,
We have configured CCMS monitoring for Adapter Engine for our client.
In RZ20 im able to see the alerts come up,with the default data that the system provides.
1. I need to send a mail when the alert is triggerred, but if I try to set the autoreaction method, it is greyed out and I get a info saying that the adpter engine node cannot be changed. How do I get over this?
2. Incase im able to set the autoreaction method , I want to send additional information like communication channel name etc in the alert message. How can I change the text in the alert email?
Thanks
Shakthi

Hello!
Please check the blog entry below
Configuration for forwarding Alerts as Emails
Configuration for forwarding Alerts as Emails

CCMS monitoring for Queues(SMQ1/SMQ2)

Hi,
How do we monitor Queues(SMQ1/SMQ2) in CCMS. My requirement is to monitor Queues(SMQ1/SMQ2) in CCMS based on the Queue name. I want to create different nodes in CCMS and I want queue name falling under certain criteria should come and sit in the respective node of CCMS.
Means queue with name High_priority should come n sit under node say Test1, queue name with medium_priority should come n sit under node say Test2 and queue name with medium_priority should come n sit under node say Test3.
Is it possible to do so.

Hello,
also for queue monitoring the easier and more flexible way to monitor is via Business Process Monitoring. The configuration is easier than CCMS where you have to use transaction RZ21 and need to transport objects. And the qRFC monitoring is more flexible than in the CCMS. Basically all customers knowing both standard CCMS qRFC monitoring and qRFC monitoring in BPMon chose the later or exchange their existing CCMS monitoring by BPMon.
See also the SDN blog /people/johannes.fleig/blog/2008/06/11/new-business-process-monitoring-functionalities-in-sap-solution-manager-150-qrfc-monitoring
and check out the Interface Monitoring Setup Guide under http://service.sap.com/bpm > Media Library > Technical Information.
Best Regards
Volker
Edited by: Volker von Gloeden on Jul 2, 2010 4:48 PM

CCMS Monitoring for specific tcodes

Hello All,
Hope someone can help me out. I have a list of tcodes for a daily check which are:
SM21
ST22
SM37
SM50
DB02
I have configured CCMS correctly and its working to send out alerts via email but only for ST22. I can't seem to find the right MTE class to use for any of the rest listed above. Does anyone know which class I should be using or point me in the direction of how to include these?
Any help would be greatly appreciated
Thanks
Stephanie

Hi Faisal,
Here's an approach to answering the question "does CCMS monitor X". It's not perfect but it will help you find a starting point:
- think of what you want to monitor, not in terms of transaction codes ("how do I monitor transaction SM13") but in terms of the functionality you want to monitor ("how do I detect failed updates?")
- in RZ20, open SAP CCMS Technical Expert Monitors --> All Monitoring Contexts.
- Expand the whole tree with the "Expand all" button. This will show you the entire tree of everything that is currently monitored in your system
- do a text search of the tree for useful keywords (for example "Update"). In this case you will find several possibilities including AbapErrorInUpdate, which I think is the one that you want
- highlight the node and press Properties to get the MTE class, in this case R3AbapErrorInUpdate
There is no exhaustive list anywhere that I can find, that lists every possible thing that CCMS monitors. But the approach above will catch most scenarios. You will come up short in a few scenarios where optional monitoring components are not enabled by default (for example, SAPConnect monitors).
Also be forewarned that often CCMS will not monitor exactly what you want, and you'll have to find ways to monitor around the edges of your true intention. For example, there is no monitor for determining if a background job ran between midnight and 02:00, but you can monitor delay and runtime which can come close to what you want. Part of the art of CCMS monitoring is finding the right combination of monitors that come closest to achieving your objective.
Good luck and happy monitoring,
Jon

CCMS monitoring for SAPconnect based on Error Message Numbers

Hi,
We are trying to use the CCMS monitoring to produce alerts for SAPconnect based specific Error Message Numbers for emails for example, however the monitoring function or data collection method for SAPconnect (BCOMAL_SXDS) does not provide that level of granularity. Has anybody faced this same problem and can provide a recommendation for this?
Thanks,
Javier

Hello,
You can see the message details in SE91.
In FI, you can control the message number in OBA5. Normally message numbers are issued like this
AA165
First two digits (alpha) is called application area next digits are called message number.
Sometimes, you may not be able to see the messages in OBA5, in such case you need to go to OBMSG transaction code and include the message number to your application area, then you need to come to back to OBA5 to make it information / warning / switch off / error (as the case may be)
Regards,
Ravi

CCMS monitoring for DB2/400 database backup.

Hi,
sap on iseries experts,
We need a good monitoring for the alerts from DB2/400 database backup failure with CCMS for a solution manager management.
Actually I don,t see a specific node (or MTE class) inside CCMS for this alert;
But DB12 display well the daily backup status . . . . . . . .
Can anybody help me ?
Kind Regards
Fabio

Hi all,
I'm searching also for such an possibilty.
When running Oracle there is following MTE:
RZ20 -> SAP CCMS Technical Expert Monitors -> All Monitoring Contexts -> Oracle -> Backup/restore -> Backup status -> Last succ
Does anybody know a method to monitor the backup with SAP on Iseries?
Tobias

CCMS Monitoring for Average HTTP response time

Hi guys ,
Is it possible to monitor Av. response time for HTTP(this is based on ST03) using CCMS ?
Thanks in advance
George

hi
As per my understanding you tried to view the responsetime comp as same like in sto3 by ccms, the way as below, RZ20-> SAP CCMS montior templates- >Entiresystem-><sid>->application server -><server>R3 services -> DIalog you can get all the response time as same in the ST03.
else in otherway if you looking for monitoring Java and webdynpro, you can do this by GRMG.chk this for to knw http://help.sap.com/saphelp_nwpi71/helpdata/en/45/4ee37fea5917eae10000000a155369/content.htm|http://help.sap.com/saphelp_nwpi71/helpdata/en/45/4ee37fea5917eae10000000a155369/content.htm]
for configuration,[GRMG-config guide|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/106a4d88-2a36-2c10-549b-dc549d00b8b9?quicklink=index&overridelayout=true]
chk and update
jansi

Ccms alert for RFC service

I have a simple task that i was told to monitor.
There is RFC to a remote non-sap system that is setup in SM59. This non-sap system some times stops responding. I would like to setup a CCMS alert specific to this RFC. I have tried creating all kinds of alerts and methods but have not been successful.
Does anyone have a simple steps on how I go about creating a simple alert specifically monitoring a particular RFC connection?
I have looked at sdn ccms page and help on ccms from sap help, but they have not 'helped'.

HI
For any application server with a single instance,whenever it would stop working, would mean that the message server has gone down.In such a case, how is a system suppose to respond?
Do correct me if I am wrong here.
Regards
Chen

CCMS monitoring for CIF-queues

Hello,
we would like to monitor the number of queue entries in the qRFC in/outbound queues (smq1/smq2). The number of queue entries should be checked every 15 minutes.
We then would like to store the data in the central performance history to get some kind of a load profile for the queues.
We could not find a data collector in the ccms or st03n.
Do you know if there is something available to solve the issue?
Thanks in advance,
Matthias

Hi Matthias,
The smq1/smq2 entries changes randomly. So the work around can be
Schedule report RSTRFCM1 for smq1 & RSTRFCM3 for smq2 after every 15mins.
Then from sm37 for those job --> spool tab
In this you can get Display of Queue entries.
Award Points if helpful

Can the B520 be used as an external monitor for a macbook via the HDMI in?

Hi,
I'm very happy with the Lenovo, but it looks like our family will be acquiring a macbook in the near future. Can I use HDMI in on the Lenovo B520 so that it becomes an external display for an apple computer?
Thanks for the help.

Thank you very much for the help. Now if I could only figure out why the Lenovo B520 doesn't see my apple airport extreme network anymore. I guess I'll have to post separately for that one. It was incredibly fast and now it doesn't connect at all. Thanks for the help on this. I need a mac for access to iBooks Author. Silly (and expensive), but true. Thanks again!

CCMS Monitor to Pager for Failed Background Jobs

Hello Experts,
I am currently leveraging Central CCMS monitoring to alert us via email whenever a background job fails in production using the MTE Class R3BPServerSpecAbortedJobs.
I am trying to find a way that I can tweak the monitor to alert me ONLY when specific background jobs fail.
We want this alert to notify the oncall pager only when a handful of critical jobs fail. Does anyone know how I can delimit this MTE?
For example, we will be creating jobs that begin with Z_ALERT* that I will tie to an auto-react method that will email a pager.
Thanks in advance.
Bill

Hi Sundara.
From following link, you can download step by step setup information.
So please check following documents.
http://www.service.sap.com/bpm
=>Media Library=>Technical Information
=>1. Business Process Monitoring - Setup Roadmap
=>2. Setup Guide - Business Process Monitoring
Before you start setup, I recommend you to check
SAP Notes 521820 to ensure whether you already fulfill
prerequestions.
Basically what you have to do is following.
1. Describe your business process under following area.
   (T-CD DSWP =>Solution Landscape =>Solution landscape maintenance)
2. Setup BPMon session.
   (T-CD DSWP =>Operation Setup => Solution Monitoring =>
    Business Process Monitoring)
   in BPMon session, select job monitoring. And define background
   job that you want to monitor.
   In BPMon job monitoring, you can monitor, cancel, delay, duration,
   unexpected parallelization, also job log and so on.
I hope this information help you.
Best Regards
Keiji Mishima

Missing "SAP XI Adapter engine" in CCMS Monitor

Dear all,
we try to configure PI CCMS monitor but we can't find the subtree "SAP XI Adapter engine " in Visual admin.
In detail:
the subtree "SAP XI Adapter engine "is not displayed in Visual administrato under
server->service->monitoring->Monitor tree ->Root application .
So we have set to true the value "CCMSEnabled" of seervice "SAP XI AF core" , and we have restarted the instance.
After the restart i DO NOT find the "SAP XI Adapter engine " in
SAP NetWeaver Administrator,
'System Management' -> 'Monitoring' -> 'Java System Reports' -> 'Reports'. From the dropdown list 'Report' choose 'Monitor Browser', and display all monitors
So I can't activate the monitor.
and if the subtree is not present , i can't see the MTE in "SAP XI Adapter engine " RZ20.
Additional info:
- In RZ20 I have my system under SAP J2ee Monitor template->All system
but the MTE "J2EE Applications" is grayed.
- In file application.xml under /usr/sap/ccms/XIT_10/j2ee<server0> i do not find the tag:
<app name="application sap.com/com.sap.aii.af.app">
<node>\XIT\XIT 10 Appl .... sp30t0\SAP XI Adapter Engine</node>
</app>
I think this is the correct procedure that we have done in other different landscape whithout problems.
Is there something else to check ?
I've alredy checked following Blogs
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
/people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
Thanks in advance
Steven

Hi Sekhar,
I am using PI 7.0 instead so I have followed the instruction in (http://help.sap.com/saphelp_nw70/helpdata/en/e5/5d1741b393f26fe10000000a1550b0/frameset.htm) instead.
The problem is, Adapter Engine is still not listed as one of the application avaialble for Monitoring in Visual Admin even though the SAP XI AF Core has definitely been set with CCMSEnabled = true.
Any further suggestions?
Thanks,
Wi

404 error while accessing sicf services via apache reverse proxy

Hi,
I set up an reverse proxy with apache 2.2 and try to access SICF Services via this proxy. I got the following error message from the sap system:
Service cannot be reached
The termination occurred in system SMP with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:NE-SSMP01_SMP_00-v:0-s:404-r:Notfound
When I access J2EE services via the proxy it works.
Is there any configuration which have to be done in the ABAP Stack for accessing Services via the proxy server?
For tests I tried to access the simple ping service ( /default_host/sap/public/ )
Thanks and best regards,
Tim

Hi Oliver,
I allready checked the SDN posts for the reverse proxy. Maybe I missed something.
The ProxyPreserveHost is on.
I redirect to the ICM. I only redirected to the J2EE for tests. This worked by the way withe the same conifiguration.
Here is my apache config:
VirtualHost *:5443>
        ServerName      domain.com
        ServerAdmin     test.de
     ProxyPreserveHost On
     #ProxyVia On
     #AllowEncodedSlashes On
Rewrite Rules
- forward sap/public/ping?sap-client=001 -> Test Ping
- Passthrough /sap/public/ping/*
- Redirect any other URL -> Test Ping
        RewriteEngine On
        RewriteRule     ^/sap/public/ping?sap-client=001$     /sap/public/ping?sap-client=001          [R,L]
     RewriteRule     ^/sap/public/(.*)                     /sap/public/$1                    [PT,L]
     RewriteRule (.*)                               /sap/public/ping?sap-client=001          [R,L]
     RewriteLog logs/rewrite_SMP.log
     RewriteLogLevel 3
Reverse Proxy to
- Disable Forward Proxy
- Allow Connections from All
- Reverse Mapping for 302 Response
- Forward / Requests to domain.com:8000
        ProxyRequests Off
        <Proxy *>
                AddDefaultCharset off
                Order Allow,Deny
                Allow from all
        </Proxy>
Forward Rules
     ProxyPass             /sap/public/ping          http://domain.com:8000/sap/public/ping?sap-client=001
     ProxyPassReverse      /                    http://domain.com:8000/
</VirtualHost>
Best regards,
Tim

Guidelines for Health Monitoring for TimesTen

This document provides some guidance on monitoring the health of a TimesTen
datastore. Information is provided on monitoring the health of the
datastore itself, and on monitoring the health of replication.
There are two basic mechanisms for monitoring TimesTen:
1. Reactive - monitor for alerts either via SNMP traps (preferred) or
by scanning the Timesten daemon log (very difficult) and reacting
to problms as they occur.
2. Proactive - probe TimesTen periodically and react if problems, or
potential problems, are detected.
This document focusses on the second (proactive) approach.
First, some basic recommendations and guidelines relating to monitoring
TimesTen:
1. Monitoring should be implemented as a separate process which maintains
a persistent connection to TimesTen. Monitoring schemes (typically based
on scripts) that open a connection each time they check TimesTen impose
an unnecessary and undesireable loading on the system and are discouraged.
2. Many aspects of monitoring are 'stateful'. They require periodic
sampling of some metric maintained by TimesTen and comparing its
value with the previous sample. This is another reason why a separate
process with a persistent connection is desireable.
3. A good monitoring implementation will be configurable since the values
used for some of the chcks may depend on e.g. the TimesTen configuration
in use or the workload being handled.
MONITORING THE HEALTH OF A DATASTORE
====================================
At the simples level, this can be achieved by performing a simple SELECT
against one of the system tables. The recommended table to use is the
SYS.MONITOR table. If this SELECT returns within a short time then the
datastore can be considered basically healthy.
If the SELECT does not return within a short time then the datastroe is
stuck in a low level hang situation (incredibly unlikely and very serious).
More likely, the SELECT may return an error such as 994 or 846 indicating
that the datastore has crashed (again very unlikely, but possible).
A slightly more sophisticated version would also include an update to a
row in a dummy table. This would ensure that the datastore is also capable
of performing updates. This is important since if the filesystem holding
the trsnaction logs becomes full the datastore may start to refuse write
operations while still allowing reads.
Now, the SYS.MONITOR table contains many useful operational metrics. A more
sphisticated monitoring scheme could sample some of these metrics and
compute the delta between subsequent samples, raising an alert if the
delta exceeds some (configurable) threshold.
Some examples of metrics that could be handled in this way are:
PERM_IN_USE_SIZE and PERM_IN_USE_HIGH_WATER compared to PERM_ALLOCATED_SIZE
(to detect if datastore is in danger of becoming full).
TEMP_IN_USE_SIZE and TEMP_IN_USE_HIGH_WATER compared to TEMP_ALLOCATED_SIZE
(ditto for temp area).
XACT_ROLLBACKS - excessive rollbacks are a sign of excessive database
contention or application logic problems.
DEADLOCKS - as for XACT_ROLLBACKS.
LOCK_TIMEOUTS - excessive lock timeouts usually indicate high levels of
contention and/or application logic problems.
CMD_PREPARES & CMD_REPREPARES - it is very important for performance that
applications use parameterised SQL statements that they prepare just once
and then execute many times. If these metrics are continuously increasing
then this points to bad application programming which will be hurting
performance.
CMD_TEMP_INDEXES - if this value is increasing then the optimiser is
comntinually creating temporary indices to process certain queries. This
is usually a serious performance problem and indicates a missing index.
LOG_BUFFER_WAITS - of this value is increasing over timne this indicates
inadequate logging capacity. Yiou may need to increase the size of the
datastore log buffer (LogBuffSize) and log file size (LogFileSize). If that
does not alleviate the problem you may need to change your disk layout or
even obtain a higher performance storage subsystem.
LOG_FS_READS - this indicates an inefficieny in 'log snoop' processing as
performed by replication and the XLA/JMS API. To alleviate this you should
try increasing LogBuffSize and LogFileSize.
Checking these metrics is of course optional and not necessary for a basic
healthy/failed decision but if you do check them then you will detect more
subtle problems in advance and be able to take remedial action.
MONITORING THE HEALTH OF REPLICATION
====================================
This is a little more complex but is vital to achieve a robust and reliable
system. ideally, monitorting should be implemented at both datstores, the
active and the standby. There are many more failure modes possible for
a replicated system than for a standalone datastore and it is not possible
to ennumerate them all here. However the information provided here should
be sufficient to form the basis of a robist monitoring scheme.
Monitoring replication at the ACTIVE datastore
1.     CALL ttDataStoreStatus() and check result set;
If no connections with type 'replication' exists, conclude that
replication agents are stopped, restart the agents and skip
next steps.
It is assumed here that the replication start policy is 'norestart'.
An alarm about unstable replication agents should be raised
if this is Nth restart in M seconds (N and M are configuration parameters).
The alarm can later be cleared when the agents stayed alive K
seconds (K is configuration parameter).
2.     CALL ttReplicationStatus() and check result set;
This returns a row for every replication peer for this datastore.
If the pState is not 'start' for any peer, raise an alarm about paused or
stopped replication and skip rest of the steps.
It is assumed that master cannot help the fact that state is not
'start'. An operator may have stopped/paused the replication or
TimesTen stopped the replication because of fail threshold
strategy. In former case the operator hopefully starts the replication
sooner or later (of course, after that TimesTen may stop it again
because of the fail threshold strategy). In latter case the standby
side monitor process should recognise the fact and duplicate the data
store with setMasterRepStart-option which sets state back to 'start'.
If for any peer, lastMsg > MAX (MAX is a configuration parameter), raise
an alarm for potential communication problems.
Note that if replication is idle (nothing to replicate), or there is
very little replication traffic, the value for lastMsg may become as
high as 60 seconds without indicating any problem. The test logic
should cater for this (i.e. MAX must be > 60 seconds).
3.     CALL ttBookmark();
Compute the holdLSN delta between the values from this call and the
previous call and if the delta is greater than maximum allowed
(configuration parameter), raise an alarm about standby
that is too far behind. Continue to next step.
Notice that maximum delta should be less than FAILTHRESHOLD * logSize.
4.     CALL ttRepSyncSubscriberStatus(datastore, host);
This step is only needed if you are using RETURN RECEIPT or RETURN TWOSAFE
with the optional DISABLE RETURN feature.
If disabled is 1, raise an alarm for disabled return service.
Continue to next step. If RESUME RETURN policy is not enabled we could,
of course, try to enable return service again (especially when DURABLE
COMMIT is OFF).
There should be no reason to reject TimesTen own mechanisms that
control return service. Thus, no other actions for disabled return
service.
Monitoring replication at the STANDBY datastore
1.     CALL ttDataStoreStatus();
If no connections with type 'replication' exists, conclude that
replication agents are stopped, restart the agents and skip
next steps.
It is assumed that replication start policy is 'norestart'.
An alarm about unstable replication agents should be raised
if this is Nth restart in M seconds (N and M are configuration parameters).
The alarm can later be cleared when the agents stayed alive K
seconds (K is configuration parameter).
2.     Call SQLGetInfo(...,TT_REPLICATION_INVALID,...);
If the status is 1, this indicates that the active store has marked this store
as failed due to it being too far out of sync due to log FAILTHRESHOLD.
Start recovery actions by destroying the datastore and recreating via a
'duplicate' operation from the active.
3.     Check 'timerecv' value for relevant row in TTREP.REPPEERS
If (timerecv - previous timerecv) > MAX (MAX is a configuration parameter),
raise an alarm for potential communication problems.
You can determine the correct row in TTREP.REPPEERS by first getting the
correct TT_STORE_ID value from TTREP.TTSTORES based on the values in
HOST_NAME and TT_STORE_NAME (you want the id corresponding to the active
store) and then using that to query TTREP.REPPEERS (you can use a join if
you like).
The recovery actions that should be taken in the event of a problem with
replication depend on several factors:
1. The application requirements
2. The type of replication configuration
3. The replication mode (asynchronous, return receipt or return twosafe)
that is in use
Consult the Timesten replication guide for information on detailed recovery
procedures for each combination.
================================ END ==================================

The information in the forum article is the abridged text of a whitepaper I wrote recommending best practice for building a monitoring infrastructure for TimesTen. i.e. you write an 'application' in C, C++ or Java that performs these monitoring activities and run it continually in production against your datastores. Various aspects of the behaviour of the application could be controlled by configurable parameters; these are not TimesTen parameters but parameters defined and used by the monitoring application.
In the specific case you mentioned, the 'lastMsg' value returned by ttReplicationStatus is the number of seconds since the last message was received from that peer. The monitoring application would compare this against some meaningful threshold (maybe 30 seconds) and if lastMsg is > that value, raise an alarm. To allow flexibility, the value compared against )MAX) should be configurable.
Does that make sense?
Chris

CCMS Monitor for SMTP-Service via ICM SMTP-Plugin

Similar Messages

Maybe you are looking for