반응형


Check out RFC 2821
you are supposed to use the codes defined in RFC 3463 (or 1893)


----------------------
In general, you have to look at your options and choose the one that
most closely approximates what you are trying to communicate. In the
set of 4xx messages you have:



421 Service not available
432 Password required
450 Mailbox unavailable/busy
451 Local error in processing
452 Insufficient storage
453 You have no mail
454 TLS not available temporarily
458 Unable to queue message temporarily
459 Node X not allowed

Of all of those, 452 jumps out as the only one that obviously has
something to do with storage limits. In attempting to communicate more
accurately the cause of the error to the user, you are supposed to use
the codes defined in RFC 3463 (or 1893); in this case, 4.2.2 (or
5.2.2, though the RFC says that it *should* be considered a
"persistent transient error") communicates "mailbox full".



Of the 5xx errors defined in SMTP, there are:

500 Syntax error
501 Syntax error in parameters
502 Command not implemented
503 Bad sequence
504 Parameter not implemented
521 Machine does not accept mail
530 Authentication required
534 Authentication mechanism too weak
538 Encryption required
550 Mailbox unavailable permanently
551 User not local
552 Message too big
553 Mailbox name not allowed
554 Transaction failed



반응형

+ Recent posts