9.1.1 Email Acknowledgement Message

This ack message holds the overall result of the update, which either ‘FAILED' or was a total ‘SUCCESS'. If the update included several objects and the operation on any of those objects failed, then the overall result is ‘FAILED'. If no individual operation failed, then the overall result is ‘SUCCESS'. This includes any individual ‘NOOP' results where no operation was carried out, as the submitted object was identical to the object already in the database. This overall result is stated at the start of the subject line of the ack email sent to the user. Any user comment on the Subject line of the submitted update follows this result.

Subject: SUCCESS: some user comment
Date: Thu, 11 Sep 2014 10:42:15 +0200 (CEST)
From: RIPE Database Administration local <unread _at_ ripe _dot_ net>
To: denis _at_ ripe _dot_ net

The acknowledgement message content is split into sections. The first section shows from where the update was sent. This could be a copy of the update email header or the IP address for a synchronous connection. This section also includes a summary of the update results, explaining how many objects were recognised by the database software, how many operations were successful and how many failed.

An example first section of an acknowledgment message would look like this:

>  From:       Denis Walker <denis _at_ ripe _dot_ net>
> Subject: some user comment
> Date: Thu, 11 Sep 2014 10:42:14 +0200
> Reply-To: Denis Walker <denis _at_ ripe _dot_ net>
> Message-ID: <54116066.7030403 _at_ ripe _dot_ net>


Number of objects found: 5
Number of objects processed successfully: 4
Create: 1
Modify: 2
Delete: 0
No Operation: 1
Number of objects processed with errors: 1
Create: 0
Modify: 1
Delete: 0

The next section is the "DETAILED EXPLANATION" of the acknowledgement message. This is split into three parts.

  • The first part lists all the objects where the operation failed. This will include "***Error:" messages as well as possible "***Info:" and "***Warning:" messages.
  • The next part shows all the operations that were successful. This may include additional "***Info:" and "***Warning:" messages with each operation listed.
  • The third part lists all the paragraphs from the update message that were not recognised as objects.

Each part is separated in the ACK by a line containing several '~' characters. Within each part, the objects and paragraphs are listed in the order that they were processed. This is generally the order that they appear in the update message unless ‘AUTO-n' NIC Handles are referenced. The line before each object contains three hyphen characters (-) . This allows for easy parsing by script.

Below is an example of this section of the acknowledgement message:


***Warning: Invalid keyword(s) found: some user comment
***Warning: All keywords were ignored

The following object(s) were found to have ERRORS:

Update FAILED: [person] dn1172-ripe de nis
***Error: Syntax error in object

person: de nis
address: here
phone: 1
***Error: Syntax error in "1"
nic-hdl: dn1172-ripe
mnt-by: TEST-MNT
source: ripe

The following object(s) were processed SUCCESSFULLY:

Modify SUCCEEDED: [person] dn1172-ripe de nis

The following paragraph(s) do not look like objects

This is a private email.
It is intended only for the named recipient.


There are many reasons why the operation may fail for an object, including syntax error, authorisation failure and failed business rules check.