Re: libwrap compiled into Cyrus IMAPd
Hmm, have you installed libwrap-devel? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: 2.2.6 does not compile due to ./configure bug
Hi again, Olaf Zaplinski wrote: Hi all, imapd-2.2.6 does not compile, even 2.2.4 does not. The latest release that compiles well is 2.2.3. my configure line: [...] I found the solution! Someone included a bug here, I guess, it was with version 2.2.4. I had to edit imap/Makefile.in, in line 66 change CPPFLAGS = -I.. -I$(srcdir)/../lib @COM_ERR_CPPFLAGS@ @SIEVE_CPPFLAGS@ @CPPFLAGS@ @SASLFLAGS@ to CPPFLAGS = -I.. -I$(srcdir)/../lib -I$(srcdir)/../sieve @COM_ERR_CPPFLAGS@ @SIEVE_CPPFLAGS@ @CPPFLAGS@ @SASLFLAGS@ and imapd compiles fine. Any comments on this? It would be great if this would not become another "ancient" bug some day like this "/usr/local/local" bug that is there since 2.0. Olaf --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
2.2.6 does not compile due to ./configure bug
Hi all, imapd-2.2.6 does not compile, even 2.2.4 does not. The latest release that compiles well is 2.2.3. my configure line: ./configure \ --with-cyrus-user=cyrus \ --with-cyrus-group=mail \ --with-cyrus-prefix=/opt/cyrus-imapd \ --disable-sieve The problem is exactly that 2.2.6 tries to enable sieve, no matter what I say: 2.2.3: ### Making all in /usr/src/cyrus-imapd-2.2.3/man make[1]: Entering directory `/usr/src/cyrus-imapd-2.2.3/man' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/cyrus-imapd-2.2.3/man' 2.2.6: ### Making all in /usr/src/cyrus-imapd-2.2.6/man make[1]: Entering directory `/usr/src/cyrus-imapd-2.2.6/man' creating sieveshell.1 pod2man ./../perl/sieve/scripts/sieveshell.pl > ./sieveshell.1 creating imapd.conf.5 ./../tools/config2man ./../lib/imapoptions > ./imapd.conf.5 make[1]: Leaving directory `/usr/src/cyrus-imapd-2.2.6/man' compiling then stops with: gcc -c -I.. -I./../lib -I../et -DHAVE_CONFIG_H -g -O2 \ version.c version.c:66: sieve_interface.h: No such file or directory make[1]: *** [version.o] Error 1 make[1]: Leaving directory `/usr/src/cyrus-imapd-2.2.6/imap' Regards Olaf --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: cyradm auth problem
Chris J. Babyak wrote: Hi all, I'm having problem with cyradm and creating mailboxes. Try: cyradm -u cyrus localhost Olaf --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: 9800XXXXXXXXXXXXXXXX+100XXXXXXXXXXXXXXXXXXXX,XXXXXX50XX
John Hughes wrote: > What kind of anti-spam is this list using? It doesn't seem to be > working too well. It's using no spam protection at all... :-(
Re: 'couldn't change to partition /var/spool/imap'
Ken Murchison wrote: > > Olaf Zaplinski wrote: > >>Hi *, >> >>has someone had this error also while installing 2.0.16? >> >>$ /usr/src/cyrus-imapd-2.0.16/tools/mkimap >>reading configure file... >>i will configure directory /var/imap. >>i saw partition /var/spool/imap . >>you are using /var/imap/sieve as your sieve directory. >>done >>creating /var/imap... >>creating /var/imap/sieve... >>creating /var/spool/imap ... >>couldn't change to partition /var/spool/imapat (eval 1) line 157. >> >>$ ls -ld /var/spool/imap/ >>drwxr-x---2 cyrusmail 48 Apr 18 19:27 /var/spool/imap/ > > > Hmm. What are the permissions on the parent directories? If they are > not 'executable' by the user in question, then that user can't cd to > lower directories. > > Ken It's 0755 for /var and /var/spool - and simply cd'ing to /var/spool/imap as user cyrus is possible, file creation also. Olaf
'couldn't change to partition /var/spool/imap'
Hi *, has someone had this error also while installing 2.0.16? $ /usr/src/cyrus-imapd-2.0.16/tools/mkimap reading configure file... i will configure directory /var/imap. i saw partition /var/spool/imap . you are using /var/imap/sieve as your sieve directory. done creating /var/imap... creating /var/imap/sieve... creating /var/spool/imap ... couldn't change to partition /var/spool/imapat (eval 1) line 157. $ ls -ld /var/spool/imap/ drwxr-x---2 cyrusmail 48 Apr 18 19:27 /var/spool/imap/ Cheers Olaf
Re: delivery to imap AND OS users possible?
Schiemer, Markus wrote: > How can I manage the delivery of mails based upon the existence (OS/imap) of > the user? > [...] On Linux, this works (it's not from me, but Andrzej Filip). The bottom of my mc file reads: Klocaluser hash /etc/mail/localuser LOCAL_RULESETS SLocal_localaddr R$* $: < $(localuser $1 $: $) > $1 R<$-:$+> $* $# $1 $@ $2 $: $3 R<$-> $*$# $1 $: $2 In /etc/mail/localusers, I have one line per Cyrus recipient: jdoe cyrus:localhost Cheers Olaf
Re: RH7.2, db-4.0.14 and cyrus-imap-2.1.3
Mathias, please look if you have db3/ and/or db.h in /usr/include. If yes: move them elsewhere while ./configuring and compiling. when configuring, try --with-bdb-libdir=/usr/local/BerkeleyDB.4.0/lib and --with-bdb-incdir=/usr/local/BerkeleyDB.4.0/include (or whereever your db-4 files reside). Cheers Olaf
Re: compile error in 2.1.3
It's solved - never ever compile db-4 with './configure --with-uniquename'! Cheers Olaf
compile error in 2.1.3
Hi *, compilation fails on one machine here: user.c: In function `user_delete': user.c:115: warning: unused variable `pat' user.c: At top level: user.c:84: warning: `user_deleteacl' defined but not used gcc -c -I. -I.. -I../sieve -I. -I./../lib -I./../acap -I../acap -I./../et -I./../sieve -I/usr/include/db3 -I/usr/local/BerkeleyDB.4.0/include -I/usr/local/include -DHAVE_CONFIG_H -Wall -g -O2 \ seen_db.c gcc -c -I. -I.. -I../sieve -I. -I./../lib -I./../acap -I../acap -I./../et -I./../sieve -I/usr/include/db3 -I/usr/local/BerkeleyDB.4.0/include -I/usr/local/include -DHAVE_CONFIG_H -Wall -g -O2 \ notify_unix.c notify_unix.c: In function `notify': notify_unix.c:36: warning: unused variable `wait' notify_unix.c:35: warning: unused variable `write_template' notify_unix.c:35: warning: unused variable `read_template' notify_unix.c:30: warning: unused variable `buf' gcc -c -I. -I.. -I../sieve -I. -I./../lib -I./../acap -I../acap -I./../et -I./../sieve -I/usr/include/db3 -I/usr/local/BerkeleyDB.4.0/include -I/usr/local/include -DHAVE_CONFIG_H -Wall -g -O2 \ idle_idled.c rm -f libimap.a ar cr libimap.a append.o mailbox.o mboxlist.o mupdate-client.o mboxname.o message.o config.o imap_err.o mupdate_err.o proc.o setproctitle.o convert_code.o duplicate.o saslclient.o acapmbox.o signals.o annotate.o search_engines.o squat.o squat_internal.o base64.o imapparse.o telemetry.o user.o seen_db.o notify_unix.o idle_idled.o ranlib libimap.a gcc -L/usr/local/lib -Wl,-rpath,/usr/local/lib -L/usr/local/BerkeleyDB.4.0/lib -Wall -g -O2 -o imapd \ ../master/service.o pushstats.o imapd.o index.o tls.o version.o libimap.a ../acap/libacap.a ../lib/libcyrus.a -lsasl2 -lrt -lssl -lcrypto -lfl -ldb-4.0 -lresolv ../et/libcom_err.a -lwrap -lnsl ../lib/libcyrus.a(cyrusdb_db3.o): In function `mysync': /usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:232: undefined reference to `txn_checkpoint' ../lib/libcyrus.a(cyrusdb_db3.o): In function `myarchive': /usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:257: undefined reference to `log_archive' /usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:278: undefined reference to `log_archive' /usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:306: undefined reference to `log_archive' ../lib/libcyrus.a(cyrusdb_db3.o): In function `gettid': /usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:379: undefined reference to `txn_id' /usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:382: undefined reference to `txn_id' /usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:392: undefined reference to `txn_id' ../lib/libcyrus.a(cyrusdb_db3.o): In function `mystore': /usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:671: undefined reference to `txn_id' /usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:681: undefined reference to `txn_id' ../lib/libcyrus.a(cyrusdb_db3.o):/usr/src/cyrus-imapd-2.1.3/lib/cyrusdb_db3.c:695: more undefined references to `txn_id' follow collect2: ld returned 1 exit status make[1]: *** [imapd] Error 1 make[1]: Leaving directory `/usr/src/cyrus-imapd-2.1.3/imap' make: *** [all] Error 1 I'm using the following configure line: CPPFLAGS=-I/usr/local/BerkeleyDB.4.0/include \ LDFLAGS=-L/usr/local/BerkeleyDB.4.0/lib \ ./configure --with-cyrus-user=cyrus --with-cyrus-group=mail --with-cyrus-prefix=/opt/cyrus --with-idle=idled --with-notify=unix Any ideas? All I changed compared to the old config (which compiled, but did not run well) was: removing --with-idle=no --disable-sieve --without-notify and adding --with-idle=idled --with-notify=unix instead. Cheers Olaf
lock files in /var/imap/socket
Hi *, just one question: shouldn't be there no *.lock files in /var/imap/socket when the imap server is absolutely idle? I see the following here: binky:~ # l /var/imap/socket/ total 1 drwxr-xr-x2 cyrusmail 155 Mar 28 23:05 ./ drwxr-x--- 12 cyrusmail 362 Mar 31 23:35 ../ srwxrwxrwx1 cyrusroot0 Nov 27 10:45 idle= -rw---1 cyrusmail0 Mar 27 14:50 imap.lock -rw---1 cyrusmail0 Mar 25 23:34 imaps.lock srwxrwxrwx1 root root0 Mar 28 23:05 lmtp= -rw---1 cyrusmail0 Mar 25 23:35 lmtpunix.lock I also have several imapd and lmtp processes here. Olaf
what to backup?
Hi *, I have much trouble with imap-2.2 and sasl-2, so I thought I just had to install Debian Potato, db-3.3 (for sasl-1 and sendmail), db-4.0 and sasl-2 and imap-2.2. Reason: Debian Potato does not know anything about db>=3. But it did not work, 'master' now segfaults on that test machine. For me, sasl-2 and imapd-2.2 are still to be considered experimental, nothing to try on production servers since they cause trouble on Debian Potato *and* SuSE 7.3... :-( Now what I would like to know: What will I have to backup if I would like to go back to imapd-2.0? Of course /var/spool/imap/user since these are the message contents. But how about /var/imap? What files do I have to backup here? I don't want to make mistakes since 'reconstruct' does not do its job which some of us here know well... Olaf
Re: bug in imapd-2.1.3 / Berkeley DB
Ken Murchison wrote: > > Olaf Zaplinski wrote: > >>Clifford Thurber wrote: >> >>>What do you mean when you say they don't disappear? Can you be more >>>specific? >> >>Yes, right now I have 5 processes named 'imapd -s' and 2 named 'lmtp' in my >>process list. They will stay there forever until I restart cyrus-imapd. And >>when the first user logons after that, they are recreated. > > > Look at /etc/cyrus.conf. Are you preforking these processes? Nope, they all are configured with 'prefork=0' Olaf
Re: bug in imapd-2.1.3 / Berkeley DB
Clifford Thurber wrote: > What do you mean when you say they don't disappear? Can you be more > specific? Yes, right now I have 5 processes named 'imapd -s' and 2 named 'lmtp' in my process list. They will stay there forever until I restart cyrus-imapd. And when the first user logons after that, they are recreated. Olaf
Re: bug in imapd-2.1.3 / Berkeley DB
Now it works - in /usr/include, I had to delete db.h and the db3 directory. But my problem is not resolved: I still have several imapd and sometimes one or more lmtp processes which never disappear. Olaf
Re: sieve with sendmail 8.12 ... permissions problems ...
Marc G. Fournier wrote: > Anyone using 8.12 yet? Just delivered an email to an account that has > sieve filtering turned on, and get the following in the maillog: > > Mar 26 13:39:32 nsnet sendmail[38611]: NOQUEUE: SYSERR(cyrus): can not >chdir(/var/spool/clientmqueue/): Permission denied > > What should permissions/ownership be for this to work? Hmmm... did you try deleting /etc/mail/submit.cf? I remember some trouble I had some day, and deleting that file fixed it. Olaf
Re: bug in imapd-2.1.3 / Berkeley DB
Hi Prune, Prune wrote: > can you add the result of the 'configure' ? look at the begining when it > tests for gcc do you mean this? checking whether the C compiler (gcc -I/usr/local/BerkeleyDB.3.3/include -L/usr/local/BerkeleyDB.3.3/lib) works... yes checking whether the C compiler (gcc -I/usr/local/BerkeleyDB.3.3/include -L/usr/local/BerkeleyDB.3.3/lib) is a cross-compiler... no Later on it finds the db-3.3 libs: checking for db_create in -ldb-4.0... no checking for db_create in -ldb-4... no checking for db_create in -ldb4.0... no checking for db_create in -ldb4... no checking for db_create in -ldb-3.3... yes > also try to put -I flags in CFLAGS also. it sometimes help. Not here. :-( Perhaps I should tell why I want to try another db version: my server works fine, but I have several imap and lmtp processes here which never stop. Cheers Olaf
bug in imapd-2.1.3 / Berkeley DB
Hi *, following bug occured: 1. CPPFLAGS=-I/usr/local/BerkeleyDB.3.3/include \ LDFLAGS=-L/usr/local/BerkeleyDB.3.3/lib \ ./configure 2. make 3. make install 4. start of cyrus => 'incorrect version of Berkeley db: compiled against 3.1.17, linked against 3.3.11' So I re-started 3. and voila: gcc -c -I/usr/include/db3 -I/usr/local/BerkeleyDB.3.3/include [...] Although I told configure where to look for db3, it searches on its own and finds the system's db-3.1.17 instead of by self built db-3.3.11. Workaround: vi `find . -name Makefile` :-( (This did not really help because sasl-2.1.1 does not like db-3.3, saslpasswd2 crashes.) Regards Olaf
Re: How to shrink /var/spool/imap/db/* ...
Ken Murchison wrote: > > "Marc G. Fournier" wrote: > >>Is it possible? >> > > http://www.sleepycat.com/docs/utility/db_archive.html > > FYI, we are working on adding functionality like this to ctl_cyrusdb. Did I get that right? What I did: -- 1. -- binky:/var/imap/db # /etc/init.d/cyrus-imapd stop -- 2. -- binky:/var/imap/db # du -s /var/imap/ 11510 /var/imap binky:/var/imap/db # du -s /var/spool/imap/ 6175/var/spool/imap binky:/var/imap/db # l total 14797 drwxr-xr-x2 cyrusmail 185 Jan 30 18:55 ./ drwxr-x--- 11 cyrusmail 331 Jan 24 11:47 ../ -rw---1 cyrusmail 8192 Jan 30 16:27 __db.001 -rw---1 cyrusmail 11550720 Jan 30 16:27 __db.002 -rw---1 cyrusmail98304 Jan 30 16:27 __db.003 -rw---1 cyrusmail 270336 Jan 30 16:27 __db.004 -rw---1 cyrusmail24576 Jan 30 16:27 __db.005 -rw---1 cyrusmail 3595221 Jan 30 18:55 log.01 Yup, same situation. -- 3. -- binky:/var/imap/db # db_archive -s deliver.db mailboxes.db tls_sessions.db So /var/imap/db/* are obsolete files, right? Let's see... -- 4. -- binky:/var/imap/db # rm * binky:/var/imap/db # l total 1 drwxr-xr-x2 cyrusmail 35 Jan 30 18:58 ./ drwxr-x--- 11 cyrusmail 331 Jan 24 11:47 ../ -- 5. -- binky:/var/imap/db # /etc/init.d/cyrus-imapd start Initializing Cyrus IMAPD: done -- 6. -- binky:/var/imap/db # l total 11161 drwxr-xr-x2 cyrusmail 185 Jan 30 18:58 ./ drwxr-x--- 11 cyrusmail 331 Jan 24 11:47 ../ -rw---1 cyrusmail 8192 Jan 30 18:58 __db.001 -rw---1 cyrusmail 11550720 Jan 30 18:58 __db.002 -rw---1 cyrusmail98304 Jan 30 18:58 __db.003 -rw---1 cyrusmail 270336 Jan 30 18:58 __db.004 -rw---1 cyrusmail24576 Jan 30 18:58 __db.005 -rw---1 cyrusmail 333 Jan 30 18:58 log.01 I really did not win much space here, but at least the log file has gone. -- 7. -- binky:/var/imap/db # db_archive -s deliver.db tls_sessions.db Why is it no longer necessary to back up mailboxes.db? At least all IMAP folders and messages seem to be there... Olaf
Re: error log entries with 2.1
Rob Siemborski wrote: > On Fri, 25 Jan 2002, Olaf Zaplinski wrote: > > >>Can someone tell me what's going on here please? >> > > The "unable to get entry point" messages are Mostly Harmless (not all > modules implement all of a client, server, canon_user, and auxprop > plugin). In fact, none do. > > These messages are logged at the LOG_DEBUG level so if you decrease the > level that syslog logs at they will go away. > > -Rob Thanks! Anyway, I just found this one in cyrus-imapd-2.1.1/doc/text/changes: "Changes to the Cyrus IMAP Server Since Version 1.5.19 [...] * Annoying (and confusing) lines in syslog every time a message was delivered if deliver was compiled using dbm saying that deliver was "unable to fetch entry" have been removed." ;-) Olaf
error log entries with 2.1
Hi *, yesterday I switched from sasl-1.5.27 to sasl-2.1.0 and from imapd-2.0.16 to imapd-2.1.1. Everything works fine since then, just as before. But I get unknown log entries. When one mail arrives, the log entries are like this in chronological order: ==> mail <== Jan 25 19:08:40 binky sendmail[990]: g0PI8dox000988: to=<[EMAIL PROTECTED]>, delay=00:00:01, xdelay=00:00:01, mailer=cyrus, pri=30728, dsn=2.0.0, stat=Sent ==> imapd <== Jan 25 19:08:39 binky lmtpd[992]: accepted connection Jan 25 19:08:39 binky lmtpd[992]: lmtp connection preauth'd as postman Jan 25 19:08:39 binky lmtpd[992]: duplicate_check: <[EMAIL PROTECTED]> user.olaf0 Jan 25 19:08:40 binky lmtpd[992]: mystore: starting txn 2147483974 Jan 25 19:08:40 binky lmtpd[992]: mystore: committing txn 2147483974 Jan 25 19:08:40 binky lmtpd[992]: duplicate_mark: <[EMAIL PROTECTED]> user.olaf1011982119 ==> messages <== Jan 25 19:08:39 binky lmtpd[992]: unable to get entry point sasl_auxprop_plug_init: /usr/lib/libsasl2.so.2: undefined symbol: sasl_auxprop_plug_init Jan 25 19:08:39 binky lmtpd[992]: unable to get entry point sasl_canonuser_init: /usr/lib/libsasl2.so.2: undefined symbol: sasl_canonuser_init Jan 25 19:08:39 binky lmtpd[992]: unable to get entry point sasl_auxprop_plug_init: /usr/lib/libsasl2.so.2: undefined symbol: sasl_auxprop_plug_init Jan 25 19:08:39 binky lmtpd[992]: unable to get entry point sasl_canonuser_init: /usr/lib/libsasl2.so.2: undefined symbol: sasl_canonuser_init Jan 25 19:08:39 binky lmtpd[992]: unable to get entry point sasl_auxprop_plug_init: /usr/lib/libsasl2.so.2: undefined symbol: sasl_auxprop_plug_init Jan 25 19:08:39 binky lmtpd[992]: unable to get entry point sasl_canonuser_init: /usr/lib/libsasl2.so.2: undefined symbol: sasl_canonuser_init Can someone tell me what's going on here please? TIA Olaf
Re: sieve connexion
Luca Olivetti wrote: > He'll probably have the same problem with sieveshell, at least I do: /me too: olaf@binky:~ > sieveshell Can't locate Cyrus/SIEVE/managesieve.pm in @INC (@INC contains: /usr/lib/perl5/5.6.0/i586-linux /usr/lib/perl5/5.6.0 /usr/lib/perl5/site_perl/5.6.0/i586-linux /usr/lib/perl5/site_perl/5.6.0 /usr/lib/perl5/site_perl .) at /usr/local/bin/sieveshell line 42. BEGIN failed--compilation aborted at /usr/local/bin/sieveshell line 42. olaf@binky:~ > perl -v This is perl, v5.6.0 built for i586-linux Olaf
Re: Delete button grayed out in Netscape
"Aaron M. Stromas" wrote: > > On the good side I finally configured sandmail to work with Cyrus. The > question now is why Netscape 4.76 won't let me delete mail from th > INBOX? The "delete" button is grayed out. Mozilla works fine, however... > > Is there something that can be done to restore Netscape's capability to > delete mail? TIA, It's a Netscape bug, you can still delete mails with Ctrl- (Windows) or Alt- (Unix) D. At least that's true for me (IMAP 2.0.12 and Netscape 4.76) Olaf
Re: Where does configure look for berkeleyDB?
Try export LDFLAGS="-L/usr/local/BerkeleyDB.3.2/lib" export CFLAGS="-I/usr/local/BerkeleyDB.3.2/include" before ./configure Good luck! I never got IMAPD 2.0.12 compiled on a Debian 2.2 'potato' box, but this helped me to compile Courier IMAPD... ;-) Olaf jennyw wrote: > > I'm trying to install Cyrus imapd on a Debian 2.2 box. I downloaded > BerkeleyDB from Sleepycat's site, and followed the instructions. This > installed the software into /usr/local/BerkeleyDB.3.2. I then tried to > run configure, but it didn't work. I realized I had an older version of > Berkeley DB installed in /usr/lib, so I deleted libdb.a and replaced it > with a symlink to the new libdb.a. I also did ln -s > /usr/local/BerkeleyDB.3.2/bin/* /usr/local/bin. This didn't work, > either. > > Looking through the configure script, it seems like it's looking for > something called db_create, which doesn't exist (there are a lot of > other db_* files in the bin directory). Any suggestions? > > Thanks! > > Jen
Re: Compilation probs:- ldb-3
Michael Fair wrote:
>
> When I installed cyrus on my Debian Potato
> system I compiled SASL to use GDBM instead
> of Berkeley DB.
>
> The rest of the system used db3.
>
> -- Michael --
I tried this ('--with-dblib=gdbm') and got:
sasldblistusers.c: In function `listusers':
sasldblistusers.c:312: warning: unused parameter `cb'
sasldblistusers.c: In function `main':
sasldblistusers.c:332: warning: passing arg 1 of `listusers' from
incompatible pointer type
sasldblistusers.c:332: too many arguments to function `listusers'
make[2]: *** [sasldblistusers.o] Error 1
Olaf
> - Original Message -
> From: "Olaf Zaplinski" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 05, 2001 3:54 AM
> Subject: Re: Compilation probs:- ldb-3
>
> > GOMBAS Gabor wrote:
> > >
> > > On Wed, Apr 04, 2001 at 11:20:18PM +0200, Olaf Zaplinski wrote:
> > >
> > > > For me, the only way to make it work is to get a distro with 'built
> in' db3
> > > > (SuSE 7.1). Reason: even if you get all db3 stuff installed and
> configure
> > > > accepts it (yup, that's what I did on a Debian box), the binary will
> be
> > > > linked with db2 => segfaults. And of course you cannot just deinstall
> db2...
> > >
> > > I got curious and tried to build cyrus-imapd-2.0.12 on a Debian/Woody
> box
> > > (DB3 built from sources), and could not find a single binary that got
> linked
> > > with DB2. Something is really broken on your system. My first guess
> would
> > > be you forgot to rebuild Cyrus-SASL with DB3...
> >
> > Yup, it is Debian that must be broken... I have two potato boxes here
> (woody
> > is still unstable and so 'forbidden' to be used as a production system
> > here).
> >
> > I can compile the cyrus stuff with db3 just like Mark Sweney explained to
> > us. Even sendmail compiles without errors when linked against db3, but it
> > then always segfaults on startup => no db3 for Debian potato.
> >
> > I am giving up. No IMAPD for our customers then... only for me with my
> SuSE
> > box... ;-)
> >
> > Olaf
> >
Re: Compilation probs:- ldb-3
GOMBAS Gabor wrote: > > On Wed, Apr 04, 2001 at 11:20:18PM +0200, Olaf Zaplinski wrote: > > > For me, the only way to make it work is to get a distro with 'built in' db3 > > (SuSE 7.1). Reason: even if you get all db3 stuff installed and configure > > accepts it (yup, that's what I did on a Debian box), the binary will be > > linked with db2 => segfaults. And of course you cannot just deinstall db2... > > I got curious and tried to build cyrus-imapd-2.0.12 on a Debian/Woody box > (DB3 built from sources), and could not find a single binary that got linked > with DB2. Something is really broken on your system. My first guess would > be you forgot to rebuild Cyrus-SASL with DB3... Yup, it is Debian that must be broken... I have two potato boxes here (woody is still unstable and so 'forbidden' to be used as a production system here). I can compile the cyrus stuff with db3 just like Mark Sweney explained to us. Even sendmail compiles without errors when linked against db3, but it then always segfaults on startup => no db3 for Debian potato. I am giving up. No IMAPD for our customers then... only for me with my SuSE box... ;-) Olaf
Re: Compilation probs:- ldb-3
paul wrote: > > Hi all, > > downloaded 2.0.12 and ran into problems during the ./configure process. > It bailed when looking for a properly configured db3 install. I didn't > have it, so I downloaded and installed the appropriate db3 and db3-devel > rpms from rpmfind.net. Still failed, which I thought was curious. So I > downloaded the latest db3 source, uninstalled the RPMS and did the > compile and install thing. This still did not fix the problem. > > Has anyone else had this experience? Are there some symbolic links I > need to have in place or something? > > I'm away from the machine now, or I'd put up the full error message. > Perhaps someone else has encountered this and knows the solution though. > It's a Mandrake 7.2 distro. > > Best regards and thanks, > > Paul Dorman. For me, the only way to make it work is to get a distro with 'built in' db3 (SuSE 7.1). Reason: even if you get all db3 stuff installed and configure accepts it (yup, that's what I did on a Debian box), the binary will be linked with db2 => segfaults. And of course you cannot just deinstall db2... :-( Olaf
segfault when starting master
Hi all, I have 2 Linux machines, they are almost identical: Kernel 2.2.18 cyrus-imapd-2.0.12 cyrus-sasl-1.5.24 Berkeley DB 3.1.17 openssl-0.9.6 sendmail 8.11.3 One is a SuSE 7.1 distro, the Berkeley DB and openssl came as a RPMs; the other one is a Debian 2.2, and it was hard work to get Berkeley DB compiled and installed. On the SuSE box, I did not much more than compiling and installing everything, and its cyrus imapd still works fine. On the Debian box I spent a lot of time on the Berkeley DB because several packages did not regognize it, or they segfault'ed when starting, but they do now except for imapd. Today I compiled everything needed and linked it against the Berkeley DB: sasl, sendmail and imapd. But now, whenever I start 'master', I get a segmentation fault. Any ideas? I don't know how to proceed and am about to cancel that imap server project. I *really* would love to fdisk that *&%!@ Debian box and install SuSE, but my boss says no, although I spent more than 4 times the time I spent on the SuSE box to have imapd up and running, and I am not finished yet. Could it be that some parts (libs?) of the Debian distribution are simply outdated? From time to time I find .deb packaged software which is significantly more outdated than the packages of other distros. Olaf
Re: sent items folder on inbox level
Tom Karches wrote: > [...] > I've never heard of being able to store all folders (including Inbox) at > the same level in Cyrus unless : > > - you are running Cyrus as an administrative user, which lets you create > folders anywhere you want. Running IMAP clients as an administrative > users is generally not a good idea Well, my OE logs in with a plain user account w/o admin permissions. > - you are not running a Cyrus server. I do, believe me! ;-) Olaf
Re: sent items folder on inbox level
"Scot W. Hetzel" wrote: > [...] > > 2. I have SASL with CRAM-MD5, Plain and Digest-MD5 but I can't use the > > secure authentication connection from outlook. I checked with imtest and > > sasl works with all auth method. Is outlook using something else? > > > When you compiled Cyrus-SASL, did you configure it with "--enable-login", as > this enables the LOGIN mech used by Outlook Express & Outlook. Well, I did not, but Cyrus works fine with German MS OE for me. I even have all folders on the top level: "Posteingang" (inbox), "Gesendete Objekte" (sent) and "Entwürfe" (drafts). Olaf
no big msgs?
Hi all, yesterday I wanted to download a big mail (6.5 MB) - but after about 10-20%, the mail clients stopped downloading. The clients: MS Outlook 97 (pop3) MS OE (imap) NS Messenger 4.76 (imap, Linux) I am lucky, I am root@my-mail-server, so I could scp the files I needed at home. Did anyone have this problem also? Olaf
Re: Default Mailbox / Inbox settings.
"Scot W. Hetzel" wrote: > [...] > see the following for more information: > > http://asg.web.cmu.edu/archive/message.php3?index=5091&array_index=2 > > P.S. Maybe the above should be added to the Cyrus-IMAP FAQ, as it appears > that I keep answering the same question. > > Scot Yup, that worked for me! I am not the one who asked, but I had the same problem. Okay, next question: How can I tell Netscape Messenger the same? Olaf
no folder creation
Hi all, now I have it all up and running... :-) But now the clients (Netscape 4, OE 5) don't work as expected: they see their INBOX, but the other folders (Trash, Sent...) can be created, but they are not shown and so cannot been used. Has anyone had that problem before? Olaf
perl ok now - next problem
Hi,
thanks a lot for the hints, I moved two directories from
/usr/local/lib/site_perl to /usr/lib/perl5... now it works, but I have the
next problem:
imtest says:
cyrus@ridcully:~ > imtest -m login -p imap localhost
C: C01 CAPABILITY
failure: prot layer failure
The log says then:
Mar 10 00:15:23 ridcully service-imapd[16290]: executed
Mar 10 00:15:23 ridcully service-imapd[16290]: unable to set close on exec:
Bad file descriptor
Mar 10 00:15:23 ridcully ^B
I get the same log entries when I try to login with cyradm.
BTW, it's not DeadRat, it's SuSE 7.1
OK, I fixed that. The "Cyrus HOWTO" is wrong, I started imapd via
inetd.conf. Now I had that corrected I have the trouble with sasldb.
Sendmail says it's not ok to chmod 0640 it. I know there is an option for
sendmail to tell it to shut up and do its work.
Sigh... ;-)
I had to compile sendmail with -D_FFR_UNSAFE_SASL, okay. But now I have to
enable the option DontBlameSendmail. But how? It's not clearly mentioned in
the sendmail... err, let's name that 'docs'. ;-)
Which of these is it?
1.
DAEMON_OPTIONS('DontBlameSendmail', `GroupReadableSASLFile')
2.
FEATURE('DontBlameSendmail', `GroupReadableSASLFile')
3.
define('DontBlameSendmail', `GroupReadableSASLFile') this one did not work
4.
LOCAL_CONFIG
DontBlameSendmail=GroupReadableSASLFile
Olaf
perl error with cyradm
Hi all, I get an error whenever I start cyradm: Can't locate Cyrus/IMAP/Shell.pm in @INC (@INC contains: /usr/lib/perl5/5.6.0/i586-linux /usr/lib/perl5/5.6.0 /usr/lib/perl5/site_perl/5.6.0/i586-linux /usr/lib/perl5/site_perl/5.6.0 /usr/lib/perl5/site_perl .). BEGIN failed--compilation aborted. But the file is there: /usr/local/lib/site_perl/5.6.0/i586-linux/Cyrus/IMAP/Shell.pm ./configure; make; make install had no errors. Has anyone had this error, and how can I fix that? Olaf
