Sending registrations informations to current customers is
not spamming
Set a screen giving to your customers the possibility to
add years, collect the money and use the control panel to
extend the period.
It would be done by cloning and customizing the transfer
screens. If the customer is new, just transfer his domains
else renew.
Igael
----- Original Message -----
From: "Tiger Technologies" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 13, 2000 10: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
>
