Status Node Reference

Transcription

1 IceWarp Unified Communications Status Node Reference Version 10.4 Printed on 23 February, 2012

2

3 Contents Status 1 Message Queue... 2 Spam Queues... 3 Quarantine... 3 Whitelist... 4 BlackList... 5 Greylisting... 7 Intrusion Prevention... 8 Traffic Charts Logs Example Mailing List Logs Example Anti-Spam Report Log Interpretation of 5xx errors in Icewarp SMTP Statistics Sessions Account Statistics Volume... 26

4

5 1 C H A P T E R 1 Status The Status node allows access to various queues, logs and statistics areas of IceWarp Server. This node can be extremely helpful in diagnosing problems, seeing what has happened historically, and seeing what is happening right now. Using these can increase your understanding of how your IceWarp Server is being used. In This Chapter Message Queue... 2 Spam Queues... 3 Traffic Charts Logs Statistics Sessions Account Statistics Volume... 26

6 2 Status Node Reference Message Queue The Message Queue node allows you to view both Incoming and Outgoing queues or you can show the messages from user's mailbox. You can choose either user's regular inbox or his/her spam folder. It lists all the messages from chosen destination and moreover, you can double-click the message in the list and it opens the message in text editor. Field Server Mailbox Account Filter Max Items Description Select the type of the server queues: Outgoing, Incoming, MDA, SMS. Select the appropriate folder of the selected account. Use the "..." button to select the appropriate account of which you want to view queues. You can filter message queue using expressions from the From, To and Subject fields. Specify a non-zero value here to limit the number of messages displayed. Press the Refresh button after entering the value. NOTE: The higher the value, the slower the list will be to populate. NOTE: There is maximum of items set to Loading more items could break up server. Button Refresh Delete Send Now Bounce Back Whitelist Blacklist Description Refreshes the queue or mailbox so you see current list of messages. Deletes chosen message you can use Ctrl and Shift keys to choose more messages. Forces an attempt to deliver the messages. Finishes the attempts to deliver the message in queue and returns the messages back to sender as undeliverable. Click the button to whitelist the sender of the selected message. Click the button to blacklist the sender of the selected message.

7 Spam Queues 3 Spam Queues The Spam Queues node allows you to administer spam queues. In This Chapter Quarantine... 3 Whitelist... 4 BlackList... 5 Greylisting... 7 Intrusion Prevention... 8 Quarantine Selecting the Quarantine tab presents you with a list of messages awaiting action. For each message in the queue you, are shown the Sender, Subject, Date/Time sent, Owner (recipient) and Recipient Domain: Field Sender Description Specify a sender address here to only show messages from that sender. You will need to press the Refresh button after entering the information. Owner Specify an owner's (recipient's) address here to only show messages destined for a particular address. You will need to press the Refresh button after entering the information. Domain Specify a Domain name here to only show messages from a particular Domain. You will need to press the Refresh button after entering the information. Max Items Specify a non-zero value here to limit the number of messages displayed. You will need to press the Refresh button after entering the value.

8 4 Status Node Reference NOTE: The higher the value, the slower the list is populated. Number between the list and buttons Refresh Add Whitelist Blacklist Deliver Delete This figure indicates number of the list items. (In this case, it is 3.) Press this button to refresh the list, taking into account any filters you have entered. Non-functional. Press this button to have the Senders of selected messages added to the Whitelist. Press this button to have the Senders of selected messages added to the Blacklist. Press this button to have selected messages delivered without having the Sender added to the Whitelist or Blacklist. Press this button to have selected messages deleted without any further action. Whitelist Selecting the Whitelist tab presents you with a list of whitelisted senders. For each message in the queue, you are shown the Sender, Date/Time added, Owner (recipient) and recipient's Domain: Field Sender Description Specify a Sender address here to only show messages from that sender. You will need to press the Refresh button after entering the information. Owner Specify an owner (recipient) address here to only show messages destined for a particular address. You will need to press the Refresh button after entering the information. Domain Specify a domain name here to only show messages for a particular domain. You will need to press the Refresh button after entering the information. Max Items Specify a non-zero value here to limit the number of messages displayed. You will need to press the Refresh button after entering the value. NOTE: The higher the value, the slower the list is populated. Refresh Press this button to refresh the list, taking into account any filters you have entered.

