On 6/4/10 2:38 PM, "W B Hacker" <wbh@???> wrote:
> Presuming this applies only to (the balance of) the current session and child
> process, why should it be a 'PANIC' situation anyway? Hard-coded PANIC,
> IMNSHO,
> should be reserved for events/absence of events that impair the ability of the
> MTA to function at all.
>
> Now - if it were to disable optioned-on DKIM signature verification (attempts)
> for all *subsequent* sessions/children, that MIGHT be worthy of a 'PANIC'.
Thank you, Bill.
Sadly, I was thinking more of my situation here, where I don't want panic
log entries for the DKIM parsing failure but do want the (main) logged
information about incoming DKIM generally, than about a proper fix for
<
http://bugs.exim.org/show_bug.cgi?id=966>.
I think I'll go ahead and build a sed script that throws my patch into the
source and see what happens on the development server. (Our builds begin by
extracting the source fresh from the tarball, so such things have to happen
with each build.)
--John
