- Original Message -
From: "Ing. Andrea Vettori" <[EMAIL PROTECTED]>
> Hi,
>
> I have a Cyrus installation with about 300 mailboxes, many of them with
> a lot of messages inside (the record is 21000).
> I have the following problem that I think is not related to Cyrus.
> Excuse me if I'm
Dear Ken,
Thanks for the suggestion. I'll do that tomorrow. I managed to
get it to convert all the DBs to skiplist (except subs which are flat
files) and it seems to be working a treat. No DB4 or PANIC errors in the
log files and going well. I wish I'd never set eyes on BDB but I learn
from my mis
Dear Mark,
Thanks for the help. Your idea worked a treat. I also had to mess around
with the files in the db directory but I worked all that out it seemed
to work okay. Just in case anyone else wants to do that (as I've copied
this to the list). Here's what I did to convert the seen database from
Hi,
I have a Cyrus installation with about 300 mailboxes, many of them with
a lot of messages inside (the record is 21000).
I have the following problem that I think is not related to Cyrus.
Excuse me if I'm asking here but I hope someone had the same problem in
the past...
When outlook expres
Hello all,
If I am trying to reconstruct user.chris.Sent and user.chris.Save, should I be
able to simply run: "reconstruct -r user.chris"?
If so, it does not seem to work. I have to manually reconstruct every single
subdirectory.
If I misunderstood the "-r" option, what is it used for?
thanks,
Colin Bruce wrote:
Dear All,
Yet another problem with BDB (at least I think it is)
On a test system I think I have completely removed BDB. However, I still
get these errors showing up in the log files.
Apr 15 17:21:27 r118-1 ctl_cyrusdb[20562]: DBERROR db4: PANIC: Invalid argument
Apr 15 17:21:2
Dear All,
Yet another problem with BDB (at least I think it is)
On a test system I think I have completely removed BDB. However, I still
get these errors showing up in the log files.
Apr 15 17:21:27 r118-1 ctl_cyrusdb[20562]: DBERROR db4: PANIC: Invalid argument
Apr 15 17:21:27 r118-1 ctl_cyrus
Dear Mark,
Thanks for the info. That idea worked on my test system (which is a copy
of the live system). I'll try it on the real system tonight when everyone
has gone home. There are other problems now as well. I wish I'd never
heard of BDB :-(
Best wishes...
Colin
On Thu, 15 Apr 2004, Mark Keas
I don't know if that's the correct list to put this question. Please
forgive me if not the correct list and notice me where can i write
the problem.
--
I'm trying to use Cyrus with sasl + ldap authentication.
i get this error:
# cyradm --user cyrus localhost
IMAP Password:
Lo
> Since upgrading Cyrus imapd to 2.2.3, there have been no entries in
Logging has changed in 2.2. The logging facility can now be configured at
compile time and at least my rpms do it with '--with-syslogfacility=MAIL'.
That said you may have a closer look at how your cyrus got compiled.
Simon
>
> Hi,
>
> I'm using 2.2.3 and had no trouble with syslogd, I use
> local6.* instead of
> local6.debug.
> By the way local0 through local7 are made available by syslog
> to applications
> wishing to have a separate log file (man syslog.conf should
> tell you more).
>
> If local6.* doesn't chan
Our murder started to act a little strange some days ago:
Apr 15 13:17:43 frontend1 mupdate[21845]: successful mupdate connection to master
Apr 15 13:17:43 frontend1 mupdate[21845]: unready for connections
Apr 15 13:17:43 frontend1 mupdate[21845]: synchronizing mailbox list with master
mupdate se
Hi,
I'm using 2.2.3 and had no trouble with syslogd, I use local6.* instead of
local6.debug.
By the way local0 through local7 are made available by syslog to applications
wishing to have a separate log file (man syslog.conf should tell you more).
If local6.* doesn't change anything you should tr
> I've just had something similar, it was down to spacing in the
> syslogd.conf file, it really didn't like spaces - needed to be tabs. I
> think this is due to the file be parsed by m4.
>
> Neil.
Thanks Neil,
The local6.debug line was not using tabs, just a space, so I rewrote the
line using t
Rob,
Kinda "yes" and kinda "no". Since the transition is from an old ESYS
commercial version, there are no cyrus.* files anyway -- they changed them to
fdb.* and I have no idea whether the file has a similar format or not. So
the problem occur when no cyrus.* files. I also added an empty cyr
I've just had something similar, it was down to spacing in the
syslogd.conf file, it really didn't like spaces - needed to be tabs. I
think this is due to the file be parsed by m4.
Neil.
On Thu, 2004-04-15 at 16:04, Doug Koobs wrote:
> Since upgrading Cyrus imapd to 2.2.3, there have been no ent
Since upgrading Cyrus imapd to 2.2.3, there have been no entries in
/var/log/imapd.log. I did a little Googling, and learned that syslog is
actually doing the logging. syslog is running, the ps command shows:
root 1565 1 0 Apr10 ?00:21:33 syslogd -m 0
In /etc/syslog.conf, I have
Neil, open the files in question and modify the four real lines of the
script so that you have -I/install/location/lib to where the perl modules are.
This has been an ongoing bug that is indecently easy to fix, but Rob won't
accept any patches on it. He evidently thinks that installing modules in
Some further information :
Cyrus was configured with :
./configure --with-openssl=/usr/local/ssl --with-libwrap=/usr/local
--with-sasl=/usr/local
I had to move the sasl header files into the imap source tree under
sasl/ otherwise it complained they were not present.
The configure complained a
Thanks for that, I have now recompiled SASL and imap in the default
location, it seems the PREFIX is set in the Perl makefile for imap, and
thus it loads in the Cyrus tree instead of the Perl tree. My recompile
used default locations and now all is installed where I think it should
be. How ever it
On Thursday 15 April 2004 12:37, Neil Marjoram X 663711 wrote:
> I have found the Cyrus Perl module located in the directory I installed
> cyrus in : /opt/cyrus/lib/perl5/site_perl/5.8.0/sun4-solaris/. How do I
> get it installed in the Perl tree?
Did you install cyrus imap from a precompiled pack
-Original Message-
Trying to do mail filtering to cyrus imapd using procmail instead of
sieve. I'm putting "| [cyr]deliver -m blah-folder" into my
"~/.procmailrc", instead of the global "/etc/procmailrc"; this fails:
"couldn't connect to lmtpd: Permission denied_ procmail: Program
failu
I have searched and searched but have not fond the answer to my
problems.
My server is a Sun Ultra 5 running latest Solaris 9 + Marches patches.
First problem is when I run cyradm I get the message :
Can't locate Cyrus/IMAP/Shell.pm in @INC (@INC contains:
/usr/local/lib/perl5/5.8.0/sun4-solaris
23 matches
Mail list logo
