RemoteDelivery: Exception delivering message (Mailxxx) - 451 4.7.1 Please try again later
What's the RFC say for 451? If it's authoritatively saying you should try later, then I think the behavior is currently correct.
To fabricate a case that could justify current behavior, say I have a quota on Joe Smith's mailbox at 10 MB. His mailbox is at quota, so I don't want to accept more messages for Joe.
Meanwhile, I have a remote backup server that accepts messages when the primary is down. Because it is remote, I can't check whether a mailbox is full, so I don't reject based on the quota.
Right now our server would see that Joe is overquota, and try again later, until either Joe clears some messages or our retry fails. If you change it, you'll deliver to my remote server, thereby getting around my rejection on the quota basis. Yes, my remote server will ultimately figure this out, but I would have preferred Joe's sister never send those 10 additional 5 MB messages in the first place.
Sorry the lengthiness, but it depends on whether 451 is a reply for the domain or for this server. I tried reading through the RFCs, and am only the worse for it. :) I don't see anything that says when you should move through the MX chain, just that you should and how. My feeling is if the server gives a response, that's enough for the domain. Dunno.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
