[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fwd: zmailer kill scheduler
On Wed, Sep 01, 2004 at 03:36:56PM -0300, Mariano Absatz wrote:
> Sorry... forgot to Cc: the list.
> ---------- Forwarded message ----------
> From: Mariano Absatz <firstname.lastname@example.org>
> Date: Wed, 1 Sep 2004 14:41:44 -0300
> Subject: Re: zmailer kill scheduler
> To: Roy Bixler <email@example.com>
> On Wed, 1 Sep 2004 09:30:00 -0500, Roy Bixler <firstname.lastname@example.org> wrote:
> > On Wed, Sep 01, 2004 at 12:45:25PM +0300, Matti Aarnio wrote:
> > No, I would not like to do that. However, I see another possibility.
> > When failover occurs, the first thing that happens is that the cluster
> > IP address is released. The transport agents use the real IP address
> > of the machine. If there is a way to make the transport agents use
> > the cluster IP address instead, then I would imagine that, when this
> > IP address is released, the transport agents would immediately die.
> Well, I think you can add (in scheduler.conf) the '-L' option to the
> smtp/* channel's smtp command.
> See http://zmailer.org/man/smtp.8zm.html for the syntax, but something like
> smtp -L [aa.bb.cc.dd] <other options>
> where aa.bb.cc.dd is the cluster IP address should work.
> Never tried it, Matti could confirm or deny this, but I think this is
> what you're looking for.
That is roughly equivalent of doing a route:
however it does not solve the load-balancing thing which works
by distributing the TCP connection setups among the backends.
ZMailer's style of sending all messages out thru single connection
does not amend itself easily to load-balancing.
Elsewere I did notice that gmail.com has become rather popular, and
presents about 1/8th of all subscribers of a popular nerdie list.
We begun to wonder, that emails didn't get successfully sent to
all recipients in there. Then we realized that there are over
500 recipients in that domain alone, and our list management
system was sending each recipient individual messages all thru
the same connection. With some 300 messages per day that mode
became rather inefficient. Solution was to make a route:
Without that "send individual messages to each recipient" detail,
usual "send as many RCPTs in single MAIL transaction as possible"
would handle the load trivially.
> Mariano Absatz - El Baby
/Matti Aarnio <email@example.com>
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to firstname.lastname@example.org