[sf-lug] Recipients needed for weekly roster mailing

Sat Nov 29 04:13:42 PST 2025

FYI, the BALUG VM (which also hosts sf-lug.org, etc., but not the SF-LUG list)
does also continue to pick up copies of the SF-LUG list roster and mbox archive.
Rick and I set that up many moons ago.
# echo file://`hostname``pwd -P`/
file://balug-sf-lug-v2.balug.org/home/sflug/sf-lug_roster/
# rlog sf-lug_roster 2>&1 | sed -ne '/^revision /{N;s/\n/
/;H;};${g;s/^\n//;s/^$\([^\n]*\n$\{5\}\).*$\(\n[^\n]*$\{5\}\)$/\1...\3/p;}'
revision 1.282 date: 2025/10/12 13:28:29;  author: sflug;  state: Exp;
 lines: +1 -0
revision 1.281 date: 2025/08/17 13:27:27;  author: sflug;  state: Exp;
 lines: +1 -1
revision 1.280 date: 2025/08/15 13:27:28;  author: sflug;  state: Exp;
 lines: +0 -1
revision 1.279 date: 2025/08/04 13:27:26;  author: sflug;  state: Exp;
 lines: +1 -1
revision 1.278 date: 2025/08/02 13:27:27;  author: sflug;  state: Exp;
 lines: +1 -0
...
revision 1.5 date: 2015/03/06 14:31:44;  author: sflug;  state: Exp;
lines: +3 -4
revision 1.4 date: 2015/02/06 14:32:18;  author: sflug;  state: Exp;
lines: +1 -0
revision 1.3 date: 2015/02/04 14:32:29;  author: sflug;  state: Exp;
lines: +219 -220
revision 1.2 date: 2015/02/02 23:08:04;  author: sflug;  state: Exp;
lines: +2 -11
revision 1.1 date: 2015/01/22 11:09:46;  author: sflug;  state: Exp;
#
The roster itself isn't public, but the stats are, even automagically
reported monthly,
e.g: http://linuxmafia.com/pipermail/sf-lug/2025q4/016168.html
Likewise automagic updating of copy of the raw mbox archive.
# echo file://`hostname``pwd -P`/
file://balug-sf-lug-v2.balug.org/home/sflug/sf-lug.mbox/
# rlog sf-lug.mbox 2>&1 | sed -ne '/^revision /{N;s/\n/
/;H;};${g;s/^\n//;s/^$\([^\n]*\n$\{5\}\).*$\(\n[^\n]*$\{5\}\)$/\1...\3/p;}'
revision 1.1557 date: 2025/11/17 15:43:58;  author: sflug;  state:
Exp;  lines: +196 -0
revision 1.1556 date: 2025/11/04 22:20:09;  author: sflug;  state:
Exp;  lines: +329 -0
revision 1.1555 date: 2025/11/01 14:31:09;  author: sflug;  state:
Exp;  lines: +326 -0
revision 1.1554 date: 2025/10/29 15:54:21;  author: sflug;  state:
Exp;  lines: +276 -0
revision 1.1553 date: 2025/10/22 06:09:15;  author: sflug;  state:
Exp;  lines: +610 -0
...
revision 1.5 date: 2015/02/08 10:19:56;  author: sflug;  state: Exp;
lines: +67 -0
revision 1.4 date: 2015/02/07 01:50:02;  author: sflug;  state: Exp;
lines: +2158 -0
revision 1.3 date: 2015/02/02 05:47:55;  author: sflug;  state: Exp;
lines: +1974 -0
revision 1.2 date: 2015/02/01 09:15:58;  author: sflug;  state: Exp;
lines: +8709 -0
revision 1.1 date: 2015/01/22 05:40:22;  author: sflug;  state: Exp;
#
And the raw mbox file is available for anyone to download and save copy of:
http://linuxmafia.com/pipermail/sf-lug/2025q4/016168.html
Also, recent copy also continues to be available here:
https://www.sf-lug.org/sf-lug.mbox/sf-lug.mbox
And theoretically also version control history under here:
https://www.sf-lug.org/sf-lug.mbox/
but looks like that's not presently visible/accessible.  I'll add
correcting that
to my todo list, but not a top item, and that list is over 6,700 lines
long ... and it
generally grows faster than things get removed from it.

Anyway, more backup(s)/redundancy, etc., is generally a good thing.

And (competent) volunteers can always be useful.
Not so useful is, after setting up someone's account to, e.g. be able to
maintain web pages, then they're like, "Uhm, but you need to open up FTP
so I can transfer the pages back 'n forth."
So, e.g., if someone wants to look over the web server configuration
(it is quite
non-trivial, as it virtual name hosts many sites, and including also
wiki and WordPress)
and figure out exactly what needs be adjusted to allow the RCS
directory and contents
thereof show and be accessible under
https://www.sf-lug.org/sf-lug.mbox/
then sure, stuff like that could be useful.
But stuff that generally increases the workload of the sysadmins,
list/web/mail/... admins,
and with negligible to zero useful results ... sorry, that's not so useful.
I've created a lot of accounts for volunteers ... most of whom manage to then
do nothing useful, or quite close to that.

On Fri, Nov 28, 2025 at 7:14 PM Rick Moen <rick at linuxmafia.com> wrote:
>
> Gentlebeings:
>
> Happy holiday, and I need one or more of you to speak up.
>
> Jim Stockford's e-mail has not been deliverable in a dog's age.
> Therefore, he has not been receiving the Sunday automated safety copies
> of this mailing list's roster, sent out by the cron daemon -- one of the
> things I set up to ensure continuity for SF-LUG in case my server goes
> down again.
>
> So, I need to substitute one or more person (two or three would be
> ideal) to receive that automated e-mail every week, taking Jim's
> place.  I therefore need a couple of volunteers.
>
> Your role would be merely to be one of the people who have the
> subscriber roster, and be able to provide it to SF-LUG if it's
> ever necessary to rehost/replace this forum.
>
> /etc/cron.weekly/mailman-rosters, which does the mail-out, is:
>
> #!/bin/sh
> set -euo pipefail
> #
> # mailman-rosters:  Cron script to mail out current Mailman mailing list
> # rosters.
> #
> #               Written by Rick Moen (rick at linuxmafia.com)
> #               $Id: cron.weekly,v 1.00 2015-01-21 20:28:01 rick
>
> set -o errexit  #aka "set -e": exit if any line returns non-true value
> set -o nounset  #aka "set -u": exit upon finding an uninitialised variable
>
> /var/lib/mailman/bin/list_members -f sf-lug | mail -s "sf-lug Roster as
> of $(date +%F)" jim at well.com
>
> ----- Forwarded message from Mail Delivery System <Mailer-Daemon at linuxmafia.com> -----
>
> Date: Thu, 27 Nov 2025 12:27:20 -0800
> From: Mail Delivery System <Mailer-Daemon at linuxmafia.com>
> To: root at linuxmafia.com
> Subject: Mail delivery failed: returning message to sender
>
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   jim at well.com
>     SMTP error from remote mail server after RCPT TO:<jim at well.com>:
>     host xmx.well.com [52.0.124.244]: 422 4.2.2 Mailbox is full:
>     retry timeout exceeded
>
> ------ This is a copy of the message, including all the headers. ------
>
> Return-path: <root at linuxmafia.com>
> Received: from root by linuxmafia.com with local (Exim 4.72)
>         (envelope-from <root at linuxmafia.com>)
>         id 1vNBlW-00081T-GG
>         for jim at well.com; Sun, 23 Nov 2025 07:12:38 -0800
> Date: Sun, 23 Nov 2025 07:12:38 -0800
> Message-Id: <E1vNBlW-00081T-GG at linuxmafia.com>
> To: jim at well.com
> Subject: sf-lug Roster as of 2025-11-23
> From: root <root at linuxmafia.com>
> X-SA-Exim-Connect-IP: <locally generated>
> X-SA-Exim-Mail-From: root at linuxmafia.com
> X-SA-Exim-Scanned: No (on linuxmafia.com); SAEximRunCond expanded to false
>
> [RM: Redacting from this posting the 216 members' e-mail addresses
> in plain ASCII format, that were dumped to console in ASCII order by running
> "/var/lib/mailman/bin/list_members -f sf-lug" and mailing that out.]
>
> ----- End forwarded message -----