Wednesday, August 13, 2003, 5:15:00 PM, you wrote:
> Jan Stanik writes: >> >> Tuesday, August 12, 2003, 6:27:19 PM, you wrote: >> >> >>>>>> >>>>>> Where could be the bottleneck of delivering? Can I allow more >>>>>> concurrent delivery attempts? >>>> >>>>> You can tune the delivery limits by editing >>>>> $sysconfdir/module.* files. The >>>>> MAXDELS, MAXHOST, and MAXRCPT settings are described in >>>>> http://www.courier-mta.org/queue.html. You better know what you're doing; >>>>> if the parameters aren't set right the server may not even start. As such, >>>>> always back them up first, before messing around with them. >>>> >>>>> For esmtp, MAXDELS is the maximum number of messages sent via SMTP at any >>>>> given time, and MAXHOST is the maximum number of messages sent via SMTP to >>>>> the same domain, at any given time. >>>> >>>> Thank You Sam. I searched the log file and it seems the problem >>>> occurs when "wakeup time=none" string appears in courierd records. >>>> I the same time new incoming mails are stored in var/tmp directory and >>>> dont move to queue. >>>> This situation persists from 10 minutes to few hours. >>>> It's strange because queuefill is set to 1 minute and in the queue are >>>> not more than 100 messages. What does exactly mean "wakeup time=none" and >>>> how can I affect it? >> >>> It means that all available outgoing mail delivery slots are being used, so >>> at least one mail delivery attempt must conclude before any more mail will >>> be processed. >> >> I think there are many unused slots because I set MAXDELS and >> MAXHOST to larger number than number of messages in queue. After >> courier stop/courier start the courierd daemon reads messages from >> var/tmp, move messages to queue and tries to deliver them. After few >> minutes (20-30 minutes) courierd stops reading the var/tmp directory >> and do nothing for next 30 minutes - 1 hour even though the new mails >> are in var/tmp. How can I find out why courierd is so "lazy"? > Well, for starters you can actually look at your syslog file. Your syslog > file is going to tell you exactly what's happening on your server. And by > "looking" I don't mean looking just at 2 or 3 lines, but reading the entire > mail log in question for the period of time. > You really have not provided any useful information that even begins to > explain what's going on your server. Ok, maybe this information is useful. I finally found out where is problem. After running command "courier restart" courier doesn't deliver any mail until restart is done. Restart persists from 5 min to 2 hours (from courier man page: "courier restart" waits for all current deliveries to complete before restarting.). I need run this command due to update of configuration files. -- Regards, Jan Stanik Jan Stanik [EMAIL PROTECTED] Nextra s.r.o. ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
