Ceci est une ancienne révision du document !
SYMPA : bounce (erreur)
Les messages en erreur pour un abonné sont sous ~sympa/bounce/<nom liste>
Les bounces sont stockés pour chaque abonné dans la table subscriber_table.
Un abonné pour une liste est en erreur quand le champ bounce_subscriber est différent de NULL.
Ce champ est formé de 4 parties.
Exemple : 1214927060 1214927060 1 5.0.0
| premier timestamp | dernier timestamp | Nombre de bounce | code bounce | |
|---|---|---|---|---|
| exemple 1 | 1214927060 | 1214927060 | 1 | 5.0.0 |
| Tue, 01 Jul 2008 15:44:20 GMT | Tue, 01 Jul 2008 15:44:20 GMT (17:44:20 CEST) | |||
| exemple 2 | 1214201063 | 1214201313 | 2 | 5.0.0 |
| Mon, 23 Jun 2008 06:04:23 GMT | Mon, 23 Jun 2008 06:08:33 GMT (08:08:33 CEST) |
Pour savoir à quelle date correspond un timestamp http://www.onlineconversion.com/unix_time.htm
(attention le timestamp est donné en GMT et nous sommes en CEST ; ajouter le décalage nécessaire selon l'heure d'été ou d'hiver).
Remarque à la première erreur la partie “dernier timestamp” est égale à celle du “premier timestamp” et le nombre de bounce est à 1.
| code bounce | signification |
|---|---|
| 4.0.0 | Other undefined Status |
| 4.1.1 | Bad destination mailbox address |
| 4.2.0 | Other or undefined mailbox status; Timeout connection problem |
| 4.2.2 | Mailbox full |
| 4.3.0 | Other or undefined mail system status |
| 4.4.1 | No answer from host |
| 4.4.2 | Bad connection |
| 4.4.3 | Directory server failure; Routing server failure |
| 4.4.6 | Routing loop detected |
| 4.4.7 | Delivery time expired |
| 4.7.0 | Temporary server error |
| 4.7.1 | Client host rejected: cannot find your hostname |
5.x.x
The command was not accepted and the requested action did not occur. The sender-SMTP is discouraged from repeating the exact request (in the same sequence). Even some “permanent” error conditions can be corrected, so the human user may want to direct the sender-SMTP to reinitiate the command sequence by direct action at some point in the future (e.g., after the spelling has been changed, or the user has altered the account status).
| code bounce | signification |
|---|---|
| 5.0.0 | Host or domain name not found Syntax error, command unrecognized. Also command line too long Other undefined Status |
| 5.0.350 | The error reported by the receiving server wasn't specific enough to determine the exact nature of the problem. |
| 5.1.0 | Other address status; Unknown address |
| 5.1.1 | Bad destination mailbox address |
| 5.1.3 | Bad destination mailbox address syntax |
| 5.1.6 | Destination mailbox has moved, No forwarding address |
| 5.1.10 | Recipient address has null MX |
| 5.2.0 | Other or undefined mailbox status; authentication error |
| 5.2.1 | Mailbox disabled, not accepting messages |
| 5.2.2 | Mailbox full |
| 5.2.3 | Message length exceeds administrative limit |
| 5.3.0 | Other or undefined mail system status |
| 5.3.4 | Message too big for system |
| 5.3.5 | ? Authentication failed |
| 5.4.0 | Other or undefined network or routing status |
| 5.4.1 | Unable to route |
| 5.4.14 | Hop count exceeded |
| 5.4.2 | Bad Connection |
| 5.4.316 | Message expired, connection refused |
| 5.4.4 | Unable to route; No answer from host; Host not found (not in DNS); Cannot find the next hop |
| 5.4.6 | Routing loop detected |
| 5.5.0 | Other or undefined protocol status |
| 5.6.1 | Body type not supported by Remote Host |
| 5.7.0 | Other or undefined security status |
| 5.7.1 | Delivery not authorized, message refused |
| 5.7.64 | Relay Access Denied |
| 5.7.9 | Authentication mechanism is too weak ; message content is not acceptable here |
