Did
the other one complete for you, or is it still in an inconsistent
state?
Charles Daminato
OpenSRS Product Manager
Tucows Inc. -
[EMAIL PROTECTED]
-----Original Message-----Sorry again,
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]
Sent: July 12, 2002 10:52 AM
To: [EMAIL PROTECTED]
Subject: Re: Bug in transfer away code? (.info) - sorry still a problem
the problem is still partly existing:
- the client did the transfer and entered the 'auth code' (wrong or false, I can not proof it)
- the client got an error (not a big problem, but should not happen)
- the transfer away was completed within 60 minutes and WHOIS resolves
- I did not get any notification (I have checked my mail logs twice - THIS IS A PROBLEM)
- the domain is still in my account (THIS IS A PROBLEM TOO, because I wouldn't even notice that a domain has gone away - in this case I knew it beforehand)
Anybody else noticed the same problem?
I am especially worried about the fact, that a domain which is not locked might be 'stolen' by somebody else,
and I even would not get a message 'domain has been transferred away'
Matthias
Not the case. The gaining registrar must approve/authorize a transfer. By the time it gets to the "Transfer Away" stage, that first step has already occured.
We must abide by registry rules, which is "AUTO ACK" after 5 days. We give the customer the ability to cancel/approve before hand, but they must have the proper AUTH code. In this case, the customer APPROVED the transfer away - but didn't use the correct code so it wasn't automated in our system (had to wait until our system updates)
