At last, a new version of Adolsign is available for download. Version 1.9 introduces two new directives for conditional fields: --anchor and --format. Directive --anchor can be used to produce active links in your signatures, while the directive --format allows you to produce formatted output. You can also use %LOGONSERVER% variable in the configuration file paths, to make location-independent deployments easier.

Adolsign 1.9 has improved support for multiple groups in the configuration file and Office 2007 is now supported in signature installer packages created by the option --makepackage.

Conditional fields are a convenient way to handle empty values. It is often desireable to drop leading or trailing texts in signatures if a field is not defined or empty in Active Directory. Adolsign supports seven directives in field definitions:

Let's take a simple start (assuming that your Outlook is configured to send messages in plain text):

• Create the signature template hello.txt with the content below:

field_firstname field_lastname
field_title, field_department
field_company

Tel: field_telephone
Mobile:field_mobilephone
E-mail: field_email

Scan codes are special words recognizable by Adolsign. There is a one-to-one mapping between them and properties in Active Directory user objects. As an example the scan code field_firstname corresponds to the field First Name (or property FirstName) in Active Directory.

A signature template is simply the signature you want to add to your messages, with one exception: Fields you want to populate from the information in Active Directory are tagged by special scan codes recognizable by Adolsign.

Outlook supports three formats for signatures: HTML, rich text and plain text. What format Outlook will use is totally dependent on mail format settings in Outlook (example below is from Outlook 2003):