9 Spam Queues 5 Add Press this button to add a user to the whitelist. The Whitelist dialog will open, where you should enter the Sender and Domain details: Sender - the address to be whitelisted Owner - the owner of the rule. You can specify: a user address to whitelist the sender for a single user. a domain to whitelist the sender for a domain. an asterisk to whitelist the sender for all domains on the server Use the '...' button to open the standard Item Select dialog. Whitelist Blacklist Deliver Delete Press this button to have the selected senders moved to the Whitelist useless here. Press this button to have the selected senders moved to the Blacklist. Non-functional button Press this button to have selected senders deleted from the Whitelist. BlackList Selecting the Blacklist tab presents you with a list of blacklisted senders. For each message in the queue, you are shown the Sender, Date/Time added, Owner (recipient) and recipient's Domain:

10 6 Status Node Reference Field Sender Description Specify a sender address here to only show messages from that sender. You will need to press the Refresh button after entering the information. Owner Specify an owner (recipient's) address here to only show messages destined for a particular address. You will need to press the Refresh button after entering the information. Domain Specify a domain name here to only show messages for a particular domain. You will need to press the Refresh button after entering the information. Max Items Specify a non-zero value here to limit the number of messages displayed. You will need to press the Refresh button after entering the value. NOTE: The higher the value, the slower the list is populated. Refresh Add Press this button to refresh the list, taking into account any filters you have entered. Press this button to add a user to the blacklist. The Blacklist dialog opens, here you should specify the Sender and Owner information: Sender - the address to be blacklisted Owner - the owner of the rule. You can specify: a user address to blacklist the sender for a single user. a domain to blacklist the sender for a domain. an asterisk to blacklist the sender for all domains on the server Use the '...' button to open the standard Item Select dialog. Whitelist Blacklist Deliver Delete Press this button to have the selected senders moved to the Whitelist. Press this button to have the selected senders moved to the Blacklist useless here. Non-functional button. Press this button to have the selected sender deleted from the Blacklist..

11 Spam Queues 7 Greylisting Selecting the Greylisting tab presents you with a list of connections that have been made to IceWarp Server, and their Greylisting Status Pending, Authorized, Expired. For each message in the queue, you are shown the Sender, Owner (recipient), Status and Date/Time of first connection attempt: Field Status Description Select Status from the dropdown to only show entries with that status. You will need to press the Refresh button after entering the information. Owner Specify Owner (recipient's address) here to only show messages destined for a particular address. You will need to press the Refresh button after entering the information. Value Specify the sender's address here to only show messages from that sender. You will need to press the Refresh button after entering the information. Max Items Specify a non-zero value here to limit the number of messages displayed. You will need to press the Refresh button after entering the value. NOTE: The higher the value, the slower the list is populated. Refresh Authorize Delete Press this button to refresh the list, taking into account any filters you have entered. Press this button to authorize the selected connection. Press this button to delete the selected connection from the queue.

12 8 Status Node Reference Intrusion Prevention Selecting the Intrusion Prevention tab presents you with a list of IP addresses that have been blocked by the Intrusion Prevention function, along with the Date/Time that the block will expire. Field Refresh Add Description Press this button to refresh the list,. Press this button to Add an IP address to the list. You are presented with the Tarpitted IPs dialog, where you should specify the IP address: NOTE: The expiration time will be calculated for you according to your Anti-Spam settings. Remove Remove All Expired Remove All Press this button to remove the selected IP addresses.. Press this button to have all expired IP addresses deleted from the queue. Press this button to have all IP addresses removed from the queue. Intrusion Prevention Reason Codes Reason Code C I M R D A P Explanation Tarpitting invoked via Content Filters IP blocked for exceeding connections in one minute IP blocked for delivering oversized message IP blocked for exceeding RSET command count IP blocked for being listed on DNSBL The account that this message was sent to was a "tarpit" account so the sending IP is tarpitted IP block for exceeding unknown User delivery count

13 Spam Queues 9 Y S U L IP blocked for Relaying IP blocked for exceeding Spam score in a message Ip blocked Manually via Console IP blocked for too many failed login attempts

14 10 Status Node Reference Traffic Charts Here you can see nicely done charts of traffic on your server. You can choose not only particular services to be shown but different types of messages can be shown as well e.g. Received or Send etc. Of course, you can adjust the time period to be shown so you can see charts per day, per week or per month. Field Service Description Select the service you wish to display. Category Select the category of the shown data. E.g.: SMTP Spam Refused #. <Interval> From/To Refresh Save As Image Select the interval for data revealing. (1 Day, 1 Week, 1 Month, specified interval) Available only when Interval chosen. Click this button to reveal relevant data. Click the button to save data currently shown. NOTE: You can zoom in into a selected area. Just mark this (rectangle) area using the left mouse button. To zoom out, click the Refresh button.

15 Logs 11 Logs The Logs tab allows you to show any part of logs on your server. You can choose the type of logs (even Error logs and Instant Messaging Archive can be shown), the Date and exact period of that date to be shown. Field Service Date From/To Filter Refresh Load Clear Delete Save To File Find Description Select the service that you want to view logs for. Select the day. Specify time period. Usage of the hh:mm:ss format is possible. Enter searched string. It can be any part of a log IP, time, thread ID, user, etc. Multiple filter can be used separate strings by ";" (semicolon) that works as a boolean AND. Click the button to reveal fresh data. Click the button to show logs for selected service, day, etc. Click the button to clear log display. Click the button to delete revealed logs. Click the button to save the selection you made to a new file. Opens a find dialog, where you can search through the current log file. This may come extremely handy for the quick visual log analysis.

16 12 Status Node Reference Explore Opens the log directory (as defined in Tools - Storage - Directories). NOTE: Log filtering is disabled for following types of logs: - Instant Messaging Archive - Instant Messaging Presence - VoIP (SIP) - LDAP - ActiveSync - SyncML - WebDAV - Anti-Spam Reports - PHP Error In This Chapter Example Mailing List Logs Example Anti-Spam Report Log Interpretation of 5xx errors in Icewarp SMTP... 14

17 Logs 13 Example Mailing List Logs This example shows logs of a message sent to a mailing list and logs of messages sent to mailing list recipients. In the mailing list scenario, one message arrives to a mailing list account. Its ID is called original ID. Because it is a mailing list, the message is resent to mailing list recipients. The resent s have another ID, but you can find the ID of the original message in the log file. Example Anti-Spam Report Log This section explains Anti-Spam report logs. Challenge [0001] 11:24: Log Part Description 11:24:42 time duration of report script running (in seconds) 1 number of active accounts ( = they have access to Anti-Spam or Quarantine) 0 number of active spam administrators 23 total number of spam items (= sum of all spam messages in active domains/accounts) 0 total number of quarantine items (= sum of all quarantine messages in active domains/accounts)

18 14 Status Node Reference Interpretation of 5xx errors in Icewarp SMTP SMTP delivery errors can occur in SMTP session log and the category "5" indicates that a message was not delivered. The table below lists the most common SMTP errors with a short description to help you understand their cause, and provides brief remedy instructions. Consult further documentation before you modify any security settings. Co de En. Code Error Phrase Description Remedy Instructions Command unrecognized Domain name required The SMTP command currently used was unrecognized or is not supported by the SMTP service. Sender has no domain specified (usually in MAIL FROM). Review the syntax of the last command and try again. Another possibility is that you are trying to use telnet and the telnet connection to your server is not allowed. Check the settings in administration console: Mail Service > Security > Advanced. Specify the sender's domain name and try again. The problem will be with user's client, not your server. The client configuration is probably not supplied with a domain name Unbalanced SMTP session syntax invalid (usually unbalanced brackets). Check the syntax of the last command and the configuration of corresponding.dat files Syntax error in parameters scanning HELO/EHLO requires domain address Authentication canceled Authentication failed Common syntax error. You probably mis-typed last command or last string is invalid. Usually when there was blank or invalid string sequence after HELO/EHLO command. The process of authentication was canceled for any reason. The username/password combination provided during authentication was invalid. Check the syntax of the last command. Retry the SMTP greeting with correct HELO/ELHO command. Restart the authentication process by using proper command. Reenter both the username and the password and authenticate again Permission denied You are not authorized to send. Result of "Reject if originator's IP has no rdns" or "Reject if SMTP AUTH is different from sender". Check the authentication in client. Be sure the options are NOT checked in

19 Logs Sorry, we do not support this operation Incorrect command sequence Authentication already done HELO/EHLO command required HELO/EHLO already specified Unrecognized authentication type Authentication required [AUTH] This operation is not allowed. A supported command was used in invalid order. For example command RCPT TO used before MAIL FROM or DATA command used when RCPT TO command was not accepted. Error occurs by reauthentication. Greeting error. HELO/EHLO command is required by the server. Greeting used again. Invalid authentication type. Incorrect or none type of AUTH specified. Authentication with command AUTH is required. administration console, or: Put the local IP range and your client IP in the "Relaying from" box, or: Create a Bypass for this IP/host. You can allow/disable particular operations and commands from the administration console: Mail Service - > Security -> Advanced. Solution depends on the context in which this error occurred. Check the last few commands sequence. You have to use HELO or EHLO command. You can deactivate this option in administration console, or create a Bypass: Mail Service - > Security -> Advanced. Use the command AUTH with proper authentication type. Use AUTH command (SMTP Server requires authentication) or disable this authentication type in administration console We do not relay Server is not open for relay We do not relay, account limits apply Refer to this FAQ. Check the account limits for the particular user account, its domain and on the server level You have rights to send mail to local domains only The user who gets this error is allowed to send mail only to local domains. Disable this option in the administration console: Management -> [User] -> Options -> User can send mail to local domains only Access not allowed 1) Server blocked access by a blacklist filter, or 2) Reject if originator's domain is local and not authorized option turned on. 1) Review server black list filter settings or set a bypass file. 2) Local users have to authorize themselves so if they do not have this set up in their clients and you turned this on they are not allowed to send.

