Completely understand - here's what I would like to see in the process...
Automated/Server Based Renewals
Everyday, our system will compile a list of domain names that are up for
renewal within [90] days. These will be presented to the RSP via the RWI
so that the RSP can pick out any domains that should not be processed for
renewal. The remainder would be approved and submitted for processing.
Once approved by the RSP, our system would send out a message on the RSPs
behalf notifying the registrant that they need to renew their registration
with the RSP at a URL the RSP specifies. The RSP has the choice of sending
out a stock email that we would generate (fill in the blanks type stuff)
or write their own message. The registrant would process the renewal via
the RSPs web site or other processes.
Of course this would be completely opt-out to allow RSPs to process
renewals using their own systems via the API....
On Wed, 13 Sep 2000, Chuck Hatcher wrote:
> I am absolutely and positively opposed to anyone else sending an email
> message with my or my company's email address listed as the From: address!
>
> I understand OpenSRS has to have a procedure in place for the direct
> notification of domain name registrants before the expiration (or at least
> before the deletion) of their domains. But hopefully any email generated
> will include enough information to determine its origin and purpose.
>
> (One thing I dislike about Paypal is that the payment notices appear to be
> sent by the party making the payment.)
>
> In the case you mentioned, I think if the customer wants you to expire the
> domain, maybe you should ask him for the password and change the contact
> email addresses so he is not bothered further.
>
>
> ----- Original Message -----
> From: "Tiger Technologies" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, September 13, 2000 4:13 PM
> Subject: Re: Expirations and renewals - WAS: Re: Probably a silly question
> but...
>
>
> > At 9/13/00 12:12 PM, adam wrote:
> >
> > >As far as I'm aware, the proposed model for gTDL exprirations is to send
> a
> > >renewal notice to the *RSP* a set period before the expiration. If the
> > >domain
> > >still isn't renewed by another set period, OpenSRS will "take over" and
> send
> > >a renewal notice direct to the client.
> >
> > That's fine as a default behavior, but there needs to be a way for RSPs
> > or domain owners to prevent the OpenSRS message for a certain domain if
> > the RSP/domain owner knows that the domain should not be re-registered.
> >
> > For example, we register domain names on the customer's behalf as part of
> > our Web hosting service. In at least one case, the customer has
> > specifically asked us to cancel the service and not renew the domain
> > name. We'll look pretty stupid if the ex-customer starts getting urgent
> > renewal notices (that appear to be from us) next year, with no way for us
> > to stop them coming.
> >
> > Keep in mind that sending messages to a customer when the customer has
> > asked not to receive them may be a violation of some privacy policies, or
> > even laws.
> >
> > Giving the RSP and/or domain owner the power to turn off renewal messages
> > when they would be inappropriate would seem to be a requirement.
> >
> > --
> > Robert L Mathews, Tiger Technologies
> >
> >
>
Thanks,
-rwr
Ross Wm. Rader
Director Product Management,
Channel Platform Group
Tucows Inc.
[EMAIL PROTECTED]
t. 416.535.0123 x335
f. 416.531.5584
"Embrace the cow, love the cow.
And remember, Winsock means love."
