On Jul 17, 2012, at 1:46 PM, Barry Warsaw wrote:
On Jul 17, 2012, at 01:34 PM, Richard Wackerbarth wrote:
But there probably should be a per-list configuration option for gateway-ing a list to the news. There may well be lists for which I am willing to advertise the existence without wanting their content to be spread far and wide.
Agreed. Some thoughts.
One is whether the mailing list is gatewayed to "Usenet" (really any external NNTP server). We already have settings for this.
Then that should suffice for Alex's purposes. He should not have to "discover" that the gateway is active. If he gets a message on the archive service interface, he sends it out. If it doesn't appear, it wasn't meant to be.
In an mm3 world where we can have multiple system-wide configured and enabled archivers, it probably makes sense to allow individual lists to opt-in or -out of specific available archivers.
Yes, this also allows George to collect metrics about messages without having the underlying messages archived. Or it also allows the messages to be archived without being counted by the metrics. It's all up to how our users choose to configure things.
We've talked about this before, and it's something I'm generally in favor of allowing.
The complication is that the system may want to force individual lists to enable certain archivers. E.g. if the site administrators want to keep a local maildir of all messages to all mailing lists.
This is a more general question concerning just how the configuration service enforces site policies.
On an implementation level, it gets mapped so that, to each of the various message handling services, each list has its own full set of configuration parameters. In other words, a message handler does not care whether "switch x" is set because it is set specifically for the current list or because it is set for all of the lists within some collection of lists.