Sessions

New and very powerful session monitoring and session history engine lets you perform various operations with services sessions including killing, viewing of logs, history, etc.

sessions

Figure. Sessions section.

The Active sessions type lets you monitor the active connections and sessions to the all server services (including VoIP, GW, IM, FTP, Control, etc.)

Icons in Active Session

Within the Active sessions monitor, the icons can have one of two letters and one of three colors:

S denotes a Server session (IceWarp Server acts as receiver)

C denotes a Client session (IceWarp Server acts as sender)

Yellow denotes an Active session

Green denotes a Success

Red denotes a Failed Session

You can view the commands being sent to the server and also the responses. If you have the service logging on, you can double click on the particular session and the whole history of the session protocol (log) will be displayed or can be saved into a file.

Every session can be killed. Various statistics, such as volume of transferred data for SMTP,POP3 and IMAP, current URL for Control, number of connections for user and volume of data FTP are shown.

newViewKillDisplaySessionLog

History works for every service separately. The session History type displays all history events up to the maximum history value.

Icons in Session History

There are three colors and two letters which can be shown in icons in the Session History.

S denotes a Server session (IceWarp Server acts as receiver)

C denotes a Client session (IceWarp Server acts as sender)

Red denotes an Fatal Error

Green denotes a Success

Brown denotes a Disconnected session

If you double-click the circle, the log of the appropriate session will appear.

Server session

This type of session means that IceWarp Server acts as a server in the client/server model. In other words, IceWarp Server is the receiver of a message in this case. It can occur when:

  • a client wants to send a message through the IceWarp Server
  • another server sends a message to IceWarp Server because it is e.g. for users on IceWarp Server

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 Connected

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 >>> 220-195.122.222.29 ESMTP to je gol; Thu, 22 Apr 2004 22:01:42 +0200

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 <<< HELO localhost

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 >>> 250 195.122.222.29 Hello localhost [127.0.0.1], pleased to meet you.

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 <<< MAIL From:<admin@icewarpdemo.com>

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 >>> 250 2.1.0 <admin@icewarpdemo.com>... Sender ok

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 <<< RCPT To:<test-icewarp-001@yahoo.com>

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 >>> 250 2.1.5 <test-icewarp-001@yahoo.com>... Recipient ok; will forward

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 <<< DATA

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:42 +0200 >>> 354 Enter mail, end with '.' on a line by itself

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:43 +0200 *** <admin@icewarpdemo.com> <test-icewarp-001@yahoo.com> 1 348 00:00:00 OK

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:43 +0200 >>> 250 2.6.0 348 bytes received in 00:00:00; Message accepted for delivery

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:43 +0200 <<< QUIT

127.0.0.1 [00000A1C] Thu, 22 Apr 2006 22:01:43 +0200 >>> 221 2.0.0 195.122.222.29 closing connection

SYSTEM [00000A1C] Thu, 22 Apr 2006 22:01:43 +0200 Disconnected

This is a session when client on the server sends a message from a mail client to the IceWarp Server – it was received by IceWarp Server.

Client session

This type of session occurs only when IceWarp Server sends along an already received message to another mail server.

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session Connected

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session <<< 220 mail.yahoo.com - Yahoo, Inc. ESMTP

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session >>> EHLO 195.122.222.29

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session <<< 250 8BITMIME

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session >>> MAIL From:<admin@icewarpdemo.com>

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session <<< 250 ok

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session >>> RCPT To:<test-icewarp-001@yahoo.com>

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session <<< 250 ok

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session >>> DATA

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:50 +0200 Client session <<< 354 go ahead

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:51 +0200 Client session <<< 250 ok 1082664147 qp 10068

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:51 +0200 Client session *** <admin@icewarpdemo.com> <test-icewarp-001@yahoo.com> 1 521 00:00:00 OK

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:51 +0200 Client session >>> QUIT

212.80.76.44 [00000F6C] Thu, 22 Apr 2006 22:01:51 +0200 Client session <<< 221 mail.yahoo.com - Yahoo, Inc.

SYSTEM [00000F6C] Thu, 22 Apr 2006 22:01:51 +0200 Client session Disconnected

This is a session where IceWarp Server sends along the message which was received in the previous server session.

Note: Session history is stored just in the service memory. Only last 100 sessions are stored in the memory, this memory is cleared with every single restart - –this applies for all the services except for WebClient. WebClient runs PHP sessions and only the ones which are not active anymore are visible in the history.
For WebClient, the history shows all sessions which were not properly closed with a logout - so the session file exists in php\temp and because of this file, the entry shows up in history.
Also note that if you close WebClient by closing the browser, the corresponding session remains active for 15 minutes after browser shutdown and then shifts into history.