Re: Disabling XBATCH by default in innd

Hi Russ,

>> For users of CURRENT snapshots (main branch for upcoming 2.7.0 release),
>> innd no longer accepts XBATCH commands by default.  A new "noxbatch"
>> parameter has been added in incoming.conf, that should be set to false
>> for remote peers with which you're using XBATCH.  (This may be very rare
>> nowadays...)
> 
> I wonder if it would be worth avoiding the double negative.  In other
> words, introduce a new parameter "xbatch" with a default of "false" that
> you set to "true" if you want to allow XBATCH access.
> 
> (I know INN has a few double negatives in configuration already, but they
> tend to confuse people so it may be worth avoiding adding new ones.)

Yes, that's exactly why I chose "noxbatch" as we already have 2 double 
negatives in incoming.conf.
I'm fine with naming it "xbatch" instead.

Maye we could rename "nolist" and "noresendid" to "list" and "resendit" 
in the major 2.7.0 release?
innupgrade can do the change.
This way, we'll get rid of all double negatives in incoming.conf.

We could also remove "comment" and "email" parameters which are unused 
in the code (I've checked), just mentioned "marked as reserved for 
future use" in documentation.

-- 
Julien ÉLIE

« Ce que j'aime chez vous, c'est que vous savez jusqu'où on va trop
   loin. » (Cocteau)
-- 
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers