JEMH directives not at first line

Matt Newton2

I'm having trouble figuring out whether JEMH is supposed to accept directives throughout the email or just at the first line. I've found this in the documentation:

The handler assumes that the first line(s) of an email may contain Directives. Generally, a single empty line after any Directives indicates the start of the Comment. If no Directives are found in the body at all, the whole email is used as the Comment (subject to minimum criteria being met, defaults found etc). The exception to this rule is the SubjectBasedFieldProcessor, which works for most options, is unable to be used for all options.

It seems to sort of imply that directives can be throughout the body, but maybe not. In my testing, JEMH has not been picking up directives unless they are at the top of the email.

Is there any way to configure JEMH to pull directives from anywhere in the email?

Thanks,

Matt

unknown

Short answer: No, body based directives are expected to precede 'content' that would be taken as 'comment content'. All examples illustrate this.

Longer answer: This allows those directives to be removed and not form part of the 'comment content'. Multi line directives may exist in JEMH directives, but the rider is that the last directive must not be a multi line, and a double CR signifies the end of directives.

Custom email field processors can be written, e.g. Nagios, eg Wufoo, each of which is tailored for a specific kind of content.

Once JEMH 1.0 ships as a p2 plugin complete with UI and so on, future extensions will allow you to write scripted 'custom' field processors without any recompilation.

Meantime, If your source is generic, perhaps a handler for such a source could be written.