No. What you downloaded and are currently evaluating is the full product. But the included license certificate file is only valid for 60 days. When you purchase a license, you'll receive a new license certificate file. You must then copy this new license certificate file into the directory <InstallDir>\Licenses. The new license certificate file will be automatically detected. There's no need to restart anything or to reinstall the product.

Yes. DisclaimIt 3.x is fully functional and supported on SBS 2000/2003.

No. DisclaimIt 3.x supports only Exchange 2000/2003. It won't run on an Exchange 2007/2010 server. The reason is that MS reworked the complete architecture of Exchange, they removed the COM-based transport interfaces and substituted them with .NET-based interfaces, causing DisclaimIt 3.x to be incompatible with Exchange Server 2007/2010.
A new version of DisclaimIt compatible with Exchange 2007/2010 has been developed and is available as DisclaimIt 4.5. Please note that DisclaimIt 4.5 is not compatible with MS Exchange 2000/2003. Use DisclaimIt 3.x for MS Exchange 2000/2003.

Licenses for DisclaimIt 1.x or 2.x are not valid for DisclaimIt 3.3 and must be upgraded to DisclaimIt 3.x licenses. Please look here for more information.

DisclaimIt ignores messages which are encrypted or signed. This is necessary because any change to such messages would corrupt them.

Yes, starting with DisclaimIt 3.0, processing of internal messages is supported.

Yes, starting with DisclaimIt 3.0, processing of internal and outbound rich text messages is supported.

Yes. DisclaimIt can process messages sent from all kinds of MS Exchange clients: Outlook, OWA, Outlook Express or other POP3/IMAP4 clients.

No. Text is added by DisclaimIt to messages while the message is in transit. The original messages in the user's Sent Items folder are not modified.

In the plain text of your text module, just insert empty lines at top before your text. In the HTML text, use HTML formatting tags (e.g. <P>, <BR>) to achieve the desired spacing.

It depends:

• For plain text messages: You can't specify the font for the plain text because plain text message doesn't support any kind of formatting - except line breaks.
• For HTML messages: Use the <FONT> tag in your HTML source code to specify the font to use.
• For rich-text (RTF) messages: The font properties of the plain text portion of your text module are preserved.

Your problem occurs if you are using an Outlook 2003/2007 client, your disclaimer text contains Umlaute and the message text contains only US-ASCII characters: Outlook in its default configuration will not use the configured encoding, for example: Western European (ISO), in case that the message text contains only US-ASCII characters, but will use the encoding US-ASCII for the message to send. When then DisclaimIt adds the disclaimer text which contains Umlaute, they are converted to their possible representation in US-ASCII (e.g.: ä -> a, ö -> o, ü -> u, etc. ). The solution for this problem is to configure Outlook 2003/2007 to always use the specified encoding, for example: Western European (ISO). This can be configured by unchecking the check box Auto select encoding for outgoing messages in the dialog Tools->Options->Mail Format->International Options. This setting can also be centrally configured by group policy.

• Install DisclaimIt on the new server.
• Copy the files in the following subfolders of the installation folder from the old server to the new server:
  • Attachments
  • Data
  • Images
  • Include
  • Licenses
• The settings of the computer object (SMTP Server Bindings, Directory Access, Message Archival, Diagnostic Logging) are not stored in configuration files but in the registry. You should use DisclaimIt Manager on the new server to manually configure any non-default settings.