20 16 Status Node Reference Access to not allowed by rules Permission denied Unknown local user Unknown user; rejecting No such user found No such mailing list found Too many recipients Message size exceeds fixed maximum message size Message cannot be accepted, virus found Message cannot be accepted, content filter rejection Message cannot be accepted, spam filter rejection Message cannot be accepted, spam rejection Message deleted by filter Message 1) Server blocked user access by a blacklist filter/rule, or 2) Server blocked access from the originating server by HELO/EHLO Filter. Unknown user account. The recipient is not local, thus reject the message. User account is not local. Mailing list is not local. The number of recipients exceeds the maximum of allowed recipients. Too many data was sent by the user. User account has an amount limitation. Virus was found in the message body or in the message attachment. Content filter applied and the message was rejected. Message is probably spam. Message is probably spam. 1) Review server black list filters and user rules or set a bypass item. 2) Whitelist the originating server in HELO/EHLO filter, or remove it from blacklist, or create a Bypass. Behavior and the treatment of messages coming to unknown user accounts can be set from administration console: Management < [Domain] > Unknown Account. Older versions of IceWarp Mail Server used to follow RFC and had maximum of recipients set to 100. If you need more recipients or use mailing lists, upgrade to the latest version (adds support for unlimited number of recipients). You can increase or disable amount limit from administration console - user account management - Limits tab. Make sure all 3 levels (server, domain and user) are set to 0 (stands for unlimited). If you think the attachment is not harmless (false positive), try to alter the configuration of the anti-virus engine (Quarantine instead of Reject), or create a Bypass entry. Review the content filter settings in administration console. If you think this message is spam (false positive), try to alter the configuration of the anti-spam engine, index the message by Bayesian or create a blacklist entry. If you think this message is not spam (false positive), try to alter the configuration of the anti-spam engine, index the message by Bayesian or create a whitelist entry. Alter your content filters configuration. If you do not want to use Challenge Response,

