Hello Jud,
Letterrip can't be in the business of trying to interpret the english text
of the error code. We would never succeed at it.
In reference to the discussion on server response: "554 this mail box is full" and your response.
I agree that you can't rely on the english text because it constantly changes. But you should be able to rely on the error codes, since they are supposed to be governed by RFCs.
This from rfc1893 regarding enhanced mail system status codes. http://www.faqs.org/rfcs/rfc1893.html
Here's what a 544 should mean...
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.5.X Mail Delivery Protocol Status
The mail delivery protocol status codes report failures involving the message delivery protocol. These failures include the full range of problems resulting from implementation errors or an unreliable connection. Mail delivery protocol issues may be controlled by many parties including the originating system, destination system, or intermediate system administrators.
X.5.4 Invalid command arguments
A valid mail transaction protocol command was issued with invalid arguments, either because the arguments were out of range or represented unrecognized features. This is useful only as a permanent error.
Using 544 is just plain wrong, because it doesn't relate to the mail box or it's status. Unfortunately, some of the big ISPs: netzero and earthlink appear to be using an RFC from some other planet.
It would be semi-logical to return a 5xx series status code, since the word permanent is only intended that resending right away probably won't help.
They should return a 522 or preferably a 422, since that relates to the mail box condition.
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.
Hope this sheds more light on the situation for others who are trying to make sense of the topic of bounce management.
Thanks, Marty
Marty Crouch • webvalence.com • 503-335-3442 2236 NE 44th Avenue • Portland, OR 97213 • US
Server_Log says:
10/23 17:24:18 [151] - smtp send: ERROR!! Address error, LetterRip sent:"RCPT TO:<<[EMAIL PROTECTED]>" .... server responded:"554 This mailbox is full. Please try again later. for [EMAIL PROTECTED]"
In the past, it was very rare for an SMTP server to report "mailbox full"
during the SMTP transaction. It would typically occur after the fact with a
Delivery Status Notification. Regardless, the 5xx series of SMTP errors are
permanent errors. Mailbox full is supposed to be a transient error and
should be reported with a 4XX SMTP error code.
Letterrip can't be in the business of trying to interpret the english text
of the error code. We would never succeed at it.
JUd
-- This message is from the Letterrip-Talk Mailing list. To unsubscribe, send mail to: [EMAIL PROTECTED]