From: dann frazier <dannf@dannf.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Thibaut VARENE <varenet@parisc-linux.org>,
linux-parisc@vger.kernel.org, taggart@lackof.org,
bame@riverrock.org
Subject: Re: decommissioning parisc-linux.org
Date: Thu, 9 Feb 2012 13:49:31 -0700 [thread overview]
Message-ID: <20120209204931.GD22332@dannf.org> (raw)
In-Reply-To: <yq1mx8rn7cy.fsf@sermon.lab.mkp.net>
On Thu, Feb 09, 2012 at 02:18:21PM -0500, Martin K. Petersen wrote:
> >>>>> "Dann" == dann frazier <dannf@dannf.org> writes:
>
> >> What's the status of @p-l.o email addresses? I'm receiving a fair bit
> >> of email on this domain, and I think others do too, if we need to
> >> move on elsewhere it'd be nice to have a little headstart... ;)
>
> Dann> My assumption is that mail will follow the domain.
>
> I would like something to be done with the mail situation. It totally
> sucks being secondary mx since I get to deal with all the spam bounces
> and blacklistings.
>
> We can either move mail forwarding to my machine wholesale so I can fix
> things or we can leave it on palinux and discontinue having me as
> secondary. I'm happy either way.
Well, my vote is that we take you up on that offer and move it to you,
at least while things are in flux. Only problem I see is that some
people don't forward their mail off of palinux, but its probably a
good idea to deprecate that RSN.
> I'm also happy to continue providing DNS. I would like the ability to
> update the zone files, though. I would have fixed the mail problems long
> ago if I could...
I don't see any reason we wouldn't let you take over even primary if
you wanted to. Frankly, I'm surprised we hadn't given you whatever
privs you needed already - really just seems like an oversight on our
part, my apologies.
next prev parent reply other threads:[~2012-02-09 20:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 14:33 decommissioning parisc-linux.org dann frazier
2012-02-08 22:16 ` Thibaut VARENE
2012-02-08 23:47 ` John David Anglin
2012-02-09 1:53 ` John David Anglin
2012-02-09 14:54 ` John David Anglin
2012-02-09 15:41 ` Paul Bame
2012-02-09 17:55 ` dann frazier
2012-02-11 19:11 ` John David Anglin
2012-02-11 22:12 ` Thibaut VARENE
2012-02-11 22:41 ` John David Anglin
2012-02-11 23:26 ` Thibaut VARENE
2012-02-11 23:29 ` Carlos O'Donell
2012-02-12 0:25 ` John David Anglin
2012-02-14 18:05 ` dann frazier
2012-02-14 18:31 ` Thibaut VARENE
2012-02-14 18:33 ` Carlos O'Donell
2013-01-23 21:17 ` dann frazier
2013-01-23 23:14 ` John David Anglin
2013-01-23 23:32 ` dann frazier
2012-02-09 17:56 ` dann frazier
2012-02-09 19:18 ` Martin K. Petersen
2012-02-09 20:49 ` dann frazier [this message]
2012-02-12 14:38 ` James Bottomley
2012-02-12 14:49 ` James Bottomley
2012-02-12 20:01 ` James Bottomley
2012-02-12 22:47 ` Carlos O'Donell
2012-02-12 22:56 ` John David Anglin
2012-02-13 2:22 ` Carlos O'Donell
2012-02-13 5:20 ` James Bottomley
2012-02-13 22:26 ` Carlos O'Donell
2012-02-13 4:05 ` Grant Grundler
2012-02-13 5:19 ` James Bottomley
2012-02-14 18:06 ` dann frazier
2012-02-13 11:23 ` Thibaut VARENE
2012-02-14 13:41 ` Thibaut VARENE
2012-02-14 18:06 ` dann frazier
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=20120209204931.GD22332@dannf.org \
--to=dannf@dannf.org \
--cc=bame@riverrock.org \
--cc=linux-parisc@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=taggart@lackof.org \
--cc=varenet@parisc-linux.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;
as well as URLs for NNTP newsgroup(s).