So, at present, BALUG lists use domain lists.balug.org.
While migrating lists(+list archives) off of DreamHost.com,
we'll need to use a temporary subdomain/name. When all is fully
completed, we'll end back up on lists.balug.org. Quesion is, name for
the temporary domain.
At first I was thinking lists2.balug.org - but that would be slightly
confusing potentially, as we shift back to lists.balug.org (e.g. folks
might expect a lists3, or wonder why we were going "backwards" (or
seemingly so). …
[View More]I expect the temporary will only be for week(s) to a
month or so ... and it can remain longer for backwards compatibility
(and eventually get "retired"). But, as we'll end up back on
lists.balug.org when all is said and done, ... what would be optimal and
less/least confusing ... to the extent feasible.
So, I was thinking perhaps (no particular order - I randomized the sort):
lists-moving.balug.org.
lists-migrating.balug.org.
lists-migration.balug.org.
lists-tmp.balug.org.
lists-mv.balug.org.
lists-move.balug.org.
So ... what'cha all think? I'm thinking *any* of those are better than
lists2. Some best compromise between conveniently short, and
(sufficiently) clear/unambiguous regarding intent/purpose (and avoiding
confusion over what will follow)?
Anyway, feel free to chime in or suggest (it should be a single level
subdomain under balug.org - also can't conflict with DNS RRs (names)
reserved by DreamHost's hosting of the domain. Suggestions/feedback
appreciated. Will need to reach decision and implement fairly soon
(likely within about 4 to 7 days).
[View Less]
Hello, Michael Paoli and the 38 other members of this 40-subscriber
mailing list.
As listadmin, I've just received one of these for each of the three
BALUG mailing lists. Am guessing Dreamhost did a password reset to
comply with a trouble ticket from Michael Hubbard, their customer (last
I heard) for shared-hosting of balug.org.
Reviewing facts I doubtless once knew but forgot again ;-> , I see
Michael Paoli is currently owner ('Regisrant') of domain balug.org.
(Any time you want to …
[View More]make DNS revisions, I stand ready to help.)
So: I've just changed the listadmin passwords for balug-admin,
balug-talk, and balug-announce from the temporary password redacted
below to one that is not guessable but still reasonable to type -- same
password for all three.
Michael P., please call me to get the new password.[1]
We should review policy and procedures. Is there a third core BALUG
person who should hold the listadmin password? Three is better
redundancy than two, and I've found works well enough.
Also, are there people beyond just me who're willing to receive Mailman
notices of held messages and (potentially) other automated
administrative notices? Currently, it's just me.
[1] If you're not Michael P. but can believably impersonate him on the
telephone, please don't call me to get the new password. ;->
----- Forwarded message from mailman(a)listserver-grail.dreamhost.com -----
Date: Tue, 28 Mar 2017 10:53:10 -0700
From: mailman(a)listserver-grail.dreamhost.com
To: rick(a)linuxmafia.com
Subject: Your new balug-admin-balug.org list password
The site administrator at lists.balug.org has changed the password for your
mailing list balug-admin-balug.org. It is now
[redacted]
Please be sure to use this for all future list administration. You may want
to log in now to your list and change the password to something more to your
liking. Visit your list admin page at
http://lists.balug.org/admin.cgi/balug-admin-balug.org
----- End forwarded message -----
[View Less]
So, list stat posting:
https://webmail.rawbw.com/imp/message.php?mailbox=INBOX&index=121022
It was taking so long to show up I was considering reposting.
Did eventually show up.
And, peeking at headers after it did finally come through (I have my
subscription settings so that it also sends to me when I post - I
use that to generally confirm the post came through okay), I find:
Received: from che.dreamhost.com (localhost [127.0.0.1])
by che.dreamhost.com (Postfix) with ESMTP id 12F8110300;
…
[View More] Sun, 2 Apr 2017 15:08:45 -0700 (PDT)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
by che.dreamhost.com (Postfix) with ESMTP id 69B021007C
for <balug-admin(a)lists.balug.org>; Sat, 1 Apr 2017 01:58:23 -0700 (PDT)
So, basicly, it took over 37 hours to get from DreamHost.Com to
DreamHost.com. All the other hops were on the order of around a few
seconds or less. Wish I could say such glitches were exceedingly rare
with DreamHost.Com ... but at least the posts seem to be coming through
again in reasonably timely manner presently.
[View Less]
In reviewing the administrative settings, I see signs that someone might
have powerfully annoyed BALUG admins, and I'm curious if anyone
remembers the history.
This guy's name is first name Rick, second name that I'm writing with
spaces inserted so he won't find this discussion if ego-searching his
own name: 'De Gae tano'. (Remove the space characters.) His e-mail
address is or was rickde gae tano(a)yahoo.com. (Remove spaces. Same
reason.)
What I'm talking about is: 'rickde gae tano(a)…
[View More]yahoo.com' is the sole
address listed as banned from subscribing to balug-admin, and also the sole
address whose postings will be held for moderation on balug-admin. I
removed the first ban, but am keeping the 'hold for moderation' one
while asking if anyone remembers what this is about.
Mailman ban & moderation rosters, in my experience, accumulate some
entries by accident, or by overquick admin action. It's useful to prune
them occasionally.
balug-talk has seven addresses banned from membership for what seem like
antispam reasons. I'm going to remove those; I doubt they're useful:
fred(a)ugramail.ru
info(a)t-shirts.com.hk
loryta11(a)yahoo.com
sayarei111(a)yahoo.fr
shiori_f851(a)yahoo.com.ar
zonal_info1(a)yahoo.co.uk
zonal_info(a)yahoo.co.uk
(Gone.)
Also on balug-talk, Rick D.'s address is the sole address whose postings
would be held for moderation. I'm leaving that while waiting to hear
why.
Basically, was Rick D. some sort of epic pain? What kinda pain?
I'm really curious. (Tell me offlist if that's useful.)
There's an IT consultant in Burlingame of that name.
[View Less]
This is what I mean by 'other signs lately that there may be holes in
the three-way handshake process for some local LUG mailing lists':
A phony address seems to have navigated the subscription process just
using comment spam, somehow.
----- Forwarded message from Mail Delivery System <Mailer-Daemon(a)linuxmafia.com> -----
Date: Sat, 01 Apr 2017 05:00:28 -0700
From: Mail Delivery System <Mailer-Daemon(a)linuxmafia.com>
To: mailman-bounces(a)linuxmafia.com
Subject: Mail delivery …
[View More]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:
silver_first(a)email.bg
SMTP error from remote mail server after RCPT TO:<silver_first(a)email.bg>:
host smtp.email.bg [87.121.0.182]: 550 5.1.1 <silver_first(a)email.bg>:
Recipient address rejected: User unknown in virtual mailbox table
------ This is a copy of the message, including all the headers. ------
Return-path: <mailman-bounces(a)linuxmafia.com>
Received: from localhost ([127.0.0.1] helo=linuxmafia.com)
by linuxmafia.com with esmtp (Exim 4.72)
(envelope-from <mailman-bounces(a)linuxmafia.com>)
id 1cuHhf-0003Ua-2O
for silver_first(a)email.bg; Sat, 01 Apr 2017 05:00:23 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: linuxmafia.com mailing list memberships reminder
From: mailman-owner(a)linuxmafia.com
To: silver_first(a)email.bg
X-No-Archive: yes
Message-ID: <mailman.102.1491048004.13117.mailman(a)linuxmafia.com>
Date: Sat, 01 Apr 2017 05:00:04 -0700
Precedence: bulk
X-BeenThere: mailman(a)linuxmafia.com
X-Mailman-Version: 2.1.13
List-Id: Mailman site list <mailman.linuxmafia.com>
X-List-Administrivia: yes
Sender: mailman-bounces(a)linuxmafia.com
Errors-To: mailman-bounces(a)linuxmafia.com
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: mailman-bounces(a)linuxmafia.com
X-SA-Exim-Scanned: No (on linuxmafia.com); SAEximRunCond expanded to false
This is a reminder, sent out once a month, about your linuxmafia.com
mailing list memberships. It includes your subscription info and how
to use it to change it or unsubscribe from a list.
You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.
In addition to the URL interfaces, you can also use email to make such
changes. For more info, send a message to the '-request' address of
the list (for example, mailman-request(a)linuxmafia.com) containing just
the word 'help' in the message body, and an email message will be sent
to you with instructions.
If you have questions, problems, comments, etc, send them to
mailman-owner(a)linuxmafia.com. Thanks!
Passwords for silver_first(a)email.bg:
List Password // URL
---- --------
conspire(a)linuxmafia.com Hello, we are
http://www.insightvision.biz/cd-dvd-replication-insightvision-biz-faq.php <a href="http://www.insightvision.biz/cd-dvd-replication-insightvision-biz-faq.php">dvd replication manufacturing</a> [url=http://www.insightvision.biz/cd-dvd-replication-insightvision-biz-faq.php]dvd replication manufacturing[/url]
http://linuxmafia.com/mailman/options/conspire/silver_first%40email.bg
----- End forwarded message -----
[View Less]
A few days ago, I said (here):
Recently, someone subscribed each of the SVLUG mailing lists to a
Sympa-software mailing list at a large mailing list site -- a rather
bizarre thing to even attempt to do. I deferred action while wondering
WTF someone was doing, then predictably the next time I posted to
svlug(a)lists.svlug.org received an offlist notice that my 'posting' to
the _other_ remote mailing list was being held for approval (because I
wasn't subscribed to the remote Sympa …
[View More]list, only
'svlug(a)lists.svlug.org').
This clearly was not a tolerable situation, so I removed all of those
subscriptions.
My guess is either mischief or some bizarre variety of user mishap.
Specifically, Sympa mailing list 'blocktogether(a)lists.riseup.net' got
entered as a subscriber to each of the Mailman mailing lists at
lists.svlug.org, a couple of weeks ago. Because I missed one when
deleting those subscriptions, today I'm able to cite it as a specific
example. (I just deleted that last one, too.)
According to https://lists.riseup.net/www/info/blocktogether, it's no
longer an active mailing list. The successor mailing list,
https://lists.riseup.net/www/info/blocktogether-help, says 'Block
Together' is 'a Twitter API tool to help cope with harassment and abuse
on Twitter' -- basically a crowdsourced blocklist.
Perhaps this was part of a low-level effort to monkeywrench Block
Together by throwing other Internet traffic at it.
I'm a little mystified that the unknown agent was able to successfully
complete creation of those subscriptions, because of the three-way
handshake process required to acknowledge that a subscriber address
really wants to carry out that subscription. That is, the only people
able to receive confirmation mail to 'blocktogether(a)lists.riseup.net'
are listadmins of that mailing list, who'd see the confirmation mail in
the held-messages queue. Strange.
And I've seen some other signs lately that there may be holes in the
three-way handshake process for some local LUG mailing lists.
----- Forwarded message from SYMPA <sympa(a)lists.riseup.net> -----
Date: Sat, 01 Apr 2017 13:02:10 +0000
From: SYMPA <sympa(a)lists.riseup.net>
To: mailman-owner-owner(a)lists.svlug.org
Subject: Message distribution: Authorization denied
X-Mailer: Sympa 6.1.22
Your message for list 'blocktogether' (attached below) was rejected.
You are not allowed to send this message for the following reason:
Message distribution for this list is restricted to list moderators.
For further information, please contact blocktogether-request(a)lists.riseup.net
Return-Path: <mailman-owner-bounces+blocktogether=lists.riseup.net(a)lists.svlug.org>
X-Original-To: blocktogether(a)lists.riseup.net
Delivered-To: blocktogether(a)lists.riseup.net
Received: from mail.svlug.org (lists.svlug.org [71.19.144.13])
(using TLSv1 with cipher AES256-SHA (256/256 bits))
(Client did not present a certificate)
by whimbrel.riseup.net (Postfix) with ESMTPS id 53D9FFF8B3
for <blocktogether(a)lists.riseup.net>;
Sat, 1 Apr 2017 13:02:02 +0000 (UTC)
Received: from localhost ([127.0.0.1]:38865 helo=svlug.org)
by mail.svlug.org with esmtp (Exim 4.44 #1) id 1cuIfC-0003gM-B7
for <blocktogether(a)lists.riseup.net>; Sat, 01 Apr 2017 05:01:54 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: lists.svlug.org mailing list memberships reminder
From: mailman-owner-owner(a)lists.svlug.org
To: blocktogether(a)lists.riseup.net
X-No-Archive: yes
Message-ID: <mailman.590.1491051603.12067.mailman-owner(a)lists.svlug.org>
Date: Sat, 01 Apr 2017 05:00:03 -0800
Precedence: bulk
X-BeenThere: mailman-owner(a)lists.svlug.org
X-Mailman-Version: 2.1.6b4
List-Id: <mailman-owner.lists.svlug.org>
X-List-Administrivia: yes
Sender: mailman-owner-bounces+blocktogether=lists.riseup.net(a)lists.svlug.org
Errors-To: mailman-owner-bounces+blocktogether=lists.riseup.net(a)lists.svlug.org
This is a reminder, sent out once a month, about your lists.svlug.org
mailing list memberships. It includes your subscription info and how
to use it to change it or unsubscribe from a list.
You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.
In addition to the URL interfaces, you can also use email to make such
changes. For more info, send a message to the '-request' address of
the list (for example, mailman-owner-request(a)lists.svlug.org)
containing just the word 'help' in the message body, and an email
message will be sent to you with instructions.
If you have questions, problems, comments, etc, send them to
mailman-owner-owner(a)lists.svlug.org. Thanks!
Passwords for blocktogether(a)lists.riseup.net:
List Password // URL
---- --------
smaug(a)lists.svlug.org agoxduho
http://lists.svlug.org/lists/options/smaug/blocktogether%40lists.riseup.net
----- End forwarded message -----
[View Less]