From: "Dave Täht" <dave@taht.net>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] bufferbloat email list server upgrade going slow and badly
Date: Mon, 4 Jan 2016 15:38:05 -0800 [thread overview]
Message-ID: <568B025D.70808@taht.net> (raw)
all the bufferbloat.net servers are in the process of migrating to a
new co-location facility. the lists - if not the archives - should be
alive again, at least.
There is a stupid bug somewhere stopping the archived pages from
making the web.
I am concerned if anyone's bloat email is now auto-ending up in a spam
folder? (if so, please send response privately) (this email is also a
test)
The redmine webserver move is troublesome, also.
Further more, the mailman web service is under persistent attack by
a set of 286 (so far) ips flooding it with subscription requests, and
linode itself has been under enormous attack over the holidays...
there will be ssl updates and the like once all this is sorted but it
might take a week or two more. I might give up and try another co-lo also.
In the meantime, why not top it all off with breakfast at milliways?
next reply other threads:[~2016-01-04 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 23:38 Dave Täht [this message]
2016-01-05 0:10 ` Stephen Hemminger
2016-01-05 0:30 ` Dave Täht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=568B025D.70808@taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox