last1: late reply - but yeah, separating connection and transaction didn't make sense to me either. Hence why I simply log everything per transaction and ignore everything that doesn't yield a transaction (e.g. it has to reach MAIL FROM)
Whilst logging connections without transactions might seem sensible to some people, I can't see the point, the signal-to-noise ratio is horrid.
And you could be talking about considerable volumes in some circumstances.
tasansga: I've added your plugin to the "Other Plugins" on the Haraka Wiki
tasansga
_smf_: thanks. Hope it's useful for others.
SynchroM joined the channel
_smf_
tasansga: thank you - it's always nice to have new contributions.
The only improvement I'd say you could make is publish each plugin as a separate module (see the recent changes to Haraka to allow plugins to be npm modules).
tasansga
_smf_: "Plugins as modules" looks interesting, I'll try that. Separating the plugins doesn't make much sense though, they rely all on the ldappool plugin.
_smf_
Yeah - good point.
Although you can make each plugin 'require' ldappool in packages.json