** Changed in: mailman/3.0 Milestone: 3.0.0a6 => 3.0.0a7 -- Add the equivalent of postconf(1) https://bugs.launchpad.net/bugs/518517 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

** Changed in: mailman/3.0 Status: Triaged => Opinion -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/518517 Title: Add the equivalent of postconf(1) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/518517/+subscriptions

This one would be relatively easy for someone wanting to start contributing to Mailman. ** Changed in: mailman/3.0 Status: In Progress => Confirmed ** Changed in: mailman/3.0 Assignee: Barry Warsaw (barry) => (unassigned) ** Tags added: easy -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/518517 Title: Add the equivalent of postconf(1) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/518517/+subscriptions

please around unstructions, thanks! ** Changed in: mailman/3.0 Assignee: (unassigned) => bernard Keimel (bernie-bill) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/518517 Title: Add the equivalent of postconf(1) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/518517/+subscriptions

bernard, why did you attach that image? It looks like you're spamming us. :( ** Changed in: mailman/3.0 Assignee: bernard Keimel (bernie-bill) => (unassigned) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/518517 Title: Add the equivalent of postconf(1) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/518517/+subscriptions

Bernard, I'm really glad you're so enthusiastic about helping out the Mailman project, but please don't assign the issue to yourself until you've contacted the Mailman developers and introduced yourself. Assignment of the bug is not necessary to *work* on the bug. The preferred workflow is for you to upload a branch to Launchpad and link it to this bug. Then you can do a merge proposal for your branch, at which point, one of the core developers will review your branch and help you land it, if appropriate. Also, please explain what the image is supposed to be in comment #3. ** Changed in: mailman/3.0 Assignee: bernard Keimel (bernie-bill) => (unassigned) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/518517 Title: Add the equivalent of postconf(1) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/518517/+subscriptions

** Changed in: mailman/3.0 Assignee: bernard Keimel (bernie-bill) => (unassigned) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/518517 Title: Add the equivalent of postconf(1) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/518517/+subscriptions

On Jan 22, 2013, at 05:25 PM, David Soto wrote:

I would like to work on this. I was wondering whether it would be a good approach to return the results as I'll explain below and to pass the section and key names to the command by the use of options:

/bin/mailconf -s section -k key

Both options would be optional. If you don't specify a key you would get a list of all the keys and their values of a given section and, if you don't specify a section, you would get a list of all the keys and values matching the given key name. If both options are provided, it would just print the value and if only one of the two is provided, it would return the "full path" of the keys, as suggested by Barry (http://mail.python.org/pipermail/mailman-developers/2012-February/021725.htm...).

Some examples of usage:

...

...

/bin/mailconf -s mailman -k site_owner changeme@example.com

...

...

/bin/mailconf -s shell [shell] prompt : >>> [shell] banner : Welcome to the GNU Mailman shell [shell] use_ipython : no

...

...

/bin/mailconf -k path [runner.master] path: $QUEUE_DIR/$name [logging.template] path : mailman.log etc.

I like this. The alternative is to accept the `[section]variable` syntax for the key, so that the retrieval syntax would match a hypothetical (i.e. not part of this bug) setting syntax. postconf can set values too, but I propose we don't worry about that for mailmanconf now. Of course the extended syntax can always be added later, so the -s and -k semantics you describe above seem reasonable. (Note that these days, this would be implemented as a bin/mailman subcommand, probably `config`.) Feel free to follow up on mailman-developers if you have further questions. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/518517 Title: Add the equivalent of postconf(1) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/518517/+subscriptions

** Changed in: mailman/3.0 Milestone: None => 3.0.0b4 ** Changed in: mailman/3.0 Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman/3.0 Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/518517 Title: Add the equivalent of postconf(1) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/518517/+subscriptions