OpenSRS sends out a confirmation of every renewal to the reseller.  It
states:

This message is to confirm the successful renewal of xxxxxxxx.com for 1
year(s).
The new expiration date is 2004-01-08 00:00:00.

So there should be no question of whether a domain was renewed or not, as
the reseller receives the renewal notification so should know for a fact it
renewed and have a copy of the renewal notice.  If the reseller does not
receive the email confirmation order the reseller should immediately follow
up to determine why.

This notice does not contain a reference number in the body of the message.
Maybe it should as it would make it easier to track when you send a copy of
the confirmation notice to the client.

But in answer to your question,  no I do not think that the OpenSRS RWI
goofed up and is responsible for this problem with the client.  This sounds
like a human error, not a system failure.

I know there are some on this list that defends OpenSRS regardless of how
wrong they are but I am not one of those.  Do a search on my email address
and you can verify this. :)



----- Original Message -----
From: "Ashish Pawaskar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, January 18, 2003 11:05 AM
Subject: Re: Disappearing Renewals


> >>down to the fact that Phillip's client was negligent in not renewing the
> >>domain prior to expiration if he wanted to keep the domain name.
>
> PB> Well, it'd be nice if that were the case, but unfortunately it's not.
>
>
> I think the issue at stake here is that:
>
> Phillip renewed a domain, the RWI told him the domain was RENEWED when
> in fact it was not!
>
> Is it just me or does anyone else think that somehow the OpenSRS RWI
> goofed up and is responsible for whatever Phillip is facing from his
> client?
>
> Thanks!
>
> --
> Best regards,
> Ashish Pawaskar
>
> *********************************************************************
>              Internet Wizards - http://www.inwiz.com
> *********************************************************************
>

Reply via email to