Jump to content

ICANN requires to send e-mails on my behalf


hostservice_71

Recommended Posts

ICANN [sarcasm]in their ultimate wisdom and claim of the internet that apparently is accepted by most sheep on this planet [sarcasm off] has decided to make strict rules on when owners of domains need to be notified.

 

What happens now is that we have an account for instance with Enom. Also we run multiple website with different hosting products that all run whmcs and all register at the same Enom acocunt, to prevent extra costs and multiple accounts with them.

 

Recently Enom believes they have the right to send my customers e-mail in English (which we do not use) to my clients with renewal notices. Apart from the fact that I believe it is not of their business (and they claim they just follow the rules of icann) this means that many customers get send mail that seems to come from a different hosting party!

 

I asked them to stop immediately but ey said in order to do that we need to give them proof and templates of mail we send out, including the frequency, that needs to be according to ICANN regulations.

 

This is a quote:

1 - A minimum of two notifications are required approximately 1 month and 1 week prior to expiration. If a domain expires, one additional notice with renewal instructions is required within 5 days after the expiration date.

2- Renewal notices must be sent to the registrant, not just an account holder.

 

Am I overlooking something or is WHMCS not icann proof? Where can I set all these notices?

Edited by hostservice_71
Link to comment
Share on other sites

you may want to read the thread below as it might provide you with some further info...

 

http://forum.whmcs.com/showthread.php?96323-eNom-Reseller-Renewal-Information

http://blog.whmcs.com/?t=96330

 

As mentioned in my blog post a couple of weeks ago, we have been working very closely with eNom to make sure we fully address this. As is often the case however, we weren't aware of this change as far in advance as we would have liked. Nevertheless, I can confirm that the next release of WHMCS will be fully compliant with the new ICANN requirements and ensure domain providers using WHMCS can opt-out and handle the domain renewals notice process internally through WHMCS in a fully compliant way.

 

In order to do this we are implementing the following changes:

 

1. The default domain expiry email notice sending rules will be setup as per ICANN rules

2. It will be possible to configure separate email templates to be used for before and after the domain expiry date passes

3. Renewal notices will be sent to the domain registrant contacts email address (sending them to the clients profile email address is not enough)

4. A log will be kept of what domain renewal notices have been sent and when, with the ability to easily provide this to ICANN or a domain registrar upon request

 

I can also confirm that currently entering a negative number in the renewal notice reminder days to send values will not work as renewal notices are only sent to Active domains, and once a domain has expired its status gets changed to Expired.

 

If you have any further questions, please open a ticket and a member of our team will be able to put you in touch with someone who can answer your questions.

 

Matt

Link to comment
Share on other sites

Thanks Brian...when do we expect this release?

I had a feeling you might ask that question! :)

 

if they're talking about v6, then it is due to go to beta before a public release is made available - no specific dates have been made public (other than 2015), but I would imagine it would be in beta for a while, so at best it would still be a month or two before a full release is available...

 

personally, it wouldn't surprise me to see at least one more v5.3.xx release before the v6 full release.

 

I should also add that I don't work for WHMCS (hurrah!) - so I don't have any inside info on this, and i'm not speaking for them - just reading between the lines of their limited statements!

Link to comment
Share on other sites

Is WHMCS on holidays?! I'm waiting!

 

Today a customer with over 60 domains names is threatening to leave because of these unsolicited e-mails from Enom, send on our behalf.

 

Even though I feel it's Enom's fault, I cant believe WHMCS is taking so much time for such a simple and vital chance to come out.

I am NOT paying the bill for customers leaving for something our of my control.

 

Can I please have the latest version, even if it's beta?!

Link to comment
Share on other sites

Hello,

 

The sql in whmcs\install\sql\emailtemplates, creates a partial base set of email templates. It does not contain all of the email templates which are setup once the product is installed or updated. The email template sent when a domain is past the expiration date is: "Expired Domain Notice". If you have done an upgrade to 5.3.12 and don't have that template, that is something our support team can help you with.

 

Have a great day,

 

Nate C

Link to comment
Share on other sites

Just wanted to confirm, after upgrading to 5.3.12, configuring the options for the ENOM requirements, testing and then completing the ENOM opt out form stating what version of WHMCS we were now using, we received an opt out acceptance email from ENOM. Took longer than we hoped to get all this resolved but now happy it's out of the way!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated