On Fri, Jan 30, 2009 at 7:02 AM, Gordon Messmer <[email protected]> wrote: > Lisa Muir wrote: >> What is the protocol for smtp where there are multiple recipients for >> an email, either multiple to, cc or bcc, and one of the recipients is >> rejected at the SMTP submission as being an invalid email address. > > The sender (which may be a mail client) submits each address with "RCPT > TO". There is no indication during an SMTP session if an address was in > a To:, CC:, or BCC header. They're all sent with "RCPT TO". Each > address is either accepted or rejected. If an address is rejected, the > sender can continue or fail according to its own policy. > > Most mail servers will continue. They'll create a DSN for the original > sender that indicates which address failed. > > Most mail client will stop if a recipient is rejected. They will > indicate the error to the user and allow (or require) the address to be > corrected before the message is sent.
Until the next "send / receive" frequency time occurs. If a user walks away for a week, any MUA i have experience of will happily resubmit the message say every 30 mins for the entire week. > If I remember correctly, Outlook does not behave like other mail > clients. It will continue like a mail server would, and create a notice > indicating the failure in the user's Inbox. It wasn't outlook for sure. >> If the user then re-submits does it get sent to everyone else again >> and again until they delete or fix the error in that one email >> address? > > You probably have a user with Outlook. He probably saw a notice > indicating a failure. He probably resent the message to all of the > original recipients instead of just the one that needed to be fixed. No, it was on the auto send/receive frequency. In the old days a message would get accepted and bounce. Now, it is being accepted for some recipients, but the message delivery to the MTA fails, and thus interpreted by the MUA as not having being accepted at all. Either the MUA must now intelligently interpret the error and queue the message for the failing recipients only, or the MTA must not return a failure for the message, its simply illogical to reject a message during a submit to an MTA and then have the MTA deliver it anyway for some subset of the original distribution list. Lisa. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
