public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chuck Robey <chuckr@telenix.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] help!
Date: Sun, 11 May 2008 17:35:58 -0400	[thread overview]
Message-ID: <482766BE.6090701@telenix.org> (raw)
In-Reply-To: <1210540067.10485.1.camel@blackwidow.nbk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Albert Hopkins wrote:
> On Sun, 2008-05-11 at 16:39 -0400, Chuck Robey wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I used to get my domain frpm OpenSRS until they put a knife in my back, which
>> has resulted in two things:
>>
>> My being completely separated from "chuckr@chuckr.org", and instead using
>> "chuckr@telenix.org" (thank you, GoDaddy!).  I'm going to see if the BBB is
>> interested in talking to OpenSRS at all.
>>
>> The other one is the one I don't know how to handle: my existing subscriptions
>> to chuckr.org need to be administered (stopped) but only can be done from that
>> dead address, chuckr.org.  I can only use telenix.org, but I can't stop the
>> chuckr.org one from there.
>>
>> How can I stop what has become spam?  I can't see any listing for any human on
>> the lists to help me, in the gentoo lists page.  Does anyone have any ideas?  On
>> many other lists, I've already done it be identifying one person who could
>> access the lists in question, and make sure that chuckr.org no longer existed.
>> Most, they were also willing to give me a complete list of where I was attached
>> to, to aid me in moving them.  I finished the FreeeBSD, maemo, and xorg lists
>> that way, and now we're waiting on gentoo ...
> 
> Ok, I've read this a couple of times.  And, admittedly, I have a hard
> time understanding it in general.  But, specifically, I have been
> wondering WTF this has to do with Gentoo?
> 
> -a
> 
> 

Because Gentoo-user is the last list I haven't been able to fix, or even to
locate a human who is in charge of it (as access to the administrative files).
I was rather hoping that someone in that position might speak up.  It's worked
so far in two of my situations, so I thought to try it again.  It's the kind of
thing where, if you know it';s going to happen in advance, it's very easy to
deal with, but if it surprises you, there doesn't seem to be any way to cancel
the old address in favor of the new one.  I have the new one already working,
it's getting rid of the old one I can't accomplish.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIJ2a+z62J6PPcoOkRAixTAJ9qhbVMdTCZQHwrTop8tIFCiMxkqACfQoDC
6vlUCWz26jCClGRwnCfHSTM=
=KUk7
-----END PGP SIGNATURE-----
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-05-11 21:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-11 20:39 [gentoo-user] help! Chuck Robey
2008-05-11 21:07 ` Albert Hopkins
2008-05-11 21:35   ` Chuck Robey [this message]
2008-05-11 21:54   ` Chuck Robey
2008-05-11 23:14 ` Daniel Iliev
2008-05-11 23:52   ` Chuck Robey
  -- strict thread matches above, loose matches on Subject: below --
2011-10-05  4:52 [gentoo-user] Help! Lavender
2011-10-05  6:48 ` Yohan Pereira
2011-10-05  8:30 ` Neil Bothwick

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=482766BE.6090701@telenix.org \
    --to=chuckr@telenix.org \
    --cc=gentoo-user@lists.gentoo.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