Re: [sendmail] lmtp, cyrusv2d, shared folders and case
Andrzej Adam Filip a écrit : nodens2099 nodens2...@gmail.com wrote: ./socketmapClient.pl unix:/var/run/cyrus/socket/smmap cyrus +Hosting/ab...@domain.com +Hosting/ab...@domain.com = OK +Hosting/ab...@domain.com So socketmap daemon works as expected. Sendmail's maps traditionally turn looked up key into lowercase. It can be (usually) turned off by adding -f switch to map definition. [ I have reported missing -f in socket as bug myself :-) ] Thanks ! It works now that I have added the -f swith to Kcyrus in mrs_cyrus m4. -- Clement Hermann (nodens) - L'air pur ? c'est pas en RL, ça ? c'est pas hors charte ? Jean in L'Histoire des Pingouins, http://tnemeth.free.fr/fmbl/linuxsf/ Vous trouverez ma clef publique sur le serveur public pgp.mit.edu. Please find my public key on the public keyserver pgp.mit.edu. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Graceful degradation in overload conditions
On 04 Apr 2009, at 09:19, Gary Mills wrote: What about imapd and pop3d daemons, which also consume resources? Are limits a good idea here too? Users will complain to the help desk when those limits are reached, of course. Can the msg/shutdown file be used to control imapd processes in a nicer manner? I typically set the lmtpd limits very low, i.e., just above provisioned demand, because, as you say, inbound mail can queue. Setting imapd popd limits at somewhat higher than peek demand causes a fairly user friendly service degradation: mail delivery more or less stops, mail reading can continue, but that too will stop before load is so bad that nothing can be done. I also tend to actively monitor server load, so in extreme situations I can, e.g., stop or severely limit mail delivery or other lesser services to favor more important services. At some point, tho, you just need to add more capacity. :wes Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html