The hMailServer COM API lets you write your own scripts and applications that integrate with hMailServer. Almost all objects in hMailServer are accessible using the COM library. As an example, both hMailServer Administrator and the PHP WebAdmin is entirely based upon the COM library. Besides writing application like theese two, you can write scripts that are automatically run when certain events take place. For example, you can write a script that filters messages before they are delivered to the recipients.
The Application object is the root object in hMailServers COM model. Using this object, you can access all hMailServer objects and settings. Before accessing any of the properties and methods on the Application object, you must call Application.Authenticate with valid credentials.
The hMailServer API behaves as most other COM APIs, but there are some special behavior which relates to exception handling and permissions.
It is possible to create triggers in hMailServer. Triggers are script which are executed when certain actions occur. Triggers are created by adding the script to the EventHandlers-file in the hMailServer Events folder.
These are the basic steps to perform when you want to access the hMailServer COM API.
- Create an instance of the hMailServer Application object. How to do this depends on what programming language you use. In VBScript, you call CreateObject(“hMailServer.Application”).
- Authenticate. Before you can call any other methods in the API, you need to authenticate. This is done using the Authenticate() method on the Application object. This is required to prevent unauthorized users to access your hMailServer installation.
- Call the methods and use the properties you need.
For a list of changes in the COM API, see the COM API Changelog
The complete COM API is available as a .NET class in the hMailserver bin directory …\hmailserver\bin\Interop.hMailServer.dll
- Domain objects
- Server-wide objects
- Scripting-wide objects
Please see the COM API examples page