Ok....
in this case, this is what happened:
1)
Your customer went to the "transfer away" page to approve the transfer, but
entered it incorrectly (which caused the error). This does nothing - had
he entered the correct information, the transfer would have
completed.
2) The
transfer completes automatically after 5 days, unless someone explicitly cancels
it (via the "Transfers Away" interface, for example). In this case, the
domain simply goes
3) Our
system, once per day, checks the status of transfers to see where they are at -
this process has not run since this request was "confirmed" (even though our
system sees a "yes", we didn't send a correct "yes" to the registry so the
manual intervention part failed).
This
should be cleared up today in our system :)
Charles Daminato
OpenSRS Product Manager
Tucows Inc. -
[EMAIL PROTECTED]
-----Original Message-----Chuck
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]
Sent: July 10, 2002 10:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Bug in transfer away code? (.info)
I'd need to know the domain name to be sure.
Will send it off-list.
.
But note that many of our transfer processes work asynchronously (i.e.
cron jobs that run daily) for checking transfer statuses, etc. If he
entered the incorrect auth_code when he was approving the "Transfer Away"
section it would not have completed the transfer (from our side).
However, if the 5 day window has passed after the transfer request was
started (which is likely the case), the registry would have completed the
transfer and our system will pick up on that today
Perhaps a language problem, I try it in other words:
When the client had entered the 'auth code' (which seems to have been correct)
he got the error message (transfer not possible ...)
But when I checked the whois at Afilias about 60 minutes later, the transfer was already completed.
So I think the bug is not concerning the transfer itself, but for any strange reason there is
an error displayed, even if the transfer is successful.
Matthias
