Adolsign

Adolsign changelog

Release history grouped from the itefix master release export.

No component table was found for the latest release.

Adolsign 2.5 introduces full language support in templates. While earlier versions were somewhat limited to ISO 8859-1 (Latin-1, Western European primarly), version 2.5 comes with the option –encoding , allowing you to use the language of your choice. A selected set of encodings supported: ascii,euc-cn,euc-jp,euc-kr,iso-2022-jp,iso-2022-jp-1,iso-2022-kr,iso-8859-1,iso 8859-10,iso-8859-11,iso-8859-13,iso-8859-14,iso-8859-15,iso-8859-16,iso-8859-2,iso-8859-3,iso-8859-4,iso-8859-5,iso-8859-6,iso-8859-7,iso-8859-8,iso-8859-9,UCS-2BE,UCS-2LE,UTF-16,UTF-16BE,UTF-16LE,UTF-32,UTF-32BE,UTF-32LE,UTF-7,utf-8-strict,utf8 A complete list of encodings supported can be achieved by running the command “adolsign –encoding”. Default encoding is still ISO-8859-1. As an example, you can convert your templates to UTF-8 encoding and use the command: adolsign –encoding utf8 …..

Distribution packages created by Adolsign 2.4 are cabaple of setting the default signature. You can simply use command line options –newdefault and/or –replydefault to trigger that functionality. It is also possible to specify the name/location of a distribution package by using the new option –packagename . Example: adolsign –sig corporate –new –reply –user test –packagename c:\packages\test will create c:\packages\test.exe , which will generate signature corporate and set it as the default signature for new/reply messages for the user test when it is run by the user. Adolsign 2.4 introduces the option –targetdirectory , allowing you to explicitly specify the location of the signatures directory. Even if Adolsign is capable of doing that job, it may be necessary with a manual override in certain circumstances. One other feature introduced in the new version is to process signatures in the configuration file in the order they are defined. Existing customers can download the latest version from their customer pages at www.itefix.net .

Adolsign version 2.3 introduces support for Office 2013. In addition, we use a new packaging technology delivering most of the system files in a directory structure which reduces the size of adolsign executable dramatically (from 2 MB to 200KB). That will make Adolsign faster to start, plus there will be no need for local storage at users’ home directories.

Adolsign 2.2 gets information from Active Directory in UTF-8 format, allowing to support a wider set of character sets instead of only Latin-1. To utilize this new feature, you need to save your template files in UTF-8 format. Text and html signatures are supported. In addition, Adolsign can now create anchors with hyperlinks in rtf signatures. Existing customers can download the latest version from their customer page at www.itefix.net

Adolsign 2.1 is now available with a new lookup directive for conditional fields. This capability allows you to replace values in Active Directory by values in lookup tables defined in the configuration file. A flexible way to support multi-language initials, titles and many more. Example: field_title( –lookup Norwegian_titles )field_title in the configuration file: [Norwegian_titles] Manager=Sjef Consultant=Konsulent Produces Sjef or Konsulent if title values in AD are manager and consultant respectively (case insensitive). Otherwise, the value itself is used.

Process template files only if the user is member of Domain Users group. You can specify multiple groups. Adolsign will proceed if the user is member of at least one group.
Produce a Vcard
This signature is default for new and reply messages
Copy files corporate.png and corporate.css from the directory where Adolsign is started from.
Process only if AD-value for company name contains CompanyX . Comparisons are based on regular expressions and case-sensitive. You can specify AD-fields multiple times, even the same attribute!
Don’t produce a Vcard
This signature is not a default one for new and reply messages
Copy directory CX-images and CX .css from \SRV\netlogon as well

Version 1.92 introduces support for Outlook 2010. It also handles mailto anchors properly without double slashes.

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. Examples: Conditional field field_homepage ( –anchor http )field_homepage will produce the html code field_homepage . Conditional field field_mobilephone( –format “%s%s%s %s%s %s%s%s” )field_mobilephone will produce 123 45 678 if the mobile phone value in AD is 12345678.