IG missive returnCodes

From documentation SEPAmail
Jump to navigation Jump to search
SEPAmail – Norme 1206

Cette page fait partie de la version 1206 de la norme.

Sauf indication contraire, elle a été validée par les instances concernées et s'impose à tous les adhérents SEPAmail.
ATTENTION ! La version 1606 de la norme est disponible, vérifiez si cette page est toujours valable.

<svnig date="Tue Aug 07 11:27:54 CEST 2012" revision="" repository="General" last="" conversion="none" source="Msv_AckCodes.txt">

Annex : return codes for the acknowledgement missive

The class, subject and detail elements of the acknowledgement missive are used to indicate precisely on which elements the acknowledgement -- or lack thereof -- is based.

  • Class 2 always indicates success
  • Class 4 indicates a transient error, that a resending of the missive could solve
  • Class 5 indicates a permanent error, which cannot be solved by resending the missive

The full list of codes appears in the following table.

In this table, some codes appear with an 'N' class. This means that the receiver must decide whether the error is transient or permanent, and use 4 or 5 accordingly. Class 4, which allows for automatic resending of missives, should be preferred whenever possible. </svnig>

<svnig date="Tue Aug 07 11:27:54 CEST 2012" revision="" repository="General" last="" conversion="tab" source="Msv_AckCodes_1206.tab">

Code Description
Subject addresses
5.1.1 Unknown sender
5.1.2 Unknown receiver
5.1.3 Receiver known but out of SEPAmail scheme or ecosystem.
2.1.9 Receiver known, missive forwarded.
Subject mailbox
N.2.1 Mailbox is deactivated
N.2.2 Mailbox is full
5.2.3 Message is too long
Subject system
N.3.1 File system full
N.3.2 Inaccessible server
N.3.3 Sending date+time incorrect, and outside of the margin. (Missive has not been handled).
Subject debtor
5.4.1 Invalid addressing identifier (IBAN, QXBAN ...)
2.4.9 Valid addressing identifier, real account
Subject Security and cryptography
5.7.2 Impossible to decrypt (key1 or key2). In fact, since the decryption of the S-MIME envelope cannot be processed, the embedded missive cannot be read and acknowledged. Thus, the proper behaviour in this case will be avoiding any response to the sender.
5.7.3 Unsupported algorithm or security function
5.7.4 Integrity error
Subject contents
5.8.1 XML syntax error, non conforming to schema
5.8.2 Missive contents incoherent
5.8.3 Invalid missive identifier
5.8.4 Order number error
5.8.5 Version not supported
5.8.6 Corrupted contents or virus detected. In fact, since the detection of a corrupted content may be prior to the extraction of the embedded missive due to infrastructure constraints, this missive may not be acknowledged to the sender.

</svnig>