I get the following email:
**From:** "OpenSRS Transfers" <XXXXXXXXXXXXXXXXXXXX> > **To:** <XXXXXXXXXXXXXXXXXXX> > **Subject:** Transfer Request for conman.org > **Date:** Fri, 30 Nov 2001 15:54:08 -0500 (EST) >
A request has been received to transfer the domain conman.org to XXXXXXXXXXXXXXXXXXXXX, Inc., an authorized reseller of the registrar Tucows. This request was entered at Fri Nov 30 15:53:11 2001 by XXXXXXXXXXX. Note that your nameservers will not change as a direct result of this transfer.
This acknowledgement of transfer will be processed by Tucows Inc, an ICANN accredited registrar on behalf of XXXXXXXXXXXXXXXXXXXXX, Inc. If this is a valid request and you wish to approve this transfer, please visit the following url and follow the instructions:
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
You will need to enter the following information to complete the transfer: > Domain Name: conman.org > Password: XXXXXXXXXX
If you do not wish to approve this transfer, you may simply ignore this message and the request will be cancelled, or you can use the Domain Name and Password above to cancel the transfer.
Accepting this transfer will change the registrar of record for your domain from its current registrar, to Tucows/OpenSRS; it may also change some of the contact information. If you are receiving this email, you should have initiated, or at least been aware of this request already. If this is the first time that you've heard of this, do not accept the transfer until you are satisfied that the request is legitimate.
Thank you.
XXXXXXXXXXXXXXXXXXXXXXXXXX, Inc. and Team Tucows
This is interesting. Someone is attempting to move my registration for conman.org from Network Solutions [1] to OpenSRS [2]. Someone by the name of “XXXXXXXXXXX.”
Now, I had been thinking of moving my registration away from Network Solutions but have held off until I've renewed and now I suppose I can look into doing so. I called Mark [3] just to see if he may have initiated it (just on the off chance, you know?). Nope. He was like “NO! NO! Say `No!' to the request!” And when asked if he heard of or possibly knew who “XXXXXXXXXXX” might be, he didn't know.
So I turned to the all knowing Google [4] and asked about “XXXXXXXXXXX.” A few minutes poking around showed him as the owner of XXXXXXXXXX. Aha! I thought. He made a mistake in making the request transfer. So that explains that.
A quick email to him and the situation is clarified.
XXXXXXXXXXX wrote me today informing me that it was not his mistake at all, but that of his hosting company and that somehow they mixed up the domain. I apologize for the assumption that it was XXXXXXXXXXX's mistake (and the quick email wasn't as clarified as it could have been, I suppose).
I'm also agonized over how to handle his politely sent request to remove this entry. I would like to, but doing so makes for a hole in my journal, and it could potentially break links to that page (not that there are any) but I can understand XXXXXX's position on this.
Yet another email from XXXXXXXXXXX asking whem I'm going to remove this entry.
I don't want to remove this entry. And obviously, I'm not toing to remove this entry. So I went through, striking out any mention of XXXXXXXXXXX. It will take a while for this to flush out of Google [5] (where this page is the third result when looking for XXXXXXXXXXX).
[1] http://www.networksolutions.com/