Re: future directions

On 04/28/2012 03:41 PM, Robert Spier wrote:
>  log a reasonable amount, especially for LOGINFO.  I know, I know,
> reasonable is hard to pin down, but a little bit of guidance could go a
> long ways here:
>
>        DEBUG -> fire hose, spray away logging anything and everything.
>        INFO      -> normal operational info:  goal is a one line summary
> per plugin
>        NOTICE -> unusual results that are not errors
>
>
> In general, this seems quite reasonable.
Is there currently something like a CHIME event (or method) that is
agreed-upon to trigger logging and resetting statistics, that every
installed plugin would get hooked with at regular intervals? That's my
top-down suggestion of the moment

>> I'm working on a "Qpsmtpd Big Picture" document that contains a flowchart
>> of a sample connection, a catalog of all the plugins, what each plugin
>> does/sets/changes, and what information is made available to subsequent
>> plugins via notes. It took me quite a while to wrap my head around this,
>> and that learning curve presents a significant barrier to entry for
>> potential qpsmtpd users.
superduper