79. pepsi-list¶
Create and manage mailing lists, their members and their owners.
79.1. Role¶
pepsi-list is the operator’s command-line tool for Pepsi’s mailing-list
subsystem. It connects through the shared [pepsi-postgres] section and
reads its own [pepsi-list] section for the handful of settings that belong
to the site rather than to a list. Started as root it continues as the
pepsi service account before connecting, so no sudo -u pepsi is needed.
It is not setuid and must not be made so. Reference:
pepsi-list(1).
This subsystem is a reimplementation of GNU Mailman 3; see Mailing lists, which says so at greater length and names what was taken from upstream.
79.2. What it manages¶
Domains — the mail domains lists may be created in. Registering one here is separate from
[pepsi-ingress] ACCEPTED_DOMAINS. If ingress does not accept a list’s domain, it refuses the list’s mail atRCPT.Lists — creation from a style, and every one of the 99 attributes that the REST API of GNU Mailman 3.3.10 exposes.
list showprints them all;list show --explainadds each one’s explanation.Members and owners — the four roles (
member,owner,moderator,nonmember). An owner gets a user account, because they sign in to the owner console; an ordinary subscriber does not need one.Bans — per list or site-wide, as an address or a
^-anchored regular expression.Pepsi-only per-list settings —
list set-ext, among themhold_dmarc_failures(on unless set tono; the importers setnoon the lists they create). These are deliberately absent from the REST API’s/configand live at/lists/<id>/pepsiinstead; Settings Pepsi invented explains why.
79.3. Two things it deliberately does not do¶
It does not ask permission. members add subscribes an address without
a confirmation. That is what a command-line tool is for — migrating a roster,
fixing a mistake — and it is also why it is dangerous: the confirmation
workflow exists so that an address proves it wants to be there. The -join
address and the web form go through that workflow; members add is the layer
beneath it.
``owner reset-password`` prints the password rather than mailing it. The
command-line path has to work when mail is broken, which is exactly when an
operator reaches for it. The ordinary way to change a password is the web reset
flow at /lists/reset, which mails a link.
79.4. Checking a site¶
pepsi-list check looks for problems that stay silent in production. A misconfigured
stage target fails loudly the first time a message reaches it; a list with no
owner simply accumulates held messages nobody sees, and a list asking for more
trigram indexing than the site allows simply gets less. Each finding carries a
remedy.
$ pepsi-list check
error: announce@lists.example.org: has no owner
`pepsi-list owner add announce@lists.example.org <address>`, or set
[pepsi-list] SITE_OWNER so its notices reach somebody
note: site: archive search: full text and trigram (substring, fuzzy)
79.5. Configuration¶
See pepsi.conf(5)’s [pepsi-list] section, and
Mailing lists for what each option decides.