[opendmarc-users] Logging by default

[Scott Kitterman]

On Thursday, February 21, 2013 12:37:45 PM Todd Lyons wrote:
> On Thu, Feb 21, 2013 at 12:12 PM, Murray S. Kucherawy <msk at blackops.org> 
wrote:
> >> opendmarc), then it would be worthwhile to force the syslog setting on
> >> in order to address item #2 and item #4.
> > 
> > syslog can't help with (2), because assertion failures cause the program
> > to
> > terminate before any more code is executed.
> 
> That crossed my mind, but I thought I didn't
> 
> > I take this to mean, then, that you support a default "on" for syslog?
> 
> I think in the big picture it's more important that opendmarc itself
> can decide to "toggle it on in the event of an error causing tempfail
> or reject", possibly with the limitation "only if it would have
> otherwise been accepted/continued."  Maybe also add an option to turn
> that off/on, with the default being on.  When I turn off logging, I
> expect that it's only turning off messages that are not preventing
> proper delivery.  I still expect to see debug style output when an
> unexpected failure occurs.

For postfix (no idea about sendmail) if the filter dies and mail is unable to be 
delivered, postfix is very verbose in the logs about it.  I think "Can't 
deliver mail because the filter died" is the responsibility of the calling MTA 
to log.  Also for postfix, it's configurable if the lack of the filter will cause 
mail to be deferred or not, so opendkim won't even (really) know the impact of 
it failing.

Scott K