Ascio Web Service v3
ERRP - Expired Registration Recovery Policy
How to send ICANN conform mails to remind that a domain is expiring.
We offer 2 methods how mails can be sent to the registrant:
1. We send e-mails to the registrant
- We send e-mail directly to your customer
- The partner adds our SPF record into the zone of the partners DNS-server. This is the SPF record:
v=spf1 ip4:212.123.41.224/28 include:_spf.hostedemail.com -all - With SPF record we can use the partners e-mail address as mail-from.
- We can create partner-templates with the partner language and text
- Please ask partnerservice for help.
You can provide us the mail-from, reply-to, subject-template, body-template and SPF. With that we can send mails and they look like yours.
2. The partner sends e-mails and uploads them as a proof
- We send a callback to an URL on the partner-server (or via PollQueue). The OrderType is Autorenew_Domain or Autodelete_Domain. The OrderId of the Autorenew_Domain or Domain is needed for the Upload_Message API-Call.It's send 35 days before the expire-date.
- The partner sends the reminder to his customer
- The partners uploads the e-mail via AWS. It contains: from, to, subject, body, date. With that we can proof the the mail was sent.
- Please ask you integration specialist Manuel Lautenschlager for help
We won't send the same reminder again, if the partner uploaded it before
Schedular for ERRP Mails
You don't need you own schedular as we send the mails, or notify you via callback that you need to send it. The mails are sent like this:
Non-expiring domains
- 35 days before expiry: Create the autorenew order and issue callback
- 26 days before expiry. Send ERRP reminder 1 to registrant unless uploaded already re 2 below
- 7 days before expiry: Issue callback reminding partner to send ERRP reminder 2 to registrant if desired
- 4 days before expiry: Send ERRP reminder 2 to registrant unless uploaded
Use this method if:
- You what to generate your individual mails with dynamic content
- You allready have a messaging-module and what to continue using it
- You have resellers as customer and you send the reminders for them
- Your company policy forces you to send your own e-mails
Expiring domains
- 35 days before expiry: Create the autodelete order and issue callback
- 26 days before expiry: Send ERRP reminder 1 to registrant
- 7 days before expiry: Issue callback reminding partner to send ERRP reminder 2 to registrant if desired
- 4 days before expiry: Send ERRP reminder 2 to registrant
- 0 days before expiry: Issue callback reminding partner to send ERRP reminder 3 to registrant if desired
- 5 days after expiry: Send ERRP reminder 3 to registrant
- 8 days after expiry: Suspend the domain by setting it to client-hold
- 8 days after expiry: Issue callback notifying partner of suspension
- Afterwards, subsequent renew order reviving the domain must remove the hold
- 30 days (typically, depending on threshold) after expiry: Delete the domain
- Afterwards, subsequent restore order reviving the domain must remove the hold
Example mail
First/Second/Third reminder test.com
Dear Mr.Smith
Your domain test.com will expire/renew at 1.1.2000.
Please click here to renew/expire your domain.Best regards ...
These mails are required
- Expiry reminder #1 (Expiry reminder #1 example)
- Expiry reminder #2 (Expiry reminder #2 example)
- Delete notification #3 (Delete notification #3 example)
- Renew notification #1 (Renewal notification #1 example)
- Renew notification #2 (Renewal notification #2 example)
Example
use SOAP::Lite;
use Date::Format;
$proxy = "https://aws.demo.ascio.com/v3/AscioService.svc";
$namespace = "http://www.ascio.com/2007/01";
$soap = SOAP::Lite
->on_action( sub { "UploadMessage" } )
->proxy($proxy)
->ns("http://www.ascio.com/2013/02", "v3")
->ns("http://www.ascio.com/2013/02/AscioService", "service");
# Please enter your ascio-credentials here
my $header = SOAP::Header->new(
name =>"v3:SecurityHeaderDetails",
value => {"v3:Account" => "username", "v3:Password" =>"password"}
);
$soap->autotype(0);
$method = SOAP::Data->name("service:UploadMessage")->attr({xmlns => $namespace});
#Attachment
$attachment = \SOAP::Data->value(
SOAP::Data->name('v3:FileName','anything.jpg'),
SOAP::Data->name('v3:Content',base64_encode(123))
);
#ArrayOfAttachment
$attachments = \SOAP::Data->value(
);
#Message
$message = \SOAP::Data->value(
SOAP::Data->name('v3:Attachments',$attachments),
SOAP::Data->name('v3:Body','BodyTest'),
SOAP::Data->name('v3:Created',new \DateTime()),
SOAP::Data->name('v3:FromAddress','administrator@ascio-test-domain.com'),
SOAP::Data->name('v3:Subject','base64-encoded or 7 Bit ASCII'),
SOAP::Data->name('v3:ToAddress','ToAddressTest'),
SOAP::Data->name('v3:Type','ExpiryReminder1')
);
#UploadMessageRequest
$request = \SOAP::Data->value(
SOAP::Data->name('v3:OrderId','TEST123456'),
SOAP::Data->name('v3:Message',$message)
);
@query = (
SOAP::Data->name("service:request" => $request)->attr({"xsi:type" => "v3:UploadMessageRequest"})
);
$result = $soap->call($method => @query, $header);
unless ($result->fault) {
$response = $result->valueof("//UploadMessageResponse/UploadMessageResult");
print "ResultCode : $response->{'ResultCode'}\r\n";
print "Message : $response->{'ResultMessage'}\r\n";
if ($response->{"ResultCode"} == 200) {
print "OK";
}
}
else {
print join ", ",
$result->faultcode,
$result->faultstring,
$result->faultdetail;
}
WSDL for AWS v3
https://aws.demo.ascio.com/v3/aws.wsdl (OTE)
https://aws.ascio.com/v3/aws.wsdl (Live)
Please configure the IP-Whitelisting in the portal/demo-portal.
https://aws.demo.ascio.com/v3/aws.wsdl (OTE)
https://aws.ascio.com/v3/aws.wsdl (Live)
Please configure the IP-Whitelisting in the portal/demo-portal.