Notification of contact email change
Recently our server started sending an email notifications when the contact info is changed for a new account. Unfortunately, one goes to us and one goes to our customer, which we don't want.
We create new accounts using the API (createacct) call, and set contactemail to our address. We then use the call to savecontactinfo to update the primary and secondary contact email. This generates the emails.
We then changed our code to first call savecontactinfo with these parameters set:
notify_contact_address_change=0
notify_contact_address_change_notification_disabled=0
without setting the contact emails at all.
Then we call the same function again to set the contact emails, hoping there will be no notifications. This sort of worked, but now we the system sends emails to the webmaster@thecustomerdomain address (which we don't set anwhere in our code) notifying them that the two settings above have been changed.
Seems any call to savecontactinfo -- whether to disable the notifications or to set new contact info -- generates an email to the customer using webmaster@thecustomerdomain even if we never set any email addresses to webmaster@ anywhere in our code. During account creation, we specifically set the contact email to our internal address, but after the account is created, it's set to webmaster@thecustomerdomain unless we specifically call savecontactinfo. It's as if the createacct call ignores the contactemail parameter we're sending in, and if we never call savecontactinfo, it then defaults it to webmaster@thecustomerdomain.
Any insights on how to set the contactemail during creation and generate NO emails to anyone during subsequent savecontactinfo calls would be helpful.
Thanks!
-
Hello, Thanks for contacting us. Would you mind opening a support ticket about this? I suspect that our support staff will be able to get you an answer more quickly than I can through this venue. cPanel Customer Portal Thanks, David Nielson Integration Developer, cPanel 0
Please sign in to leave a comment.
Comments
1 comment