The new capabilities-feature is another extension mechanism that can be used to influence the normal flow of operations. By tagging certain things as capability provider, and others as capability requester, they can be dynamically matched at run-time. Specifically, the following capabilities have been implemented:

IODEF-support

IODEF is an XML-based representation format that can be used to exchange information about security incidents. IODEF is currently an IETF proposed standard. Support for IODEF has been implemented as follows:

• The mail templates-mechanism has been extended with an @IODEF@ macro. The macro will expand to a valid representation of the basic incident data in IODEF-format. One mail template may be marked as IODEF capability provider by checking the box at the bottom of the screen.
• Each user can be marked as an IODEF capability requester. This is accomplished by checking the box at the bottom of the user details screen.
• The import queue mechanism provides an IODEF import filter that can be used to automatically parse and import messages containing IODEF markup.
  

When mail message is prepared to a recipient that is as an IODEF requester, the currently selected mail template will be ignored and that user will always be sent messages using the IODEF provider template. When preparing bulk email, separate messages will be created for IODEF requesters and non-IODEF requesters.