Hem  ›  3. Rapporter  ›  Vad betyder de olika statuskoderna för studsarna?

Vad betyder de olika statuskoderna för studsarna?

Taggar: ,

För dig som är intresserad av att se vad studsarna beror på har vi listat de vanligaste statuskoderna med en kortare beskrivning (se nedan). I vissa fall stämmer tyvärr inte statuskoderna till punkt och pricka eftersom en del e-postservrar inte levererar koder enligt gällande standard.

Generellt kan man säga att att en statuskod som är 4.x.x är ett tillfälligt fel men där koden är 5.x.x är det ett permanent. Vid tillfälliga fel försöker vi skicka tre gånger innan e-postadressen sätts till inaktiv. Vid permanenta fel inaktiveras e-postadressen direkt. Vet du vad som är fel med adressen kan du gå in på kontakten och rätta den så aktiveras den igen automatiskt.

Kod Titel (eng.) Beskrivning (eng.)
4.x.x Persistent Transient Failure A persistent transient failure is one in which the message as sent is valid, but some temporary event prevents the successful sending of the message. Sending in the future may be successful.
5.x.x Permanent Failure A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery.
x.0.0 Other undefined Status Other undefined status is the only undefined error code. It should be used for all errors for which only the class of the error is known.
x.1.1 Bad destination mailbox address The mailbox specified in the address does not exist. For Internet mail names, this means the address portion to the left of the @ sign is invalid. This code is only useful for permanent failures.
x.2.2 Mailbox full The mailbox is full because the user has exceeded a per-mailbox administrative quota or physical capacity. The general semantics implies that the recipient can delete messages to make more space available. This code should be used as a persistent transient failure.
x.3.0 Other or undefined mail system status The destination system exists and normally accepts mail, but something about the system has caused the generation of this DSN.
x.4.1 No answer from host The outbound connection attempt was not answered, either because the remote system was busy, or otherwise unable to take a call. This is useful only as a persistent transient error.
x.4.2 Bad connection The outbound connection was established, but was otherwise unable to complete the message transaction, either because of time-out, or inadequate connection quality. This is useful only as a persistent transient error.
x.4.3 Directory server failure The network system was unable to forward the message, because a directory server was unavailable. This is useful only as a persistent transient error. The inability to connect to an Internet DNS server is one example of the directory server failure error.
x.4.4 Unable to route The mail system was unable to determine the next hop for the message because the necessary routing information was unavailable from the directory server. This is useful for both permanent and persistent transient errors. A DNS lookup returning only an SOA (Start of Administration) record for a domain name is one example of the unable to route error.
x.4.6 Routing loop detected A routing loop caused the message to be forwarded too many times, either because of incorrect routing tables or a user forwarding loop. This is useful only as a persistent transient error.
x.4.7 Delivery time expired The message was considered too old by the rejecting system, either because it remained on that host too long or because the time-to-live value specified by the sender of the message was exceeded. If possible, the code for the actual problem found when delivery was attempted should be returned rather than this code. This is useful only as a persistent transient error.
x.5.0 Other or undefined protocol status Something was wrong with the protocol necessary to deliver the message to the next hop and the problem cannot be well expressed with any of the other provided detail codes.
x.7.0 Other or undefined security status Something related to security caused the message to be returned, and the problem cannot be well expressed with any of the other provided detail codes. This status code may also be used when the condition cannot be further described because of security policies in force.
x.7.1 Delivery not authorized, message refused he sender is not authorized to send to the destination. This can be the result of per-host or per-recipient filtering. This memo does not discuss the merits of any such filtering, but provides a mechanism to report such. This is us