Re: new install, error when connecting, BYE Fatal Error: can't write proc file

On Mon, 23 May 2005, Mark Nernberg wrote: Ok. I got the issues with compile_et com_err worked out (by specifying --with-com-err=/usr/local/dist/cyrus-imapd-2.2.10 in ./configure). Now that its compiled, I need to test it (duh!). When connecting via telnet to localhost 143, I get the

Re: [WORKAROUND SUCCESS] Re: et_list com-err vs imapd v2.2.12 on OSX 10.4.1

On Mon, 23 May 2005, OpenMacNews wrote: they come with the release distro: Fine, so just remove them, let them be regenerated, and move on with life. huh? Huh what, you said you did just this. and shared with you the results of making 'it' work on OSX 10.4.1. i've been trying to be

Re: [WORKAROUND SUCCESS] Re: et_list com-err vs imapd v2.2.12 on OSX 10.4.1

That was a summary not how it came across. fair nuf. The ultimate fix upstream is for these files to not be included dealer's choice, of course but I can't go back in time to fix 2.2.12. really wasn't asking/expecting you to ... thx for your help! cheers, richard --- Cyrus Home Page:

Google关键词广告价格大揭秘:

Google: Google?4000?6000?8000?,? Google: 100-900/,() 900-2800/,() ,..Google,. QQ:496349908 475079053MSN:[EMAIL PROTECTED]:0592-8458661

Re: (Silly flame war continues) Re: configure fails on Mac OS X 10.4

On May 23, 2005, at 04:41 PM, Rich Cook wrote:Nice sentiments!   And great language!  Thanks!   You continue to live up to your image.  Look you idiot, messages sent off-list require permission to post on list, what part of that don't you understand?The fact that you have some mental issues is of

MURDER : tuning for increasing load

Hello, running CyrusIMAP 2.2.8 on Debian Sarge, with a murder of 2 frontends 3 backends, (4 4) at the end. I have to deal with increasing charge of by now 500 users that will grow up to 100 000. All mailboxes exist, for a 65Mb mailboxes.db on mupdate 1- Mupdate slows down informing Frontends

cyrus imap badlogin response delay

Hello, When there is a bad login, the answer is very long. I want to get if faster even if it's worst for security purpose. I've tried to find an answer about that question, buit nothing evident. I'm using cyrus imap 2.2.12. sasl_pwcheck_method: saslauthd sasl_mech_list: PLAIN

Re: MURDER : tuning for increasing load

I have to deal with increasing charge of by now 500 users that will grow up to 100 000. All mailboxes exist, for a 65Mb mailboxes.db on mupdate Is murder even necessary for such a configuration? Based on the numbers on Cyrus' pages, I assumed 200k accounts on one big, beefy box would be ok

Re: MURDER : tuning for increasing load

John Madden wrote: I have to deal with increasing charge of by now 500 users that will grow up to 100 000. All mailboxes exist, for a 65Mb mailboxes.db on mupdate Is murder even necessary for such a configuration? Based on the numbers on Cyrus' pages, I assumed 200k accounts on one big,

Re: MURDER : tuning for increasing load

In fact, 100 000 users represent more or less 600 000 folders subfolders. The choice of murder is high availability, even if one backend falls down, only 25% of the users will loose the mail service. Each server has 2 CPU 5 GB RAM. Any idea on optimizing Berkeley DB cache? Laurent. John

Re: MURDER : tuning for increasing load

John Madden wrote: I have to deal with increasing charge of by now 500 users that will grow up to 100 000. All mailboxes exist, for a 65Mb mailboxes.db on mupdate Is murder even necessary for such a configuration? Based on the numbers on Cyrus' pages, I assumed 200k accounts on one big,

Re: MURDER : tuning for increasing load

In fact, 100 000 users represent more or less 600 000 folders amp; subfolders. The choice of murder is high availability, even if one backend falls down, only 25% of the users will loose the mail service. I see. Any idea on optimizing Berkeley DB cache? I assume reading

lockers causing messages to bounce

Hello! I've been running cyrus imap for several years. Last night I upgraded one of my two imap servers to version 2.2.12 (from 2.0.11). This morning one of my users received this bounced message (mailj is a cname): --- This is the Postfix

frontend can see mailboxes but not messages

This my first time setting up a murder. I can get the frontend too see all the mailboxes, but when I try to read a message, or even list the messages in a mailbox, the operation just times out. Anyone know what the likely cause is? We are running 2.3 from cvs. Our proxy_authname is murder.

murder or not murder

Hi, I'm facing some design issue here :-) I need to create some big nice mail architecture, which should be able to grow nicely. So, I have a big nfs nas, and, I have these small xeon 2.8 with 1G of ram. I'll also need virtual domains. So, I'm wondering, should I use a front-end/back-end

Re: murder or not murder

I need to create some big nice mail architecture, which should be able to grow nicely. So, I have a big nfs nas, and, I have these small xeon 2.8 with 1G of ram. See the docs -- Cyrus + NFS = No. -- John Madden UNIX Systems Engineer Ivy Tech State College [EMAIL PROTECTED] --- Cyrus

RE: murder or not murder

A few questions: How many accounts are you expecting??? How many messages a day are you expecting??? Are you planning on allowing quotas??? If so, how much space are you going to give each user??? Are you planning on running some sort of web mail app??? -- Jason

Sieve script problem

Hi, I am running avelsieve-1.0.0 under squirrelmail-1.4.4 with Cyrus-imapd-2.2.12 and I am having an issue with a filter that uses the 'is equal to' comparator. The following script entry generated by avelsieve rejects all messages regardless of the 'From' address: header :value eq

Re: Cyrus IMAP4 v2.1.18 no login via SSL

Hi folks, the matter appears to cross-post through every module on my machine :( Intro for the LDAP specialists: I have Cyrus-Imap SASL authenticate with ldapdb auxprop. ldapdb uses ldaps:// for the LDAP server. All works well if I try with telnet mail imap, or even with openssl s_client