hey tiger technologies, guess what ?
it seems you were right to the point :-)
and OpenSRS/Tucows listened again *and* acted immediately. thank you all.
kind regards philippe, http://InternetRoot.com
--- *** ---
At 11:38 Uhr -0500 09.02.2001, Charles Daminato wrote:
>We had a huge internal discussion on this issue. What we came up with was,
>there is no intrinsic value in blocking user's access from manage.cgi or
>renew.cgi even if they are expired (they just can't change their
>nameservers).
>
>With that in mind, all users that have expired can now login to manage or
>renew to complete the process. So no need to move these domains, n'est pas?
>
>Charles Daminato
>Product Manager (ccTLDs)
>Tucows Inc. - [EMAIL PROTECTED]
--- *** ---
>At 2/7/01 2:02 AM, Bill Gerrard wrote:
>
>>If a domain reaches its expiration date without being renewed, the
>>process of OpenSRS disabling the domain also makes it inaccessible via
>>manage.cgi and renew.cgi, so there is no way for your customer to renew
>>their domain through these scripts. You must manually renew the domain via
>>the RWI (view active domains). I have been told they (OpenSRS developers)
>>are looking into a better workaround for this problem.
>
>Hmmm, maybe I'm missing something, but isn't the easiest solution to
>simply remove this restriction completely and allow customer logins until
>the domain is actually deleted? I don't see the point of preventing
>people from logging in.
>
>If the goal is to prevent people from getting 40 days of free service,
>maybe a future version of the scripts could prevent people from doing
>anything except renewing when it's in that state -- but even that seems
>like extra work for no big gain. If people really care enough about their
>domain that they're trying to make last-minute changes, they're probably
>going to renew it.
>
>So, why not just remove the "no login" restriction? What am I missing?
>
>--
>Robert L Mathews, Tiger Technologies
