14 Oct
2020
14 Oct
'20
3:08 a.m.
Hi,
I posted to <rescue at sunhelp.org> and saw my message got stuck in the mail
queue. Upon a further inspection I saw that the domain has expired along
with `mrbill.net' where the nameservers used to reside and both have been
taken by someone else, taking the name service down for `sunhelp.org'. I
can still reach Bill Bradford's personal page when I connect to the server
by its IPv4 address at: <http://184.94.207.190/>.
I do hope nothing bad has really happened to Bill in these difficult
times. Anybody knows?
Maciej
14 Oct
14 Oct
3:46 a.m.
Umm, Bill passed away a bit over a year ago. May he rest in peace.
He had said that there was some sort of plan to hand off Sunhelp, but I'm
not sure what happened.
Patrick Finnegan
On Wed, Oct 14, 2020, 06:08 Maciej W. Rozycki via cctalk <
cctalk at classiccmp.org> wrote:
Hi,
I posted to <rescue at sunhelp.org> and saw my message got stuck in the
mail
queue. Upon a further inspection I saw that the domain has expired along
with `mrbill.net' where the nameservers used to reside and both have been
taken by someone else, taking the name service down for `sunhelp.org'. I
can still reach Bill Bradford's personal page when I connect to the server
by its IPv4 address at: <http://184.94.207.190/>.
I do hope nothing bad has really happened to Bill in these difficult
times. Anybody knows?
Maciej
4:51 a.m.
On Wed, Oct 14, 2020 at 11:08:00AM +0100, Maciej W. Rozycki via cctalk wrote:
Hi,
I posted to <rescue at sunhelp.org> and saw my message got stuck in the mail
queue. Upon a further inspection I saw that the domain has expired along
with `mrbill.net' where the nameservers used to reside and both have been
taken by someone else, taking the name service down for `sunhelp.org'. I
can still reach Bill Bradford's personal page when I connect to the server
by its IPv4 address at: <http://184.94.207.190/>.
I do hope nothing bad has really happened to Bill in these difficult
times. Anybody knows?
He was an old friend of mine he died August 15 2019 of cancer. :-(
https://www.gray329.org/bro-william-c-bradford-1974-2019/
Maciej
Diane
--
- db at FreeBSD.org db at db.net http://www.db.net/~db
5:20 a.m.
On Wed, 14 Oct 2020, Diane Bruce wrote:
He was an old friend of mine he died August 15 2019 of
cancer. :-(
https://www.gray329.org/bro-william-c-bradford-1974-2019/
So sorry to hear that. :(
Maciej
6:43 p.m.
On 10/14/20 4:08 AM, Maciej W. Rozycki via cctalk wrote:
Hi,
Hi,
I posted to <rescue at sunhelp.org> and saw my
message got stuck in
the mail queue.
When did you send your message? I'm trying to judge when the problem
started.
Upon a further inspection I saw that the domain has
expired along with
`mrbill.net' where the nameservers used to reside and both have been
taken by someone else, taking the name service down for `sunhelp.org'.
Eh ... sunhelp.org doesn't expire for a couple of years yet. The
problem is that it uses mrbill.net for DNS, which did expire and seems
to have been taken over by undesirables.
I can still reach Bill Bradford's personal page
when I connect to
the server by its IPv4 address at: <http://184.94.207.190/>.
Thanks to John's quick thinking, it's now possible to hot wire things so
that you can get to sunhelp.org, et al.
The hot wiring that I did seems to have been sufficient to allow email
to flow to sunhelp.org. I've since sent a message to a few people
inquiring about the current state of the ongoing rescue operation.
The last I knew, some of Bill's co-workers were going to take things over.
If anyone cares to similarly hot wire things on their end, I configured
my recursive DNS servers to forward Bill's domains to John K.'s DNS
server (192.80.49.4). I also configured my email server to route
sunhelp.org directly to ohno.mrbill.net.
--
Grant. . . .
unix || die
7:07 p.m.
On Wed, 14 Oct 2020, Grant Taylor via cctalk wrote:
Last Mon, Oct 12th. The last message I received from the mailing list
was on Oct 1st. WHOIS has this though:
Domain Name: MRBILL.NET
Registry Domain ID: 1373333_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2020-10-11T07:01:46Z
Creation Date: 1996-10-11T04:00:00Z
Registry Expiry Date: 2021-10-10T04:00:00Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse at namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS101.REGISTRAR-SERVERS.COM
Name Server: DNS102.REGISTRAR-SERVERS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
so I take it the original domain went down on Oct 11th at ~7am; OTOH
sunhelp.org itself has yet two years to go (as you have also observed).
I suppose the list server relies on the same nameservers in a way that
prevents e-mail distribution from happening. I have since resubmitted the
same message manually to sunhelp.org's SMTP receiver (the original message
is still in the outgoing mail queue:
smtp/sunhelp.org:
B/W/23993316: (196 tries, expires in 2d17h) smtp; 466 (No DNS response for host:
sunhelp.org; h_errno=0)
) to see what happens and got a DSN ack even, but the message did not get
through. So local hot wiring of name resolution (which I suppose could be
as easy as adding a /etc/hosts entry rather than going through the hoops
of setting up a manipulated name server) might be good enough to get at
the web pages, but not to get the list going.
Maciej
I posted to
<rescue at sunhelp.org> and saw my message got stuck in the mail
queue.
When did you send your message? I'm trying to judge when the problem started.
I can still
reach Bill Bradford's personal page when I connect to the server
by its IPv4 address at: <http://184.94.207.190/>.
Thanks to John's quick thinking, it's now possible to hot wire things so that
you can get to sunhelp.org, et al.
The hot wiring that I did seems to have been sufficient to allow email to flow
to sunhelp.org. I've since sent a message to a few people inquiring about the
current state of the ongoing rescue operation.
The last I knew, some of Bill's co-workers were going to take things over.
If anyone cares to similarly hot wire things on their end, I configured my
recursive DNS servers to forward Bill's domains to John K.'s DNS server
(192.80.49.4). I also configured my email server to route sunhelp.org
directly to ohno.mrbill.net.
7:18 p.m.
On 10/14/20 8:07 PM, Maciej W. Rozycki wrote:
Last Mon, Oct 12th. The last message I received from
the mailing
list was on Oct 1st.
The last message I see (prior to mine) from geeks at sunhelp was last
Thursday, October 8th.
so I take it the original domain went down on Oct 11th
at ~7am; OTOH
sunhelp.org itself has yet two years to go (as you have also observed).
*nod*
I suppose the list server relies on the same
nameservers in a way
that prevents e-mail distribution from happening.
I don't think so. At least I thought that the hot wiring that I did to
my mail server only effected /sending/ of email.
The changes I made to the DNS server would have effected /receiving/ of
email.
I have successfully sent a message to the geeks at sunhelp mailing list
/and/ received my copy of said message from said mailing list.
I have since resubmitted the same message manually to
sunhelp.org's
SMTP receiver (the original message is still in the outgoing mail
queue:
smtp/sunhelp.org: B/W/23993316: (196 tries, expires in 2d17h) smtp;
466 (No DNS response for host: sunhelp.org; h_errno=0)
) to see what happens and got a DSN ack even, but the message did
not get through.
Were you sending a message to geeks at sunhelp or a different address?
I accidentally sent a message to geeks at sunhelp from the wrong address
and did receive the DSN from Mailman stating that I wasn't subscribed
(with that address) and thus the message was rejected.
So local hot wiring of name resolution (which I
suppose could be as
easy as adding a /etc/hosts entry rather than going through the hoops
of setting up a manipulated name server) might be good enough to get
at the web pages, but not to get the list going.
Ya ... email tends to be more reliant on DNS. At least unless you
explicitly tell it to not use it for specific domains. And that's
exactly what I did. I hard (hot) wired email routing so that email for
sunhelp.org goes to ohno.mrbill.net, which is resolvable do to my DNS
hot wiring (forwarders).
You can probably do similar or configure the email routing to go to the
IP directly.
--
Grant. . . .
unix || die
22 Oct
22 Oct
9:07 p.m.
On Wed, 14 Oct 2020, Grant Taylor via cctalk wrote:
It was to <rescue at sunhelp.org>. The resubmitted message eventually made
it through last Tue, Oct 20th, after a week of being held:
Received: from ohno.mrbill.net ([184.94.207.190]:57765 "EHLO ohno.mrbill.net"
rhost-flags-OK-FAIL-OK-FAIL) by eddie.linux-mips.org with ESMTP
id S23991030AbgJTMxVN8USJ (ORCPT <rfc822;macro at linux-mips.org>);
Tue, 20 Oct 2020 14:53:21 +0200
Received: from ohno.mrbill.net (localhost [127.0.0.1])
by ohno.mrbill.net (Postfix) with ESMTP id E173B1E0DF9;
Tue, 13 Oct 2020 22:55:12 -0500 (CDT)
X-Original-To: rescue at sunhelp.org
Delivered-To: rescue at mrbill.net
Received: from cvs.linux-mips.org (eddie.linux-mips.org
[148.251.95.138]) (using TLSv1 with cipher AES256-SHA (256/256 bits))
(No client certificate requested) by ohno.mrbill.net (Postfix) with
ESMTPS id 84C0D1E0915 for <rescue at sunhelp.org>; Tue, 13 Oct 2020
22:55:10 -0500 (CDT)
which I think does coincide with the revival of mrbill.net services:
Domain Name: MRBILL.NET
Registry Domain ID: 1373333_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2020-10-19T15:39:08Z
and makes me conclude my suspicion was right.
I wish it was the case. The admin of linux-mips.org, a friend of mine,
has vanished since the outbreak of the COVID-19 pandemic in Europe last
March -- I do hope nothing wrong has happened to him and he does surface
sometime.
Anyway, he's the only one who can remove a stale /etc/hosts entry here
for vger.kernel.org, which prevents me from posting to any Linux kernel
mailing lists hosted there unless I resort to some horrible hacks, which
in turn tend to randomly break sending e-mail elsewhere. Sigh...
Maciej
I suppose the
list server relies on the same nameservers in a way that
prevents e-mail distribution from happening.
I don't think so. At least I thought that the hot wiring that I did to my
mail server only effected /sending/ of email.
The changes I made to the DNS server would have effected /receiving/ of email.
I have successfully sent a message to the geeks at sunhelp mailing list /and/
received my copy of said message from said mailing list.
I have since resubmitted the same message
manually to sunhelp.org's SMTP
receiver (the original message is still in the outgoing mail queue:
smtp/sunhelp.org: B/W/23993316: (196 tries, expires in 2d17h) smtp; 466 (No
DNS response for host: sunhelp.org; h_errno=0)
) to see what happens and got a DSN ack even, but the message did
not get through.
Were you sending a message to geeks at sunhelp or a different address? So local hot
wiring of name resolution (which I suppose could be as easy as
adding a /etc/hosts entry rather than going through the hoops of setting up
a manipulated name server) might be good enough to get at the web pages, but
not to get the list going.
Ya ... email tends to be more reliant on DNS. At least unless you explicitly
tell it to not use it for specific domains. And that's exactly what I did. I
hard (hot) wired email routing so that email for sunhelp.org goes to
ohno.mrbill.net, which is resolvable do to my DNS hot wiring (forwarders).
1482
days inactive
1491
days old
7 comments
4 participants
participants (4)
-
cctalk＠gtaylor.tnetconsulting.net -
db＠db.net -
macro＠linux-mips.org -
pat＠vax11.net