And now for your kind attention, the devuan-dev meet notes from
Wednesday, January 9th, 2019.

plasma41

------------------------------------------------------------------------

# Devuan meet Jan. 09, 2019 @20:30 UTC

Pad is here:
https://pad.dyne.org/code/#/1/edit/yg+TGcFlq2nARNbOlvdz1g/VEhas7ZmiI4-0jNfigD+864d/

Meet here: https://vdc.dyne.org/devuan
   * Please post notes prior to the meet.
   * Please add your name as 'Present' below when you get to the
     meet.
   * When adding a comment in someone else's notes, please
     pre-pend your name like this: (whoever) whatever . . .

Present: golinux, rrq, obeardly, jaromil, fsr, RickMoen.


## Old Business


## Old Actions
Conference is totally stalled. not.


## New Business
Not much

### golinux
- https://devuan.org/get-devuan

### RickMoen

- Reviewed effective use of Mailman admin WebUI page Privacy Settings,
Spam Filters to intercept and hold problematic posting threads for
listadmin review, if necessary. (I've used this feature in the past to
intercept problematic crossposting. In this case, Dng's listadmin team
used it to prevent a banned user from tricking frequent posters into
copying his screeds back on-list.)

- Promised to prototype and send to Jaromil a change script for utility
/var/lib/mailman/bin/<a
href="https://wiki.list.org/DOC/4.81%20How%20do%20I%20change%20one%20setting%20on%20all%20lists%3F">config_list</a>
to roll out DMARC mitigation to various Dyne.org mailing lists from
the command line. This will require running as user list at the system
shell prompt, i.e., wielding the Mailman
<a href="http://www.gnu.org/software/mailman/site.html">site administrator</a>
role, not just listadmin authority. My recommendation is to test the
change script against mailing list 'test', then against devuan-dev,
then roll out to other mailing lists more broadly.

No time like the present, so here's the solution:

[2019-01-10 update: Corrected carelessly wrong pathspecs for cited
/var/lib/mailman/bin/* utilities.]

Create this two-line file as /tmp/mailmanscript, and chown it to user
'list':

    dmarc_moderation_action = 1
    dmarc_quarantine_moderation_action = 1

On the Mailman host as root, do su - list to become user 'list'. (You
could do this as user root, but being the Mailman user is best
practices.) Then, to alter mailing list 'test' (running the script
against it):

    /var/lib/mailman/bin/config_list -i /tmp/mailmanscript test

To explain that, for setting dmarc_moderation_action, there should be
five possible settings:

    Accept
    Munge
    From
    Wrap Message
    Reject
    Discard

For purposes of the config_list utility, such multiple options are
always numbered as integers from zero upwards, so I believe you will
find that the current value is 0 (zero), meaning 'Accept'. You can view
an ASCII dump of a mailing list's configuration using config_list in
'output' mode, like this:

    /var/lib/mailman/bin/config_list -o - | less

Before making the change I mention, do that command and scroll down to
the dmarc_moderation_action item. You should see something like this:

    dmarc_moderation_action = 0
    [...]
    # legal values are:
    #    0 = "Accept"
    #    1 = "Munge From"
    #    2 = "Wrap Message"
    #    3 = "Reject"
    #    4 = "Discard"

The second config item, dmarc_quarantine_moderation_action, is a yes/no
toggle immediately below dmarc_moderation_action. For such toggles, it's
always the case that 0 signifies No, and 1 signifies Yes.

Obviously, it would be an excellent idea to re-run config_list in output
mode after making a change, to review the effects.

To roll out a change to many Mailman lists at once, standard shell
plumbing like 'for' loops are handy, e.g.:

    for list in $(/var/lib/mailman/bin/list_lists --bare); do
    /var/lib/mailman/bin/config_list -i /tmp/mailmanscript $list
    done

## New Actions
Action? What's that???