From: "Theodore Ts'o" <tytso@mit.edu>
To: debian-devel@lists.debian.org, linux-kernel@vger.kernel.org,
lf_staff@linux-foundation.org,
Head Bubba <head.bubba@credit-suisse.com>,
Marc MERLIN <marc@merlins.org>, Reuben Thomas <rrt@sc3d.org>,
Andreas Dilger <adilger@sun.com>, Alex Tomas <alex.tomas@sun.com>,
Aaron Whitehouse <lists@whitehouse.org.nz>
Subject: Please ignore mail bounces for tytso-mit@thunk.org
Date: Thu, 27 Dec 2007 10:46:14 -0500 [thread overview]
Message-ID: <E1J7uw2-0002HJ-60@closure.thunk.org> (raw)
Hi all, some of you may have noticed have received mail bounces from
mail that you sent me from MAILER-DAEMON@mit.edu that referenced failure
to deliver mail to tytso-mit@thunk.org, for example:
<tytso-mit@thunk.org>... Deferred: Connection timed out with thunk.org.
Message could not be delivered for 3 days
Message will be deleted from queue
Some of you may have also noticed that mail sent to tytso@thunk.org may
have also started bouncing in a similar fashion.
My apologies. Unfortunately thunk.org failed on December 23rd, and
because I and other people who might have been able to gain physical
access to the colo facility (where the server is located) have been
travelling for the holidays, I haven't been able to get the machine back
up as quickly as I would like. Please rest assured that mail sent to
tytso@mit.edu is being read, despite the bounce messages.
tytso-mit@thunk.org was a backup copy of mail sent to tytso@mit.edu that
I established a while back as a backup way of reading my mit.edu mail
after my mit.edu IMAP server was down for 4 days.[1]
In any case, mail service to tytso@mit.edu has not been interrupted; I
am reading mail sent there, and it is the primary way that I should be
contacted for any Linux/Open Source related matters.
Mail to tytso@thunk.org is currently being held in mail queues, and
depending on how SMTP mailers have been configured, may have started
getting returned to sender. A few debian mailing lists are set to feed
tytso@thunk.org, and some people use it to contact me, although I
generally have not published it as a contact address.
I'm hopeful that I will get thunk.org restored fairly quickly, and
apologize for any inconvenience/confusion this may have prompted.
Regards,
- Ted
[1] An interesting story, which involved the MIT I/T staff waiting 36+
hours for a Solaris ufs fsck to finish on a 1TB filesystem, before
aborting it in frustration and using other methods to restore service,
but for another day.
reply other threads:[~2007-12-27 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1J7uw2-0002HJ-60@closure.thunk.org \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=alex.tomas@sun.com \
--cc=debian-devel@lists.debian.org \
--cc=head.bubba@credit-suisse.com \
--cc=lf_staff@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@whitehouse.org.nz \
--cc=marc@merlins.org \
--cc=rrt@sc3d.org \
/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
all inboxes | Powered by JetHome®