Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: Disabling XBATCH by default in innd (Julien ?LIE)
2. Re: Disabling XBATCH by default in innd (Russ Allbery)
3. Re: Disabling XBATCH by default in innd (Julien ?LIE)
4. Re: Disabling XBATCH by default in innd (Russ Allbery)
----------------------------------------------------------------------
Message: 1
Date: Wed, 23 Mar 2022 18:10:32 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Disabling XBATCH by default in innd
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
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)
------------------------------
Message: 2
Date: Wed, 23 Mar 2022 10:54:04 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: Disabling XBATCH by default in innd
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE <[email protected]> writes:
> 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.
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?
> 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?
"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.
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 3
Date: Wed, 23 Mar 2022 19:14:26 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Disabling XBATCH by default in innd
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
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)
------------------------------
Message: 4
Date: Wed, 23 Mar 2022 11:21:37 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: Disabling XBATCH by default in innd
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE <[email protected]> writes:
> It would become commented in incoming.conf:
> #email: "[email protected]"
Oh, that's a great idea that for some reason I didn't think of. I'm in
favor of doing that.
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 139, Issue 2
*******************************************