21 Logs 17 challenged by filter Maximum mailbox size exceeded Maximum message size exceeded. you can deactivate it in your anti-spam settings (Trust tab in older versions, now Quarantine node). Review settings of Limits on server / domain / user level. Review settings of Limits on server / domain / user level Message cannot be accepted, filter rejection The message was rejected. Check your filter settings and configuration.

22 18 Status Node Reference Statistics Here you can see complete statistics about the services which you choose from the dropdown on the top the amount of data they transferred, the number of connections, etc. Most of the items are self-explanatory. Item Server Connections Client Connections Server Data Transferred Client Data Transferred Description The connections, when IceWarp Server acts really as the server side in the Client/Server architecture. e.g. When a user connects to SMTP server and send a message. The connections, when IceWarp Server acts as the client side in the Client/Server architecture. e.g. When the message is already received from a user and it is addressed to external user, IceWarp Server establishes a connection to another server and sends the message (in this case, IceWarp Server acts as client) Data transferred within Server Connections. Data transferred within Client Connections.

23 Statistics 19 Anti-Spam/Messages Numbers of messages positively evaluated or caught by appropriate feature (such as Content Filters, Anti-Spam System, etc.) snmp-mib.txt File The current version of this file is available in <InstallationRoot>\doc\snmp-mib.txt. Counter Increase Counter for one filter is increased once per session i. e. multiple recipients (within one session) filtered by one type of a filter do not cause multiple counting. But, multiple recipients filtered by different filters cause counter increase of all applied filters. E.g. we have two recipients, for one recipient, the message is evaluated as spam, for the second one, it is rejected. After this session, two counters are increased. SpamAssassin This counter counts number of messages where SpamAssassin got score different from zero. It does not count "spam messages", because almost all messages get non zero score. This counter in fact means how many times SpamAssassin was applied.

