Re: Disabling XBATCH by default in innd

Hi Russ,

>> Maye we could rename "nolist" and "noresendid" to "list" and "resendid"
>> 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.
> 
> I know it's always disruptive to change things like this, but personally
> I'd lean in favor of this.  What do other folks think?

Let's wait for other opinions then.


>> 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.
> 
> "comment" is, IIRC, left over from a desire to make the configuration file
> readable and writable by code without losing information.  That work was
> never complete, and at this point I think if we were going to pursue this
> again, we'd use a different format like YAML.  (The Python ruamel.yaml
> module supports reading and writing YAML while preserving comments and
> order.)  I'm in favor of dropping this.  Maybe innupgrade could convert
> any that it finds to actual comments?

Yes, I was meaning to drop code parsing for "comment" and "email", and 
innupgrade would just comment the lines (and not remove them).


> "email" I'm a bit more worried about since it's possible that people have
> used that field as documentation to record the contact email address of a
> peer.  I have no idea if anyone has done that or not, but keeping the
> field is also fairly cheap, so I'm not sure if it's worth the potential
> disruption.  Although maybe there too innupgrade could work some magic.

It would become commented in incoming.conf:
#email: "[email protected]"

-- 
Julien ÉLIE

« Perl programming is an *empirical* science. » (Larry Wall)
-- 
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers