Re: master not respawning properly under OpenBSD 2.8

2001-02-05 Thread Bitt Faulk
Bitt Faulk wrote: > > Bitt Faulk wrote: > > > > I've compiled Cyrus 2.0.11 under OpenBSD. The master program runs, > > but it will spawn each subserver only once. > > A little followup > > I've been doing some more research, and it looks like the fd being > used to signal back to the mast

Re: master not respawning properly under OpenBSD 2.8

2001-02-05 Thread Bitt Faulk
Bitt Faulk wrote: > > I've compiled Cyrus 2.0.11 under OpenBSD. The master program runs, > but it will spawn each subserver only once. A little followup I've been doing some more research, and it looks like the fd being used to signal back to the master process is not connected to the pip

master not respawning properly under OpenBSD 2.8

2001-02-05 Thread Bitt Faulk
This is an odd one I've compiled Cyrus 2.0.11 under OpenBSD. The master program runs, but it will spawn each subserver only once. That is, I can telnet to port 143 and login and do stuff with the imap protocol once. But if it try it again, it answers the port, but never prints out the bann

Re: [info-cyrus] global sieve script

2001-02-05 Thread Timo Proescholdt
-- Stephen Fischer ([EMAIL PROTECTED]) wrote: > I would like to have each mail item run through a standard sieve > script on delivery before being run through the individual user's > script. Is this possible? > > I'm using cyrus 1.6.24 on solaris 8. not a direct solution for your problem, jus

Re: [info-cyrus] messages being marked as unread on 2.0.11 (again)

2001-02-05 Thread Lawrence Greenfield
If this happens often to a particular user, turn on telemetry logging. (Create the directory /var/imap/log/ and make sure it is writable by the cyrus user.) When the problem shows up, send me the log files. Note that logging can be very voluminous, so you don't want to leave it on a long time fo

Re: [info-cyrus] global sieve script

2001-02-05 Thread Lawrence Greenfield
Cyrus IMAP doesn't have this capability as distributed, so you'll have to make some source code changes if you'd like it to happen. If we ever revisit how Sieve scripts are handled, I'll keep this in mind as a possible enhancement. Larry Date: Mon, 5 Feb 2001 15:32:04 +1100 From: Stephen

Re: [info-cyrus] limit_fds() in 2.0.11

2001-02-05 Thread Lawrence Greenfield
This probably won't be a problem unless you have a very large number of simultaneous connections. I'm not sure what the default limit is for Linux. Larry Date: 5 Feb 2001 10:37:27 ARST From: Ramiro Morales <[EMAIL PROTECTED]> Hello cyrus users, I'm running 2.0.11 in a Red Hat Lin

[info-cyrus] limit_fds() in 2.0.11

2001-02-05 Thread Ramiro Morales
Hello cyrus users, I'm running 2.0.11 in a Red Hat Linux 6.2 (kernel 2.2.16) I'm getting this message in syslog: master: unable to unlimit the number of file descriptors avialable (sic) Running master thru strace I find: setrlimit(RLIMIT_NOFILE, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINIT

[info-cyrus] messages being marked as unread on 2.0.11 (again)

2001-02-05 Thread jbeker
Hello Everyone, I really feel bad dragging this problem out again, but it is still happeneing. I am getting reports from several of my employees (myself included) about messages randomly being marked as unread in their mailboxes. In discussions on this list people seem to blame MS Ou

[info-cyrus] Re: mailboxes.db

2001-02-05 Thread jean-marc delpech
Thanks, Scot it works well now (I forget to say I installed Cyrus 2.0.11) In the new doc. I read that "crash in reconstruct now fixed" but when I try to do cyrus>reconstrution -m recontructing mailboxes.db currently not supported. What is the difference to rebuild mailboxes.db between your way and