At 07:10 PM 9/29/00 +0000, you wrote:
> > - offering an "opt in" managed renewal service; once configured this
> > service will automatically send email to the billing contact for all names
> > that are coming up for renewal for any RSP. This message will be fully
> > customizable by the RSP. It will send messages out at -60 and -30 days. A
> > note will be appended to notes field for the name record to show that the
> > email was sent
> >
>Just to clarify - I presume that these messages will be coming
>from "[EMAIL PROTECTED]"?
No - the "reply-to" for these messages would be set by the RSP.
> > At the renewal date, if the name has not been renewed, Tucows will send an
> > email message to the admin and billing contacts, advising them that
> this is
> > their final notice, and that if they do not renew the name within 15 days,
> > they risk losing it. This message will refer them to their RSP for
> renewal.
> > RSPs will be allowed to manually stop this message from going out on a
> "per
> > name" basis.
> >
>Pardon my ignorace, but I don't understand the "per name" bit.
It means that they would have to change it for each name if they wanted to
change it.
>Also, I think
>that there needs to be protection for the registrant(s) built-in here - if
>the RSP turns off this message, the registrant(s) run the risk of losing
>their domain through the inaction of the RSP.
Right - There is only so far we can go in protecting the registrant, yet
empowering the RSP. I feel the current spec gets the balance right. It
would take a pretty patient and savvy RSP to nab a name by exploiting this
process. Not to mention the fact that as soon as the registrant contacted
us, we would see that the RSP turned off notification, and well...
Regards,
sA
Scott Allan
Director OpenSRS
[EMAIL PROTECTED]
