Which functions is missing from the OLX app


Support from Net at Work:
Due to the current change as of Jan 1st 2007 we offer you a turnkey solution:

OLXDisclaimer is an SMTP Eventsink from Gangl, which is particularly impressive due to its simple operation without missing the necessary functions. Since this program is not bloated as a virus scanner, spam protection or other functions that you have usually already implemented elsewhere, the configuration and installation is quick and straightforward. This makes the program particularly sympathetic for companies whose administrator is not a full-time specialist.

OLX on Exchange 2007
Version 2.0 is a transport agent which, like the journal agent and rule agent, can process all messages during transmission.

OLX Disclaimer configuration steps
You can set all that olxdisclaimer.wmv (4MB)


Please use the manufacturer's website to request the current version. http://www.gangl.de/URL/OLXDisclaimer.html

Installation (pictures show version 1.4)

I did not document the actual installation with pictures. As an InstallShield copies the files to the server, you can safely do all of them. The following data must be entered during installation.

  • Confirm the license agreement
  • Enter destination path
    By default, the program is installed in C: \ Program Files \ OLXAgents \ OLXDisclaimer Agent

If you do not enter a test or product key, the following restriction applies, which is clearly displayed at the end of the setup:


As usual with Windows programs, the uninstallation takes place via the control panel. The server must then be restarted so that the DLLs are released and deleted. Unfortunately, the INETINFO process blocks the OLXDisclaimer.dll so that this file and the directories are only deleted automatically after a restart. If you only start INETINFO yourself, you can delete the files without restarting the server.


The configuration interface starts automatically during the installation. The list is initially empty and contains an entry after adding a disclaimer rule.


Click the "Add" button to start an assistant that gives you a lot of freedom in defining the various options. Just take a look at a sample rule here:

Select a meaningful description and then the corresponding text files that will contain the template for your disclaimer. You can put an appropriate message BEFORE as well as BEHIND the message.

If your users send both TEXT and HTML messages, then you will need to maintain multiple versions of the disclaimer. Unfortunately, there is no editor built into OLXDisclaimer. Of course, you can easily edit the text disclaimer with Notepad. Here is a sample of a disclaimer with fields from the Active Directory:

You can customize the HTML version with an HTML editor of your choice. A corresponding sample file is also included.

Make sure that the HTML file is "clean". Especially if you create a disclaimer with Word and save it as HTML, you should "optimize" the HTML code. So, of course, Word turns the "%%" character into an HTML representation.

You can also attach appropriate files to each email, e.g. certificates, images, etc.

At first glance, this seems a little superfluous, as a company certainly doesn't want to attach a file to every mail, but if you think a little further then it can be quite useful. For example, the disclaimer could include a file that is regularly generated by another system, e.g. a stock market ticker. The file attachments would be, for example: a route description or the terms and conditions, if the sender comes from sales.

Of course, the filtering of senders and recipients becomes interesting. In this way, you can create different disclaimers for each OU (e.g. company group or department).


The restriction to OUs also binds the admin with regard to the OU concept. for most administrators, however, the OU is exactly the desired filtering. Otherwise, of course, LDAP filters are also possible.

Disclaimer processing can be completely overridden using rules. So you can define exceptions if certain "code words" are in the message or in the subject.


The replacement of special characters probably arose from the necessity that not all mail systems code HTML properly. And if a product like the OLKDisclaimerAgent changes the mail anyway, it can also carry out this correction immediately.

The control of an "end time" is very useful if the disclaimer contains, for example, an announcement for a trade fair or event. It would be embarrassing if it was still advertised after that point.

With that the establishment of a disclaimer rule would be done. Of course, you can set up multiple rules. Make sure, however, that you do not use competing rules.


You could also find a pure product description on the manufacturer's website. If you take a look behind the scenes, you will find the following files in the program directory:

Fortunately, the product range is simply manageable. The two log files, for example, are interesting:

  • OLXDisclaimer.log
    The program logs its activities here.
  • OLXRegistrar.log
    Here you will find information on registration. This file is surely more interesting for the manufacturer for troubleshooting, but as an admin you can also see exactly how and where the OLXDisclaimerAgent registers.

The agent is not an SMTP "OnArrival" transport sink, as I use it to insert EventDisclaimer, but an "OnPostCategorize" sink.

| Binding |
Event: SMTP Transport OnPostCategorize
ID: {BD172EB0-8292-4667-B17F-D934C3ACA7DC}
Name: OLXDisclaimer Agent
SinkClass: OLXDisclaimerSMTPSink.SMTPEventSink
Priority: 24575
Enabled: -1

In this way, of course, the program circumvents the restrictions that an "OnArrival" sink cannot process MAPI mails directly. Unfortunately, this interface cannot be used with CDO and therefore not with VBScript or Visual Basic. C ++ programming is required here.

