<[Карта]                [Начало]                [Sendmail-ссылки]                [Синтаксис]                [Типовые задачки]                  [Задачки по маршрутизации]                  [Задачки по маcкарадингу]                  [SendmailACL]                  [Spamooborona]                  [VadeRetro]                  [Regex]                  [Тонкости]                  [Недок.особен.]                  [Несущ.юзеры]                  [Прячемся!]                  [RFC1893.Цитаты]                  [ТП.Эмоции]                  [Антиспам&Разум]                  [Экзерсисы]                 


RFC 1893 & 2821. Цитаты.

RFC 1893 - Enhanced Mail System Status Codes
Здесь я приведу описание некоторых кодов.

Во-первых, что такое status code?
Status codes consist of three numerical fields separated by ".".
The first sub-code indicates whether the delivery attempt was successful.
The second sub-code indicates the probable source of any delivery anomalies,
and the third sub-code indicates a precise error condition.

-----------
    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.1.X    Addressing Status
The address status reports on the originator or destination address. It may include address syntax or validity. These errors can generally be corrected by the sender and retried.

    X.2.X Mailbox Status
Mailbox status indicates that something having to do with the mailbox has cause this DSN. Mailbox issues are assumed to be under the general control of the recipient.

    X.4.X    Network and Routing Status
The networking or routing codes report status about the delivery system itself. These system components include any necessary infrastructure such as directory and routing services. Network issues are assumed to be under the control of the destination or intermediate system administrator.

    X.7.X    Security or Policy Status
The security or policy status codes report failures involving policies such as per-recipient or per-host filtering and cryptographic operations. Security and policy status issues are assumed to be under the control of either or both the sender and recipient. Both the sender and recipient must permit the exchange of messages and arrange the exchange of necessary keys and certificates for cryptographic operations.

-----------
    X.1.0 Other address status
Something about the address specified in the message caused this DSN.

    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.1.8    Bad sender's system address
The sender's system specified in the address does not exist or is incapable of accepting return mail. For domain names, this means the address portion to the right of the "@" is invalid for mail.

   X.2.1    Mailbox disabled, not accepting messages
The mailbox exists, but is not accepting messages. This may be a permanent error if the mailbox will never be re-enabled or a transient error if the mailbox is only temporarily disabled.

   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.4.0    Other or undefined network or routing status
Something went wrong with the networking, but it is not clear what the problem is, or the problem cannot be well expressed with any of the other provided detail codes.

    X.7.1    Delivery not authorized, message refused
The 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 useful only as a permanent error.

-----------
   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.

----------
8. Appendix - Collected Status Codes

X.1.0 Other address status
X.1.1 Bad destination mailbox address
X.1.2 Bad destination system address
X.1.3 Bad destination mailbox address syntax
X.1.4 Destination mailbox address ambiguous
X.1.5 Destination mailbox address valid
X.1.6 Mailbox has moved
X.1.7 Bad sender's mailbox address syntax
X.1.8 Bad sender's system address

X.2.0 Other or undefined mailbox status
X.2.1 Mailbox disabled, not accepting messages
X.2.2 Mailbox full
X.2.3 Message length exceeds administrative limit.
X.2.4 Mailing list expansion problem

X.3.0 Other or undefined mail system status
X.3.1 Mail system full
X.3.2 System not accepting network messages
X.3.3 System not capable of selected features
X.3.4 Message too big for system

X.4.0 Other or undefined network or routing status
X.4.1 No answer from host
X.4.2 Bad connection
X.4.3 Routing server failure
X.4.4 Unable to route
X.4.5 Network congestion
X.4.6 Routing loop detected
X.4.7 Delivery time expired

X.5.0 Other or undefined protocol status
X.5.1 Invalid command
X.5.2 Syntax error
X.5.3 Too many recipients
X.5.4 Invalid command arguments
X.5.5 Wrong protocol version

X.6.0 Other or undefined media error
X.6.1 Media not supported
X.6.2 Conversion required and prohibited
X.6.3 Conversion required but not supported
X.6.4 Conversion with loss performed
X.6.5 Conversion failed

X.7.0 Other or undefined security status
X.7.1 Delivery not authorized, message refused
X.7.2 Mailing list expansion prohibited
X.7.3 Security conversion required but not possible
X.7.4 Security features not supported
X.7.5 Cryptographic failure
X.7.6 Cryptographic algorithm not supported
X.7.7 Message integrity failure

-----------
RFC 2821 - Simple Mail Transfer Protocol

   4.2.2 Reply Codes by Function Groups
    500 Syntax error, command unrecognized (This may include errors such as command line too long)
    501 Syntax error in parameters or arguments
    502 Command not implemented (see section 4.2.4)
    503 Bad sequence of commands
    504 Command parameter not implemented
    211 System status, or system help reply
    214 Help message
    (Information on how to use the receiver or the meaning of a particular non-standard command; this reply is useful only to the human user)
    220 Service ready
    221 Service closing transmission channel
    421 Service not available, closing transmission channel (This may be a reply to any command if the service knows it must shut down)
    250 Requested mail action okay, completed
    251 User not local; will forward to (See section 3.4)
    252 Cannot VRFY user, but will accept message and attempt delivery (See section 3.5.3)
    450 Requested mail action not taken: mailbox unavailable (e.g., mailbox busy)
    550 Requested action not taken: mailbox unavailable (e.g., mailbox not found, no access, or command rejected for policy reasons)
    451 Requested action aborted: error in processing
    551 User not local; please try (See section 3.4)
    452 Requested action not taken: insufficient system storage
    552 Requested mail action aborted: exceeded storage allocation
    553 Requested action not taken: mailbox name not allowed (e.g., mailbox syntax incorrect)
    354 Start mail input; end with .
    554 Transaction failed (Or, in the case of a connection-opening response, "No SMTP service here")

-----------
   4.2.3 Reply Codes in Numeric Order
    211 System status, or system help reply
    214 Help message (Information on how to use the receiver or the meaning of a particular non-standard command; this reply is useful only to the human user)
    220 Service ready
    221 Service closing transmission channel
    250 Requested mail action okay, completed
    251 User not local; will forward to (See section 3.4)
    252 Cannot VRFY user, but will accept message and attempt delivery (See section 3.5.3)
    354 Start mail input; end with .
    421 Service not available, closing transmission channel (This may be a reply to any command if the service knows it must shut down)
    450 Requested mail action not taken: mailbox unavailable (e.g., mailbox busy)
    451 Requested action aborted: local error in processing
    452 Requested action not taken: insufficient system storage
    500 Syntax error, command unrecognized (This may include errors such as command line too long)
    501 Syntax error in parameters or arguments
    502 Command not implemented (see section 4.2.4)
    503 Bad sequence of commands
    504 Command parameter not implemented
    550 Requested action not taken: mailbox unavailable (e.g., mailbox not found, no access, or command rejected for policy reasons)
    551 User not local; please try (See section 3.4)
    552 Requested mail action aborted: exceeded storage allocation
    553 Requested action not taken: mailbox name not allowed (e.g., mailbox syntax incorrect)
    554 Transaction failed (Or, in the case of a connection-opening response, "No SMTP service here")

ССылки по теме: [1]
[2]: The current RFC for SMTP is 5321
[]
Обратная связь
Последнее обновление: 20 октября 2008 г.