24 20 Status Node Reference 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. 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. History works for every service separately. Session History tab displays all history events up to the Max 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)

25 Sessions 21 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 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 [00000A1C] Thu, 22 Apr :01: Connected [00000A1C] Thu, 22 Apr :01: >>> ESMTP to je gol; Thu, 22 Apr :01: [00000A1C] Thu, 22 Apr :01: <<< HELO localhost [00000A1C] Thu, 22 Apr :01: >>> Hello localhost [ ], pleased to meet you [00000A1C] Thu, 22 Apr :01: <<< MAIL From:<admin@icewarpdemo.com> [00000A1C] Thu, 22 Apr :01: >>> <admin@icewarpdemo.com>... Sender ok [00000A1C] Thu, 22 Apr :01: <<< RCPT To:<test-icewarp-001@yahoo.com> [00000A1C] Thu, 22 Apr :01: >>> <test-icewarp-001@yahoo.com>... Recipient ok; will forward [00000A1C] Thu, 22 Apr :01: <<< DATA [00000A1C] Thu, 22 Apr :01: >>> 354 Enter mail, end with '.' on a line by itself [00000A1C] Thu, 22 Apr :01: *** <admin@icewarpdemo.com> <test-icewarp-001@yahoo.com> :00:00 OK [00000A1C] Thu, 22 Apr :01: >>> bytes received in 00:00:00; Message accepted for delivery [00000A1C] Thu, 22 Apr :01: <<< QUIT [00000A1C] Thu, 22 Apr :01: >>> closing connection SYSTEM [00000A1C] Thu, 22 Apr :01: Disconnected This is a session when client on the server sends a message from 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 [00000F6C] Thu, 22 Apr :01: Client session Connected [00000F6C] Thu, 22 Apr :01: Client session <<< 220 mail.yahoo.com - Yahoo, Inc. ESMTP

26 22 Status Node Reference [00000F6C] Thu, 22 Apr :01: Client session >>> EHLO [00000F6C] Thu, 22 Apr :01: Client session <<< 250 8BITMIME [00000F6C] Thu, 22 Apr :01: Client session >>> MAIL [00000F6C] Thu, 22 Apr :01: Client session <<< 250 ok [00000F6C] Thu, 22 Apr :01: Client session >>> RCPT [00000F6C] Thu, 22 Apr :01: Client session <<< 250 ok [00000F6C] Thu, 22 Apr :01: Client session >>> DATA [00000F6C] Thu, 22 Apr :01: Client session <<< 354 go ahead [00000F6C] Thu, 22 Apr :01: Client session <<< 250 ok qp [00000F6C] Thu, 22 Apr :01: Client session *** <test-icewarp :00:00 OK [00000F6C] Thu, 22 Apr :01: Client session >>> QUIT [00000F6C] Thu, 22 Apr :01: Client session <<< 221 mail.yahoo.com - Yahoo, Inc. SYSTEM [00000F6C] Thu, 22 Apr :01: Client session Disconnected This is a session where IceWarp Server sends along the message which was received in previous Server session.

