Re: 2.1.4, linux-rh7.2: the "imapd: invalid option -- s" thing
"Matthew Hoskins" <[EMAIL PROTECTED]> writes: > Did you compile with SSL support? If not, you don't need > the -s option Yes, I asked for openssl (see below), and would like to have it. (I am also mildly curious why Fairly Obvious C code does something entirely different from what I would expect :-) Thanks for your help, Will ./configure --prefix=/our/.-ark-deploy/cyrus-imapd--2.1.4 --without-krb --with-com_err=yes --with-sasl=/our/.-ark-deploy/cyrus-sasl--2.1.2 --with-openssl=/usr/local/.-ark-deploy/openssl--0.9.6b --with-libwrap=/usr/local/.-ark-deploy/tcp-wrappers--7.6 --with-auth=unix --with-cyrus-prefix=/home/cyrus --with-statedir=/var/local/cyrus
RE: saslauthd: /var/state/saslauthd: No such file or directory
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Simon Matter > Sent: Tuesday, May 07, 2002 1:30 AM > To: jeff bert > Cc: [EMAIL PROTECTED] > Subject: Re: saslauthd: /var/state/saslauthd: No such file or directory > > > jeff bert schrieb: > > > > After installing cyrus-imapd-2.1.4 and cyrus-sasl-2.1.2 and > trying to start > > up saslauthd I get this error message: > > > > saslauthd: /var/state/saslauthd: No such file or directory > > Hi, > > You really don't give us much info about your system. > It seems your init script for saslauthd tried to write to /var/state > directory which does no longer exist on many systems like newer linux > systems. > > Simon > Nope it's not the init script it's the binary... if I call it using: # /usr/sbin/saslauthd -a pam& which gives that error. My configure/make sequence for cyrus-sasl-2.1.2: # ./configure \ --disable-anon \ --enable-plain \ --disable-krb4 \ --with-saslauthd \ --with-pam # make # make install # ln -s /usr/local/lib/sasl2 /usr/lib/sasl2 # /usr/sbin/saslauthd -a -pam& saslauthd: /var/state/saslauthd: No such file or directory # mkdir /var/state/saslauthd # /usr/sbin/saslauthd -a pam& # ll /var/state/saslauthd srwxrwxrwx 1 root root 0 May 7 00:06 mux= -rw--- 1 root root 0 May 7 00:06 mux.accept -rw--- 1 root root 0 May 7 00:06 mux.pid # I've realized that it's the --with-saslauthd option that puts this stuff in there and it's not a problem. Sorry to bother you all. Jeff
RE: 2.1.4, linux-rh7.2: the "imapd: invalid option -- s" thing
Did you compile with SSL support? If not, you don't need the -s option -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Will Partain Sent: Tuesday, May 07, 2002 12:17 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: 2.1.4, linux-rh7.2: the "imapd: invalid option -- s" thing I'm running 2.1.4 on a well-patched ia32-linux-rh7.2 box; the only oddity being that 'master' spits out "imapd: invalid option -- s" every time it tries to start up "imapd -s". You get the same message if you go to the build directory and type 'imap/imapd -s' thusly: partain$ ./imap/imapd -s ./imap/imapd: invalid option -- s (I don't know if this is not supposed to work :-). I assume the message is out of getopt, and I've checked that I really am linking in the one from glibc (2.0, I believe). I know this has come up in the past, and patches went in to deal with thread-friendliness, or some such. My own attempts to debug it w/ GDB didn't go too well, what with being an old guy who grew up in a pre-threads world :-) If I can be of assistance to someone who wants to dig into this and figure out what's going on, please yell back. Regards, Will
2.1.4, linux-rh7.2: the "imapd: invalid option -- s" thing
I'm running 2.1.4 on a well-patched ia32-linux-rh7.2 box; the only oddity being that 'master' spits out "imapd: invalid option -- s" every time it tries to start up "imapd -s". You get the same message if you go to the build directory and type 'imap/imapd -s' thusly: partain$ ./imap/imapd -s ./imap/imapd: invalid option -- s (I don't know if this is not supposed to work :-). I assume the message is out of getopt, and I've checked that I really am linking in the one from glibc (2.0, I believe). I know this has come up in the past, and patches went in to deal with thread-friendliness, or some such. My own attempts to debug it w/ GDB didn't go too well, what with being an old guy who grew up in a pre-threads world :-) If I can be of assistance to someone who wants to dig into this and figure out what's going on, please yell back. Regards, Will
Cyrus SASL 2.1.3-BETA Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'd like to announce the release of Cyrus SASL 2.1.3-BETA on ftp.andrew.cmu.edu. This version includes a significant cleanup of all of the included plugins, some major bug fixes, an LDAP saslauthd module, support for DIGEST-MD5 reauthentication, and more (see the ChangeLog for a complete list of changes). This is a beta release due to the significant amount of code rewrite that has occurred and because it has not been thoroughly tested against all applications that make use of it. Please send any feedback either to [EMAIL PROTECTED] (public list) or to [EMAIL PROTECTED] Download at: ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-sasl-2.1.3-BETA.tar.gz or http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-sasl-2.1.3-BETA.tar.gz I'd also like to thank the significant contributors to this release, including Howard Chu (for a good number of corrections to the GSSAPI plugin), and of course Ken Murchison (for the general plugin cleanup). - -Rob - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski | Andrew Systems Group - Research Systems Programmer Scotch & Soda Technical Coordinator | Cyert Hall 235 * 412-268-7456 - -BEGIN GEEK CODE BLOCK Version: 3.12 GCS/IT/CM/PA d- s+: a-- C$ UBLS$ P+++$ L++(+++) E W+ N- o? K- w O- M-- V-- PS+ PE++ Y+ PGP+ t+@ 5+++ R@ tv-- b++ DI+++ G e h r y? - --END GEEK CODE BLOCK- -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.76 iQA/AwUBPNgLQWes8cJc4y/MEQJSDwCfWtxiYBrVIAIPBfLFvHbKU/Dy/FsAn1Di Shu1HZtuG+opu9qBdPPSD/iY =gjsC -END PGP SIGNATURE-
Re: Fw: New weird compile error
On Tue, 7 May 2002, Dor S. wrote: [ you posted this to the sasl list, I'm cc-ing this to the info cyrus list instead. ] > Hey again, > Now I installed Berkeley DB 3.3.11 and I get a new compiling error: > > ### Making all in /root/cyrus-imapd-2.0.16/perl/imap > make[2]: Entering directory `/root/cyrus-imapd-2.0.16/perl/imap' > rm -f blib/arch/auto/Cyrus/IMAP/IMAP.so > LD_RUN_PATH="/root/cyrus-imapd-2.0.16/perl/imap/../../lib:/usr/lib" > c -shared IMAP.o -o > ib/arch/auto/Cyrus/IMAP/IMAP.so -L/root/cyrus-imapd-2.0.16/perl/imap/../.. > /lib -lcyrus -lsasl -lssl -lcrypto > /usr/i486-suse-linux/bin/ld: cannot find -lssl > collect2: ld returned 1 exit status > make[2]: *** [blib/arch/auto/Cyrus/IMAP/IMAP.so] Error 1 > make[2]: Leaving directory `/root/cyrus-imapd-2.0.16/perl/imap' > make[1]: *** [all] Error 1 > make[1]: Leaving directory `/root/cyrus-imapd-2.0.16/perl' > make: *** [all] Error 1 > > > Bleh? > > -Dor S. Go into cyrus-imapd-2.0.16/perl/imap and open up Makefile.PL in a text editor. Change this line: 'LIBS' => ["$SASL_LIB -lssl -lcrypto"], to this: 'LIBS' => ["$SASL_LIB -L/usr/local/ssl/lib -lssl -lcrypto"], and this line: 'INC' => "-I../../lib $SASL_INC", to this: 'INC' => "-I../../lib -I/usr/local/ssl/include/openssl $SASL_INC", Do the same thing to cyrus-imapd-2.0.16/perl/sieve/managesieve/Makefile.PL and then re-run make from the top level directory. I've had to do this with every build up to and including cyrus imap 2.1.4 even though I do pass --with-openssl=/usr/local/ssl to configure Jason -- Jason Englander [EMAIL PROTECTED]
RE: Migrate From 2.0 to 2.1.4
Ok Will try this week any way and will try write something P. > -Original Message- > From: Lawrence Greenfield [mailto:[EMAIL PROTECTED]] > Sent: mardi 7 mai 2002 11:53 > To: David Wright > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Migrate From 2.0 to 2.1.4 > > > If someone tries Ken's instructions and finds problems (or it > works) I'd really appreciate them being written up in HTML > for inclusion into the doc/ directory. > > thanks, > Larry > > >
Re: Migrate From 2.0 to 2.1.4
If someone tries Ken's instructions and finds problems (or it works) I'd really appreciate them being written up in HTML for inclusion into the doc/ directory. thanks, Larry
Zombie processes after startup with 2.1.4
After upgrading from 2.1.3 to 2.1.4 I see defunct processes after cyrus
startup. They're going away after the first pop3/imapd access and it
doesn't hurt.
The changelog says:
* master has preliminary code to avoid forking storms.
Is this because of the new feature?
ps shows:
8553 pts/0S 0:00 /usr/libexec/cyrus/cyrus-master
8558 pts/0Z 0:00 \_ [ctl_cyrusdb ]
8559 pts/0Z 0:00 \_ [ctl_deliver ]
8560 pts/0Z 0:00 \_ [tls_prune ]
8561 pts/0S 0:00 \_ imapd
8562 pts/0S 0:00 \_ imapd -s
8563 pts/0S 0:00 \_ pop3d
8564 pts/0S 0:00 \_ pop3d -s
8565 pts/0S 0:00 \_ lmtpd
cyrus.conf:
# standard standalone server implementation
START {
# do not delete this entry!
recover cmd="ctl_cyrusdb -r"
# this is only necessary if using idled for IMAP IDLE
# idledcmd="idled"
}
# UNIX sockets start with a slash and are put into /var/lib/imap/sockets
SERVICES {
# add or remove based on preferences
imap cmd="imapd" listen="imap" prefork=5
imaps cmd="imapd -s" listen="imaps" prefork=1
pop3 cmd="pop3d" listen="pop3" prefork=3
pop3s cmd="pop3d -s" listen="pop3s" prefork=1
sieve cmd="timsieved" listen="sieve" prefork=0
# at least one LMTP is required for delivery
# lmtp cmd="lmtpd" listen="lmtp" prefork=0
lmtpunix cmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=1
# this is only necessary if using notifications
# notify cmd="notifyd" listen="/var/lib/imap/socket/notify"
proto="udp" prefork=1
}
EVENTS {
# this is required
checkpointcmd="ctl_cyrusdb -c" period=30
# this is only necessary if using duplicate delivery suppression
delprune cmd="ctl_deliver -E 3" period=1440
# this is only necessary if caching TLS sessions
tlsprune cmd="tls_prune" period=1440
}
Re: Migrate From 2.0 to 2.1.4
David Wright wrote: > > > doc/install-upgrade.html > > This information assumes you are upgrading on one box. My situation (and > I suspect it is the situation of most production systems) is having 2.1 > set up clean (i.e. no mail or metadata) on a second machine, and now I > want to get all the mail from my 2.0 machine to it, without upgrading > the 2.0 machine. This insures that falling back to the old server is > trivial, in case the upgrade fails. > > The documentation doesn't discuss at all how to transfer mailstores > between machines. I think this is what Patrick and I both want to know. The document above should still be referenced because it will give you an idea of what other (if any) changes might have to be made. For migration here are some instruction off of my top of my head (I make no warranties, etc): The most important thing to remember is that the server(s) should not be running as you read/write the data. 0. Make sure you have run 'tools/mkimap' on the new server. This will create all of the directory trees. 1. Move '/var/spool/imap' from the old server to the new (tar, cpio, rsync, etc). This is all of your mailboxes and messages. 2. Move '/var/imap/user' from the old server to the new. This is all of the user subscriptions and message seen state (seen state _may_ not work correctly, but it should as long as both server use the 'flat' backend). 3. Move '/var/imap/quota' from the old server to the new. This is all of the user quota info. 4. Check the permissions on these directory trees to make sure all of the files/dirs are owned by 'cyrus' (and probably group 'mail'). 5. Run 'ctl_mboxlist -d /tmp/mailboxes.txt on the old server. This will dump your mailboxes database to a portable format. 6. Move '/tmp/mailboxes.txt' from the old server to the new (put it in /tmp, which is probably mounted on swap for speed). 7. Run 'ctl_mboxlist -u -f /tmp/mailboxes.db < /tmp/mailboxes.tmp'. This will load your new mailboxes database using your current format. 8. Move '/tmp/mailboxes.db' to '/var/imap/mailboxes.db' 9. [OPTIONAL] Move the contexts of your sieve directory from the old server to the new. 10. Start up the new server and see what happens. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Merging two Imapservers
Hello ! I've two Cyrus Imapserver both 1.6.22. I've upgraded the first to 2.0.16 (successfully). What will be the easiest way to transfer the second imapserver to the first in regards of the mailbox.db. I think that I will simply copy the /var/spool/imap/user/* files to the first server. Also the /var/imap/user/* files. When there are no same userids there shouldn't be a problem. But how shall I merge the mailbox.db file? Do you have any hints? are my assumptions right? Any pitfalls to watch for? thanks -jan
Re: New RPMs
Simon Matter wrote: > jeff bert schrieb: [...] >>No I use Linux Mandrake 8.1 [...] > Okay, Mandrake and RedHat differ. If you're running Mandrake you may > want to use Luca Olivetti's RPMs from > http://perso.wanadoo.es/olivetti/cyrus/ my packages are made for mandrake 8.2, I didn't test them with mandrake 8.1. They should work (not much has changed in terms of libraries) but I didn't test them. If you cannot install the binary packages, grab the source package and rebuild it. If that still doesn't work you'll have to tweak the spec file to take into account libraries' version installed with mandrake 8.1 Take a look at http://www.linux-mandrake.com/en/howtos/mdk-rpm/ for details on how to build rpms for mandrake. Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007
Re: saslauthd: /var/state/saslauthd: No such file or directory
jeff bert schrieb: > > After installing cyrus-imapd-2.1.4 and cyrus-sasl-2.1.2 and trying to start > up saslauthd I get this error message: > > saslauthd: /var/state/saslauthd: No such file or directory Hi, You really don't give us much info about your system. It seems your init script for saslauthd tried to write to /var/state directory which does no longer exist on many systems like newer linux systems. Simon > > so I created that directory manuall and don't get the error any longer but I > was curious does this show a sympton that something is wrong in my compile? > > Everything went fine configuring, making and installing. Just curious. > > Thanks, > > Jeff
Re: New RPMs
jeff bert schrieb: > > > Simon wrote: > > > > Did you install on RedHat 7.2? If yes, make sure you have current > > updates installed, if no, I don't know. > > > > No I use Linux Mandrake 8.1 > > > This is what I have installed: > > > > [root@dhcp-141-104 SRPMS]# rpm -qa | grep cyrus > > cyrus-imapd-devel-2.1.4-1 > > cyrus-sasl-md5-2.1.2-1 > > cyrus-imapd-2.1.4-1 > > cyrus-imapd-utils-2.1.4-1 > > cyrus-sasl-devel-2.1.2-1 > > cyrus-sasl-plain-2.1.2-1 > > cyrus-sasl-2.1.2-1 > > [root@dhcp-141-104 SRPMS]# rpm -qa | grep openssl > > openssl-devel-0.9.6b-8 > > openssl-0.9.6b-8 > > > > would you please run: > > # rpm -qa --filesbypkg | grep libssl.so.2 > # rpm -qa --filesbypkg | grep libcrypto.so.2 > > and tell me what is shows? Hi Okay, Mandrake and RedHat differ. If you're running Mandrake you may want to use Luca Olivetti's RPMs from http://perso.wanadoo.es/olivetti/cyrus/ BTW: libssl.so.2 libcrypto.so.2 are both in openssl-0.9.6b-8 Simon > > that would tell me what package(s) contain those files. > > Thanks, > > Jeff
