On Tuesday 06 April 2004 18:43, Roger Ward wrote:
> Is there a specific number of messages per connection Courier will attempt 
> per host?  
> 
> If there are 40 messages in the queue, is there a way to encourage or force 
> Courier to open one connection then send 40 messages down that connection 
> (or even a small number like 5-10).

I'm sorry but I'm not quite sure what you are asking here.  In the 
module.esmtp file in courier's 'etc' directory (usually '/etc/courier' if you 
build rpms, '/usr/lib/courier/etc' otherwise) you can specify MAXDELS and 
MAXHOST.  MAXDELS is the total number of concurrent (esmtp) deliveries (i.e. 
connections) that courier will make to deliver mail.  MAXHOST is the total 
number of conncurrent connections that courier will make to any one domain to 
deliver mail.

By default MAXDELS=40 and MAXHOST=4 (I think) which means that courier will 
make a maximum of 4 connections to any particular mailserver and a maximum of 
40 connections total.   So if you want to send lots of messages to the same 
host at the same time (and your bandwidth can support it) then you could set 
MAXHOST to be very large.  

But this may or may not solve your problem depending on how many different 
domains your recipients are at.  If you send 1 message to 40 recipients at 
the same domain then courier makes 1 connection to that domain's mailserver 
and sends the message 1 time with the 40 recipients listed.  But if you send 
1 message to 40 recipients at 40 different domains then courier is going to 
make 40 different connections - one to each of those 40 different domains' 
mailservers - and send the same message 40 times.  But, of course, if you 
have MAXDELS=40 then those 40 connections should happen at the same time.

And that is different from using a "smarthost", where ALL your mail is relayed 
through one mail server.  In that case courier still creates queues based on 
the recipients' domains and will still make 40 connections to the smarthost 
to send 1 message to 40 recipients at 40 different domains.  But there's a 
patch to make it send just one copy of a message to a smarthost regardless of 
the recipients' domains.

But if there are 3 separate messages in the queue for the same recipient then 
I don't know of any way to make courier open ONE connection to sourgeforge's 
mailserver and send all three messages down that one connection.  Each 
message in the queue is its own item and will get its own connection.  I 
*think* courier will open a connection, send the first message, close the 
connection, open another connection, send the next message, etc., etc.  (But 
I haven't actually looked at the code to see that this is always true.)  I 
don't think it will scan the queue each time it sends a message to see if 
there's another message waiting to go to the same mailserver and just keep 
sending messages on that same connection.

Does this answer your question or have I just confused things further?  (My 
wife will happily tell you that I confuse her all the time when I try and 
explain to her what I'm doing on the computer, so... :-)

Jeff Jansen


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to