27 Account Statistics 23 Account Statistics This feature allows you to monitor the usage of your users. This feature keeps a log of all sent and received messages statistics along with some other information. If you require the server to perform Account Statistics, you need to enable the feature on the System node Logging Services tab. Alternatively, you can enable Account Statistics via API by: tool set system C_Accounts_Global_Accounts_UserStat 1 Only then IceWarp Server will record the statistics. The Chart tab offers you information in a graphical format: The user statistics logs can be exported to file using the User Statistics dialog. Field Filter Category From/To Description The filter field specifies account and domain filters for which the logs are required. Multiple filters can be specified using semicolon. Determines which item should be shown in the graph. These fields indicate the timescale over which to obtain the log entries. It is considered only when the Selection is chosen instead of particular time period in pull-down menu.

28 24 Status Node Reference Max Items Specify a non-zero value here to limit the number of messages displayed. You will need to press the Refresh button after entering the value. NOTE: The higher the value, the slower the list will be to populate. Refresh Export To File Save As Image Refresh the graph according to the chosen information in the fields. Queries the server to retrieve the logs and saves them to a file. Click the button to save data currently shown. Log structure The log file structure consists of multiple lines. The first line contains the list of headers. The next lines display all the users' records matching the filter criteria. The last two lines are special. Field Received Messages Received Amount Sent Messages Description The number of messages delivered to user's mailbox. The total amount of data delivered to user's mailbox. The number of messages sent by the user to IceWarp Server. NOTE: Message sent to multiple recipients will be counted as one message for each copy, i.e. a message sent to 20 users counts as 20 messages. Sent Amount Sent Out Messages Sent Out Amount Last Sent Last Received Last Login Created The total amount of data sent by the user to IceWarp Server. The number of messages sent from IceWarp Server whose originator is the user. Local sent by the user is not considered. The number of recipients is considered because each recipient can be on a different server and it means that IceWarp Server has to send mail out additional times. The total amount of data sent from IceWarp Server whose originator is the user. When the user sent their last message. When the last message delivered to user's mailbox arrived. When the user logged on IceWarp Server for the last time. This field shows when the user's mailbox was physically created (the first login or first received mail). NOTE: This date can differ from the day when the account was created in GUI if it was not used the same day. Messages Count Messages Amount The current number of messages in user's mailbox. The total size of messages in user's mailbox. The line before the last line specifies all unknown senders. This record is present only if the filter criteria is empty. This information includes the relayed messages for unknown senders and delivered messages from unknown senders.

29 Account Statistics 25 The last line specifies the total information of the filter excluding the unknown line (last but one). The List tab offers you the same information in a tabular format: Field ID Last Login Last IP Last Host Files # Files Quota Received # Received Description Account address. When the user logged on IceWarp Server for the last time. IP address of the last server used to connect to IceWarp Server. Host name of the last server used to connect to IceWarp Server. Only applies when the Main Menu Options Resolve address in current view option is checked. Number of files within the account folder. Size of files within the account folder. In the case the account has any size limit set, used percentage of this limit is shown. Number of received messages. Size of received messages. Sent # Sent See Sent Messages above. Total size of sent messages. Sent Out # Sent Out Created See Sent Out Messages above. Total size of sent out messages. The date of account creation.

30 26 Status Node Reference Volume The Volume tab lets you watch the current server volume statistics. To calculate the volume information press the Refresh button. Every section calculates also the previous volume counter. You can directly type in the address or domain of the interest but you should rather select the object in the Domains & Accounts - Management section, right-click and select Volume. Or you can click the Account menu and choose Volume there. Another possibility is to select an account, group or domain with '...' button through simple Select Accounts dialog. IceWarp Server calculates the current volume by browsing all files and objects of the IceWarp Server directory. That means it is basically dependent on the file system. If you have too many files this can take a while so be sure you use it properly.