Jose, It's wise to inform your clients that they need the AUTH_CODE (as it's called - an EPP-ism) to complete their transfer (it's used on the usual "Transfer Confirmation" page).
If they're transfering away, the code is available via the Manage interface (public manage will do, or a recently updated manage.cgi). We're building a feature now that will enable you to email the AUTH_CODE to the registrant (in the current cycle, slated at the moment for mid-late August). This will be the same as the "Email Password" (including link for domain, and associated configurable email templates) functionality. Charles Daminato TUCOWS Product Manager [EMAIL PROTECTED] On Mon, 1 Jul 2002, Jose Luis Moya wrote: > I have just realized after getting complaints from a client that new > transfers for info.. need our client to include a registration code PRIOR to > accepting.... something which maybe I should have had... but never heared > before, nor found on the documentation. > > Now questions: > > - those this means that I am suppose to tell my clients to get the code from > his current registrar "PRIOR" to requesting me the trasnfer, then request me > the transfer... then accept mine/OpenSRS (it looks very OpenSRS!!) including > that code... and then wait to see if his register asks for another > confirmation???? > should I forget info transfers straight away and say they are not available? > > - in the opposite case if someone registers a .info domain through me and > the wants to walk away... where I am suppose to get that code that I am > suppose to give him? > > Thanks. > > > Jose Luis > >
