Regarding: http://web.infoave.net/~dsill/lwq.html#multi-rcpt
Dave S,
I'm having trouble accepting this logic. You mention 3 options:
"Say you're an MTA, and one of your users sends a message to three
people on hostx.example.com. There are several ways you could do this.
1. You could open an SMTP connection to hostx, send a copy of
the message to the first user, send a copy to the second user, send a
copy to the third user, then close the connection.
2. You could start three processes, each of which opens an SMTP
connection to hostx, sends a copy of the message to one of the users,
then closes the connection.
3. You could open an SMTP connection to host, send a copy of the
message addressed to all three users, then close the connection. "
and that qmail uses option #2. Clearly, the rank of efficiency is, from
best to worst,: 3, 1, 2
------
We had a situation with a customer who was consulting for a college. So
every few days, she had to send a 10MB PowerPoint file to about 50
recipients at that college. Under qmail, a separate thread was opened up
for each qmail-remote.
a) That means a total transfer of 500MB rather than simply 10MB.
b) Secondly, since all outbound threads were tied up for a long time,
all other mail was deferring, causing customer complaints.
c) Finally, since all 50 messages were being received by the same remote
SMTP server, the transfer was bottlenecked by the cpu and i/o of their
single mail relay trying to receive 50 copies of the same thing.
We love qmail, and it's working very well for us in general. But I'm
having a hard time reconciling your logic in this paragraph. Perhaps you
could clarify for me.
Dave (K)
