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. ;)
On 10/08/2010 09:45 AM, Eric Shubert wrote:
If I understand this correctly, I think this is the nature of the beast.
If you send an email to multiple addresses at the same server/domain,
some of which are good, and others which are not, the smtp protocol only
allows for rejection or acceptance of the entire message, somewhat
unfortunately. Qmail remedies the situation by sending messages
individually, but this doesn't solve the problem of other servers
sending a mix of valid and invalid addresses in the same message.
Also, addresses are processed by chkuser in whatever order the sending
server provides them. Sequence is of no significance.
U. George wrote:
the first e-mail rcpt is legit.
It appears that if more rcpts follow, and those accounts dont exist,
then the first legit e-mail is not processed, as is rejected with all
the other bogus attempts to send e-mail the domain.
The chkuser test process appears to try a fake e-mail, and then a
legit e-mail. BUt does not try a legit e-mail, and then a fake e-mail.
Oct 8 07:35:29 LaptopServer qmail: 07:35:29.452 sslserver: pid 21983
from 212.139.245.241
Oct 8 07:35:29 LaptopServer qmail: 07:35:29.565 sslserver: ok 21983
mail.gatworks.com:96.232.60.244:25
212-139-245-241.dynamic.dsl.as9105.com:212.139.245.241::2202
Oct 8 07:35:31 LaptopServer qmail: 07:35:31.384 CHKUSER accepted
sender: from <o.samath...@fujitsugeneral.com::> remote
<nmcdprhc:212-139-245-241.dynamic.dsl.as9105.com:212.139.245.241>
rcpt <> : sender accepted
Oct 8 07:35:31 LaptopServer qmail: 07:35:31.385 CHKUSER accepted
rcpt: from <o.samath...@fujitsugeneral.com::> remote
<nmcdprhc:212-139-245-241.dynamic.dsl.as9105.com:212.139.245.241>
rcpt <netbe...@gatworks.com> : found existing recipient
Oct 8 07:35:31 LaptopServer qmail: 07:35:31.385 CHKUSER rejected
rcpt: from <o.samath...@fujitsugeneral.com::> remote
<nmcdprhc:212-139-245-241.dynamic.dsl.as9105.com:212.139.245.241>
rcpt <nobgatworks...@gatworks.com> : not existing recipient
Oct 8 07:35:32 LaptopServer qmail: 07:35:32.395 CHKUSER rejected
rcpt: from <o.samath...@fujitsugeneral.com::> remote
<nmcdprhc:212-139-245-241.dynamic.dsl.as9105.com:212.139.245.241>
rcpt <starrea...@gatworks.com> : not existing recipient
Oct 8 07:35:34 LaptopServer qmail: 07:35:34.375 sslserver: warning:
dropping connection, unable to read/create SSL instance
Oct 8 07:35:34 LaptopServer qmail: 07:35:34.375 sslserver: end 21982
status 111;N
--
-Eric 'shubes'
!DSPAM:4caf416932711861280447!