The configuration itself is in the "OLXDisclaimer.dat" file. This file can easily be copied to other servers if, for example, you operate several connector servers. Licensing is correspondingly simple. The license key is simply copied into the directory.

When the sink is started for the first time, OLXDisclaimer sends an email with the license information to the address "[email protected]". It is actually sad that people pass on license keys and thus ultimately make the further development of the product more difficult. This behavior is clearly explained in the license agreement and is therefore not done secretly.

If you "buy" OLXDisclaimer, you will only receive one license file (olkdisclaimer.lf). You must save this in the Windows directory (C: \ WINDOWS) and not in the program directory.

Disclaimer and Exchange 5.5, 2007, Notes, GroupWise and other SMTP systems

Anyone who still uses Exchange 5.5 and does not want to integrate the Microsoft DLL in the SMTP connector or who uses Exchange 2007 and does not like the simple solution of Exchange 2007 (see E2K7 disclaimer), or who uses a completely different mail server, can also use OLXDisclaimer with this Systems. The trick is simply to route the mail through a Windows 200x SMTP server:

  • The server's operating system must be Windows 2000/2003
    Without this basis, the next point cannot be fulfilled.
  • Windows SMTP service must be installed
    This is always needed for the OLX disclaimer
  • The server must be a member of the domain
    OLXDisclaimer uses OUs or LDAP fields and cannot otherwise assign a disclaimer. There is currently no "Default Disclaimer" if the sender is not found in the AD.

Now you can tell the previous mail server that it is sending outgoing mails via smart host to the Windows SMTP server and then finding the normal route to the Internet from there. So you can also add a "disclaimer" to these systems. Depending on the system, it may even be possible to implement this linkage on one system.

Cluster and multiple SMTP servers

OLXDisclaimer only ever registers on the first virtual SMTP server. When used on a cluster or a server with several SMTP instances, it can of course happen that this is the wrong SMTP server or that OLXDisclaimer has to be linked to several SMTP servers. That is also possible. However, to do this, you have to do the binding by hand.

cscript smtpreg.vbs / add 2 OnPostCategorize "OLXDisclaimer Agent" OLXDisclaimerSMTPSink.SMTPEventSink ""

cscript smtpreg.vbs / remove 2 OnPostCategorize "OLXDisclaimer Agent"

You also need a current version of SMTPREG.VBS. The version initially distributed by Microsoft could only register OnArrival Sinks.

Please save text file with the ending VBS

Further information on SMTP sink and registration can also be found on SMTP-EventSink.

Disclaimer and S / MIME

Since version 1.5, OLXDisclaimer recognizes digitally signed mails. A disclaimer tool cannot add a disclaimer to such emails without destroying the signature. That is the principle of a digital signature that changes in a mail are recognized. OLXDisclaimer does not attach a disclaimer to such emails in order not to break the signature. This is also recorded in the log file.

03/26/2007 13:27:29: Info: New message detected. Sender: [email protected],
Subject: RE: Disclaimer to RTF
03/26/2007 13:27:29: Info: Recipient: [email protected]
03/26/2007 13:27:29: Info: Skipping e-mail because it is digitally signed or encrypted

Disclaimer and "SendAs"

A tricky question with "disclaimers" is the behavior when using proxies. Here especially when a person sends "on behalf" of another person. Which disclaimer is attached to the mail in this case?

OLXDisclaimer attaches the actual sender's disclaimer to the dispatch "on behalf of". However, if the mail is sent using "Send As", then the mail is sent with the signature of the "FROM mailbox".

Disclaimer and images

Since version 1.6 it is also possible to send "inline images" with the disclaimer. To do this, place the image in the same directory as the disclaimer (e.g. C: \ Programs \ OLXAgents \ OLXDisclaimer Agent \ Templates \) and integrate it using an IMG tag.

<img border="1"alt="Firmenlogo" src="logo.jpg" width="369" height="72">

Please note, however, that not all recipients can work with inline images and that this image can only be inserted into HTML and RTF messages.


For a list price of less than 1000 euros, you get many functions, so that it is simply no longer worth developing in-house. OLXDisclaimer can now also process redirects, automatic replies, etc. and thus goes far beyond the basic function of a simple disclaimer.

For most companies, a commercial solution is likely to be the best choice for centralized implementation of disclaimers.

If you don't like a server-side disclaimer because it breaks signed emails or the user ultimately doesn't see which disclaimer is added, you can look at OLXCorporate (http://www.gangl.de/URL/olxcorporate.html), for example, which is an Outlook Add-on works. The products can also work in combination so that the server process only appends a disclaimer if this is forgotten, prevented or not possible using ActiveSync.

more links