John R. Levine writes:
> >It would be better to send as many "return paths" as recipient
> >addresses, but only one message. This might end up looking like:
> >MAIL FROM/RCPT TO:<me-you-returned=example.com><[EMAIL PROTECTED]>
>
> Can you suggest an application where that would be useful? I use VERP
> all the time and I can't ever recall a situation where the default
> form of VERP wasn't entirely adequate. Adding features because
> someone might want them for some unknown purpose leads to bloatware.
I have seen places that use rather boring sequence numbers. That'll work
just as well, probably.
Oh, and I obviously do not agree that the bandwidth issue can be ignored.
There's no question that there's a big difference between sending an 8K
message to 10,000 AOL recipients - bigger lists certainly do that - as
10,000 individual messages, or 500 batchess. Someone will pipe in and
probably claim that sending 10,000 messages will be faster, due to
additional RCPT TO: round trips in the batch job. Duh. The PIPELINING
extension[1] eliminates those round trips, and even if by some divine
miracle sending 10,000 individual messages is still faster, that will come
at the expense of saturating your pipe and outgoing message slots, as
opposed to being able to continue to deliver to the rest of your list at
the same time as the AOL job.
[1] Implementing PIPELINING in Qmail would be a rather dumb thing to do, of
course, this is theoretical.
--
Sam
