At 12:04 PM -0500 2/25/03, ted crane wrote: >Regardless of the direction of discussions and suggestions >that might arise from my previous question, it should be noted >that SIMS is receiving one 250 message and one 452 message, >but is reporting two 452 messages in the log. Or so it seems.
Seems like that to me, too, and that's generally a bad idea. The log should should what actually happened. However, the 4xx messages, in general, apply to the entire message rather than to individual transactions. According to the RFC, the valid 4xx codes at the "RCPT TO" point are: 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 While I could understand a 450 or 451 message for an individual mailbox, a 452 message to me would indicate that I should abort the ENTIRE message (after all, they're out of room - why take what little they have left?) and try later when the problem is corrected. However, this "address throttling" that they're attempting to do isn't really covered by the standard - and, frankly, is rather offensive. All it really does is increase the bandwidth that legitimate messages take. (E.g.: I run a list server, and I send only one copy of list postings per domain; if I have two subscribers at that domain, they're going to miss out, because I'm NOT going to send one copy per user.) It's rare to find a good idea that the standard doesn't support. And, IMNTBHO, this isn't a good idea. >One might argue that MessageWall at taconic.net is simply non-compliant >with the RFC, but taconic.net very reasonably explains that MessageWall >is correctly not accepting responsibility for the second recipient, and >that Stalker should send the data of the message to the first recipient >and retain the responsibility for the second recipient until a retry. No, they're NOT doing it "correctly." A 450 would be "correctly;" it would report that that particular mailbox can't be accessed at the moment. A storage problem is not the issue. The MessageWall software has a problem. ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
