On Wed, Nov 01, 2000 at 12:11:11PM -0800, [EMAIL PROTECTED] wrote:
> I think he means by way of a non-"250 ok" response during the SMTP conversation.
I was specifically referring to 4xx codes in response to a RCPT command.
> The answer is that the protocol allows it, but many programs that talk
On Wed, Nov 01, 2000 at 02:04:54PM -0600, Charles Cazabon wrote:
> > This brings me to a question: should the grouping of recipients by
> > domain name be done in qmail-send or qmail-queue?
> My gut reaction would be in qmail-queue. However, that might make it a little
> more difficult to do this
On Wed, Nov 01, 2000 at 02:04:54PM -0600, Charles Cazabon wrote:
> Bruce Guenter <[EMAIL PROTECTED]> wrote:
> >
> > This brings me to a question: should the grouping of recipients by
> > domain name be done in qmail-send or qmail-queue?
>
> My gut reaction would be in qmail-queue. However, that
Bruce Guenter <[EMAIL PROTECTED]> wrote:
>
> This brings me to a question: should the grouping of recipients by
> domain name be done in qmail-send or qmail-queue?
My gut reaction would be in qmail-queue. However, that might make it a little
more difficult to do this optimization when mail come
> I'm looking at doing something similar, but still treating the
> recipients seperately (one recip could bounce independant of the rest),
This brings me to a question: should the grouping of recipients by
domain name be done in qmail-send or qmail-queue? The sending algorithm
used by qmail-send
Hi Bruce,
I believe you're talking about the patch I did.
See
http://www.ornl.gov/its/archives/mailing-lists/qmail/1999/11/msg00678.html
or
http://www.egroups.com/message/djb-qmail/35717
Actually, as you'll see, the patch is unfinished, I just wanted to share
what I had and listen for input. Bu
Greetings.
A while back, somebody sent a patch to the qmail mailing list that
implemented multiple RCPT support in qmail-send and qmail-rspawn. This
patch worked by sorting the domain names and transating the NUL bytes
between recipients with the same domain name into another byte, and then
trea
