Field

Description

Full text indexing service (used by IMAP SEARCH)

Select from the list:

None

Full-text search is not used.

Windows Search

Windows Search is used.

Provided that you have Windows Search installed (or you use Windows 7 where it is included), you can enable full text search within received email messages.

Windows Search indexes all words within a message (including headers and "text based" attachments – not only pain text but also, for example, .doc files) and saves them to a database with fully qualified paths (with usernames included) to files where these words occur. This allows to distinguish between users as they have to log in.

To check if Windows Search works properly, go to Control Panel – Indexing Options. The list has to include the mail item with the Exclude property with value of _outgoing:

Click the Advanced button to open the Advanced Options dialog:

You should see something similar to this figure. Note that the Index Properties and File Contents option is selected.

Automatically Configure Windows Search

Click the button to tell Windows Search to add email folder(s) to the list of folders that are indexed and start indexing of the folder content.

NOTE: Indexing may take some time. Do not select the Windows Search item (the above feature) immediately after clicking the button. Wait until indexing is done.

NOTE: Indexing works for all subfolders of the IceWarp\mail\ folder (the default one upon System – Storage – Directories – Mail path). Should you have set a different Mailbox path for any user(s), you have to add this path(s) to Windows Search to have these folders indexed too. Example: C:\mail\

NOTE: To index network drive(s) under Windows 7, you need to run the following patch: http://www.microsoft.com/downloads/details.aspx?FamilyID=f7e981d9-5a3b-4872-a07e-220761e27283&displaylang=en.

Field

Description

Processing incoming messages in MDA queue

Check this option to have the MDA queue used.

NOTE: Huge MDA queues (e.g. more than 13 000 emails) can cause SMTP not working properly.

If messages are not flowing, you can:

· either increase number of threads

· or run smtp.exe/systray using Command Line. In this case, it is not started as a service but as an application.

As a service, it has timeout set to 30 second and when there is a huge MDA queue it simply does not make it to start in the timely fashion. As an application, it does not have timeout set.

Use MDA queue for internal message delivery

Check this option to have all internal messages processed via the MDA queues.

This means that any internal message (bounce back, server generated message, Account Forwarder message, etc.) will be processed via an MDA queue and all filter, rule, AntiSpam, IceWarp Anti-Virus, etc. processing will be performed on the message.

Maximum number of simultaneous threads

Specify the maximum number of threads to use for processing incoming messages.

This can help alleviate problems on high-load servers where the sending server times out, but IceWarp Server still processes and delivers the message. The Sending Server then tries again, and a duplicate message is received.

If you enter a non-zero value here then any incoming messages are stored immediately to an incoming folder, for later processing, and the session is closed so there are no timeouts.

You should only consider using this option on high-traffic servers or servers that have major AntiSpam and/or IceWarp Anti-Virus processing.

NOTE: In MDA mode a message is accepted and then processed by other filters at a later time. If a message is then refused a bounce back is sent to the sender. If the sender's address is spoofed than an innocent recipient could get the bounce back which would be considered as spamming - because of this the recommended bounce back level in MDA mode is "local senders"

Field

Description

Maximum SMTP hop count

Sometime a message can get into a 'relay loop', where it is being passed between servers trying to find a delivery point. A hop is defined as one pass of the message to a server.

Specifying a value here instructs IceWarp Server to count the number of servers the message has been through, compare it with this value, and reject the message if the number of hops exceeds the specified value.

Maximum SMTP server recipients

Specify the maximum number of Server session recipients allowed in an outgoing message.

This can be used to protect your server from overload.

Maximum SMTP client recipients

Specify the maximum number of Client session recipients allowed in an outgoing message.

If the number is exceeded the message will be split into multiple sessions.

Exceptions

Here you can override "Maximum SMTP client recipients" for specific target domains.

Press the button to open a dialog allowing you enter the target domain and the override value.

Use TLS/SSL

Check this box and IceWarp Server will connect to remote servers using TLS/SSL, if the remote server is capable of this.

NOTE: If you want to use TLS instead of SSL while sending/receiving mails, use the basic ports in email client (25 for SMTP) and mark to use TLS. (For SSL, use the usual SSL ports).

Hide IP address from Received: header for all messages

Checking this option tells IceWarp Server not to put the IP address in a messages Received: header.

This effectively stops people from being able to work out your local network configuration.

Add rDNS result to Received: header for all messages

Check this option and a reverse DNS lookup will be performed for each incoming message and the result added to the message headers.

NOTE: Using this option improves security but can severely impact performance on high-load Servers.

Add Return-Path header to all messages

Check this option and IceWarp Server will add a Return-Path header to the email. This can be useful for debugging and checking where an email came from.

Dedupe email messages

If a user has multiple aliases and a message is sent to more than one of the aliases the end User will receive multiple copies.

Also, if a user is a member of more mailing lists (or groups) and these lists (groups respectively) receive the same message, this user will receive multiple copies.

Check this option and IceWarp Server will check for duplicate message to the same end user and only deliver one of them.

NOTE: If the Bounce back for failed recipients feature in WebClient (Tools – Administrator Options – Mail – General) is enabled, this option can not be used. As a result of enabling of both options, users would receive duplicated messages.

Field

Description

Active

Tick the box to enable header/footer processing.

Header/Footer

Click the button to define header/footer files. The Header/Footer dialog opens.

Field

Description

Header text file

A fully qualified path to a text file which will be inserted as a header to text format messages.

Header HTML file

A fully qualified path to an HTML file which will be inserted as a header to HTML format messages.

NOTE: The extension of this file must be htm or html for this function to work correctly.

Footer text file

A fully qualified path to a text file which will be inserted as a footer to text format messages.

Footer HTML file

A fully qualified path to an HTML file which will be inserted as a footer to HTML format messages.

NOTE: The extension of this file must be htm or html for this function to work correctly.

Local to local

Header and Footer will be inserted in a message if the sender and recipient are local.

Remote to local

Header and Footer will be inserted in a message if the sender is remote and recipient is local.

Local to remote

Header and Footer will be inserted in a message if the sender is local and recipient is remote.

Remote to remote

Header and Footer will be inserted in a message if the sender is remote and recipient is remote.

NOTE: If you are using HTML headers or footers you should only use HTML found within the <BODY> tag.