Andrew,
Cool, thanks for the tip.
I'll review and consider (hope you don't mind I also post this reply
to our "admin" list), and may update/add/tweak on what we've presently
got in the footer bits.
Key issue/problem, is that most of these folks that hit reply and
ask/demand we unsubscribe them, don't bother to read (or remember or note)
the instructions/information when they subscribe, don't pay attention
to the (by default) monthly reminders the list automatically sends them,
and can't be bothered to read (or comprehend) footers. In any case,
when I get some time, I'll compare and review what we've presently got
in the footers, and see if it may be worth changing/adding/updating.
And can't really put it up higher (e.g. top) of the email - as that would
further annoy/inconvenience the 99.9%* who are perfectly competent and
capable of managing their list subscribe/unsubscribe status - to
accommodate the 0.1%* that can't be bothered to read and follow basic
instructions and documentation.
And good to hear from you! ... been quite a while. I'm well, hope
you're well too!
references/excerpts (and partially REDACTED):
*http://lists.balug.org/pipermail/balug-admin-balug.org/2014-September/001507.html
> From: "Andrew Fife" <andrewbfife(a)yahoo.co.uk>
> Subject: Re: Subject: BALUG list(s) unsubscribe
> Date: Wed, 10 Sep 2014 22:49:09 -0600
> Hi Michael:
>
> It's been a while and I hope you are well!
>
> If you're interested in added an unsubscribe link to the footer of
> all messages sent via Mailman, it looks like that can be done fairly
> easily. I found these instructions on how to append messages with
> an unsubscribe link here:
>
> http://www.mediaserve.com/knowledgebase/93/How-do-I-add-an-unsubscribe-link…
>
> I hope this is helpful, but no sweat if you prefer not to use this.
>
> Kind regards,
>
> Andrew
>
> -------------------------------
> Sent from my phone
> -------------------------------
>
>> On Sep 10, 2014, at 10:34 PM, "Michael Paoli"
>> <Michael.Paoli(a)cal.berkeley.edu> wrote:
>>
>> Subscribe/unsubscribe is completely self-service on BALUG lists.
>>
>> So, you should be able to fully take care of that yourself.
>> See the reference information (links, etc.) provided further below.
>>
>> If that doesn't work for you, please provide:
>> o The error diagnostic(s) (if any) you're getting when you attempt to
>> unsubscribe.
>> o What steps you're following that result in the above (never tell me/us
>> nor anyone your list password, but otherwise provide relevant details)
>> o FULL EMAIL HEADERS of an example message that you're getting or still
>> getting that you're trying to unsubscribe from.
>>
>> Hopefully you should be able to self-unsubscribe, but if that fails,
>> please let us know, as noted above.
>>
>> Thanks for your attention to this and your cooperation,
>>
>> The busy BALUG / list administrator folks.
>>
>> See also / references / excerpts / hints:
>> http://www.balug.org/#Lists
>> http://lists.balug.org/listinfo.cgi/balug-announce-balug.org
>> http://lists.balug.org/listinfo.cgi/balug-talk-balug.org
>> http://lists.balug.org/listinfo.cgi/balug-admin-balug.org
>> http://lists.balug.org/listinfo.cgi
>>
>>
>>> From: [REDACTED]
>>> Subject: Re: [BALUG-Announce] BALUG: Tu 2014-09-16 Todd Varland of
>>> AWS; & Oct.: 2014-10-21 New Venue!
>>> Date: [REDACTED]
>>
>>> To whom it may concern,
>>>
>>> Please remove me from your mailing list. Thank you.
new BALUG venue >=2014-10 - location to be determined
Four Seas Restaurant lost their lease. We still have meeting space there
through our September meeting (their last regular day of business will
be 2014-09-27). For our October meeting and beyond, we'll need a new
meeting location. Anyway, this can (and likely will) be discussed on
the "talk" list, and I'll also mention it fairly soon on the "announce"
list (not later than whenever we put out our next regular announcement).
Hopefully we'll come up with a good/excellent "permanent" (well, at
least long-term) location, but in any case we'll certainly meet
*somewhere*.
My initial thoughts:
o BALUG has always met in San Francisco, and almost always at the Four
Seas Restaurant in Chinatown. Despite it being the
"Bay Area Linux Users Group", given history and momentum, etc., it's
probably most appropriate/best to come up with a regular meeting
location that's in San Francisco, and not too far time/distance-wise
via walking or short Muni/BART hop from the general
Financial District/Downtown/SOMA/Chinatown area, or some reasonable
approximation thereof (e.g. parts of the Mission). Notably a fair
percentage of our typical attendees come in from the East Bay, and a
significant percentage of those come in via BART. Of course we may
have a bit of the self-selecting sample set phenomenon, but if we want
to retain at least most of our attendee base, we'd probably want
something at least fairly comparably convenient regarding location
(and also some kind of semi-reasonable parking not all that far away).
o Opportunity(?) :-) ... changes? Perhaps best to think of it as an
"opportunity" - perhaps we can improve or significantly improve some
factors of our meeting location. The
"Good locations for a BAD meeting will have" listed on:
http://bad.debian.net/shotgun_rules.txt
gives a pretty good overview of what generally constitutes a good
meeting location, though some of that is different for BALUG. Notably
BALUG sometimes has large crowds - e.g. >=110 people for some of our
meetings. BALUG also almost always meets at the same fixed location.
o (relatively) Unique to BALUG - some things are relatively unique to
BALUG. Many of them are probably well worth preserving - at least
if/as feasible, others might not be so important (and can sometimes
even be a moderate disadvantage). At least a few that come to mind:
o *typically* has speaker/presentation, and meeting location suitable
to that
o can accommodate *large* crowds, e.g. up to >~=200 people
o relatively convenient location for and in San Francisco, and
considered relatively central to the Bay Area (it is the
"Bay Area Linux Users Group", after all)
o Chinese food - rather good food and a quite good price, and the
simplicity of relatively fixed menu, and fixed price - and able to
handle large meetings. Note also the restaurant/food thing can be
both advantage and disadvantage - some folks often don't come on
account of the food cost/expectation and that part of the meeting
structure. Notably some may quite prefer a much lower to free cost
of totally participating and being present at all parts of the
meeting - while that may not be possible/feasible for many (e.g.
restaurant/cafe) venues, many also have a much "lower cost of
entry" (e.g. minimum purchase might be something like a beverage or
cookie or the like).
DO NOT REPLY ALL! (unless you're subscribed to BOTH lists)
maintenance starting after 2014-07-02 5:30 P.M. PDT,
expected to conclude before 2014-07-02 24:00 PDT
there may be no additional notifications for this set of outages
Various services will be intermittently (un)available.
Will impact:
SF-LUG:
sf-lug.org, sf-lug.com, www.sf-lug.org, www.sf-lug.com., etc.
will not impact: sf-lug(a)linuxmafia.com http://linuxmafia.com/pipermail/sf-lug/
For SF-LUG, there may also remain the coincidental but unrelated timing of:
http://linuxmafia.com/pipermail/sf-lug/2014q2/010554.html
BALUG:
will mostly only impact non-production and ancillary services, e.g.:
http://www.archive.balug.org/http://www.wiki.balug.org/wiki
etc.
WILL NOT IMPACT: BALUG main web site and its pages:
http://www.balug.org/
nor BALUG mail lists or email infrastructure
Technical details:
If it's on 208.96.15.250-208.96.15.254 it will be impacted.
Various hardware/firmware/operating system maintenance will be performed
on the physical host which has guest hosts of sflug and balug,
and additional work may also be done on the sflug guest virtual machine's
operating system.
Will be doing some system maintenance, so,
some ancillary BALUG services will be intermittently unavailable.
Note that this WILL NOT IMPACT: main web site and its pages:
http://www.balug.org/
nor our mail lists or email infrastructure.
It WILL IMPACT some other services, at least intermittently,
e.g.:
http://www.archive.balug.org/http://www.wiki.balug.org/wiki
etc.
Technical details:
If it's on 208.96.15.254 it will be impacted.
The (qeum-kvm) virtual machine guest on that IP will be undergoing some
maintenance:
"convert" /usr, /var, and /home filesystems from reiserfs to ext3
(well, actually do a final rsyncs from ro mounted filesystems in
single user mode, then switch 'em out and reboot)
(and probably also continue up/cross grade from i386 to amd64)