It is not that my server is getting loaded up because of the mails. After I limt the number of concurrent lmtp connections I am able to reduce the db lock errors to a great extent. Now I have set max lmtp processes as 100 , But what will happen if my user mailboxes grow to 4000 from todays 850 then the mails will be delayed forever. By the time there will be the next batch to process.At 11:52 +0530 Ramprasad A Padmanabhan wrote: >Is there an API available with which I can directly write to lmtp >instead of sending a mail Er.. LMTP? :) >I am presently using postfix and sending the mail, But I believe that >calling an smtp agent has its own overheads. >I am sending 10-15 messages to around 850 mailboxes every hour using >postfix and aliases. The problem is there are too many lmtp processes >and I get lmtp lock errors too often You're asking the wrong list! I believe that's really quite a small message load, and that postfix can talk LMTP over a unix socket directly. Are the lmtp processes "lmtpd" or "deliver" ?
So I thought if there was a way of directly writing to lmtp and to all mailboxes at the same time I will do better
---------------------------------------------------------------- NETCORE SOLUTIONS *** Ph: +91 22 5662 8000 Fax: +91 22 5662 8134
MailServ: Email, IM, Proxy, Firewall, Anti-Virus, LDAP Fleximail: Mail Storage, Management and Relaying http://www.netcore.co.in Emergic Freedom: Linux-based Thin Client-Thick Server Computing http://www.emergic.com BlogStreet: Top Blogs, Neighborhoods, Search and Utilities http://www.blogstreet.com Rajesh Jain's Weblog on Technology:http://www.emergic.org ----------------------------------------------------------------
