-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/08/2010 11:05 AM, Eric Shubert wrote:
> U. George wrote:
>> It is not clear to me if the same message is sent to multiple users,
>> or multiple messages to multiple users using the same smtp session.
> 
> I don't recall ever seeing multiple messages using the same smtp
> session. I presume it can be done simply by following the . (ending one
> message) with another "MAIL FROM" command and proceeding with another
> message. I just haven't ever (in 4 years of using QMT) seen it in a log.
> 
>> BUT, I think, if the *last* email rcpt is legit, then the message is
>> passed along to that legit account irrespective of any any failures
>> that happened before. I will have to review the mail log to see if
>> thats true.
> 
> That shouldn't be happening. If any one of the recipients is invalid,
> the message should be rejected (depending on the bounce/catchall setting
> of course). Someone please correct me if I'm wrong on this.
> 
>> I will have to log the smtpd session to see what the actual conditions
>> are.
> 
> Please let us know what you determine. Inquiring minds want to know. ;)

A receiving SMTP server that is doing recipient validation for a
single message has no reason to reject an entire message simply
because a single RCPT command failed.  If there are three RCPT
commands, two fail, one succeeds, and the sending server continues
sending, the single recipient that was accepted will receive the message.

The sending server may choose to handle the RCPT failure however it
wants, but a receiving server should not reject a DATA command unless
there are no recipients to deliver to (or other protocol errors).
- -- 
/*
    Matt Brookings <m...@inter7.com>       GnuPG Key FAE0672C
    Software developer                     Systems technician
    Inter7 Internet Technologies, Inc.     (815)776-9465
*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyvQykACgkQIwet2/rgZyz/lACbBO52pCQsXTDPaA+p1Mh6xuVL
TxoAnjS0P43p79Rx1lfaAiLrzg6eaS/j
=BPvE
-----END PGP SIGNATURE-----

Reply via email to