OpenBSD Mailing Lists: Directory, Archives and Majordomo Commands
OpenBSD manages its email lists at lists.openbsd.org. That site holds the directory and admin pages for lists under the openbsd.org domain OpenBSD Mailing Lists.
Where to start
The site provides a Mailing Lists directory. It lists all available lists, and users start there to find a specific list.
What each list page holds
Each list has its own page. The page gives details about the list, a link to its message archives, and a subscription form. Description, history access and sign-up sit together in one place.
How commands work
Lists use Majordomo, which takes management instructions by email. Commands go by email to majordomo@openbsd.org. More than 100 help documents explain the syntax for subscribe, unsubscribe, queries and other operations.
Why this approach holds up
The broader context here is continued use of email for infrastructure work. One directory entry per list lowers discovery cost. Archives keep discussion and decision history for browsing and searching later. Forms keep sign-up explicit and beside documentation. Email commands work from any mail client, without extra tooling or privileged dashboards.
In my view, putting policy, history and sign-up together is what matters most. It points to a clear order: read scope first, review prior discussion second, subscribe third. That cuts misdirected mail and repeated questions, and gives moderators a visible reference for what belongs where.
Looking at daily work, admin mail goes to Majordomo and discussion mail goes to the list. Archive links support checks before posting a question or patch. Email stays the interface, and the pages organize entry to it. I saw the same habit with my children learning group chats, check history before asking, and it applies well here.
Stepping back from the mechanics, this model feels spare beside threaded chat and platform ticketing. The tradeoff is deliberate. Explicit sign-up leaves less doubt about membership. Text commands leave a clear record of intent. Archives grow more useful over time for debugging, design rationale and operational postmortems. Where auditability and low dependencies matter, spare tooling is rational.
In practical terms for newcomers, start from the directory rather than guessing addresses. Treat list information as binding for scope and conduct, treat archives as first research before asking, and treat Majordomo help as manual pages for uncertain syntax. The curve is shallow once those habits are set, and they transfer well to other email-driven projects.
