On Wed, Jul 14, 2010 at 2:03 PM, Murray S. Kucherawy <msk_at_blackops.org> wrote:
>> That's also the only use case I can think of for it, though. I can crack
>> that nut with a local patch to create a default, or by checking the config
>> file for an argument (but that requires the config file to contain it, which
>> it may not already). Since opendkim has yet to release in Debian stable,
>> it's not such a big deal for me, but I can't say the same for Ubuntu, which
>> has released with 2.0.2...
> Yeah, that's a good argument for restoring it, and I've encountered this in
> a work-related project as well. We can put it back for 2.1.3.
As a FreeBSD port maintainer, I prefer restoring -P option.
That makes killing or signaling the filter from startup script much simpler.
Regards,
--
Hirohisa Yamaguchi
<umq.461_at_gmail.com>
Received on Wed Jul 14 2010 - 05:18:32 PST