Re: Cyrus and very large folders
Jurgen Botz wrote: > I just installed Cyrus for the first time to evaluate it as a possible > mailserver to use at my company. I was surprised to find that each > folder/mailbox is a single directory... my experience is that on > typical Unix filesystems (UFS, ext2) this would cause severe performance > degradation once a mailbox has a few thousand messages. > I believe that Cyrus 2.1 includes Gary Mill's improved directory hashing scheme. Check the CVS tree--I haven't tried it so I don't really know what I'm talking about...
separate imap / pop3 logins (without pam) ?
Hi! Next question: Is it possible to separate the imapd from the pop3 logins (without pam)? I want to let all users use pop3. But i want to specify what users are allowed to use imap... If i use pam: separation is quite simple via pop3/imap-files in /etc/pam.d, but i can only use plain text passwords. (SSL will be available too, so plain text passwords aren't too bad) But when i use sasldb to offer md5 or something, i can't use pam... Is it possible to separate the pop3 logins from the imap logins and use sasldb ? Or do you suggest any other authentication mechanism ? Greets Mark Davis
Re: pam/mysql doesnt work
Hi! My problem is solved... You remember ? pam was not working.. Reason: I had two versions of sasl installed. One in /usr/lib/sasl, the other one in /usr/local/lib/sasl... imapd used the second one, but this one was compiled without pam support... For all to mention: if you get the message: unrecognized plaintext verifier PAM always look with ldd first, if you linked the "right" libraries e.g.: > > host$ ldd /usr/local/lib/libsasl.so.7.1.8 > > libdb.so.3 => /usr/lib/libdb.so.3 (0x4001) > > libdl.so.2 => /usr/lib/libdl.so.2 (0x4004b000) > > libcrypt.so.1 => /usr/lib/libcrypt.so.1 (0x4004f000) > > libpam.so.0 => /usr/lib/libpam.so.0 (0x4007c000) > > libresolv.so.2 => /usr/lib/libresolv.so.2 (0x40085000) > > libc.so.6 => /usr/lib/libc.so.6 (0x40094000) > > /lib/ld-linux.so.2 => /usr/lib/ld-linux.so.2 (0x8000) Greets Mark Davis - Original Message - From: "Mark Davis" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 12, 2001 1:40 PM Subject: Re: pam/mysql doesnt work > Hi! again > > Thx for your answer. But i also tried to compile sasl with the follwoing > options: > $ ./configure --prefix=/usr --with-passwd_method=PAM --with_pam=/lib/security > or > $ ./configure --prefix=/usr --with_pam=/lib/security > > and as you can see in the log of my configure: > > >checking for pam_start in -lpam... yes > > >checking for security/pam_appl.h... yes > > >checking PAM support... yes > > I also tried sasl_pwcheck_method: pam, pan??? and pam. Always "cannot find > ..." > > And i also removed the "pwcheck_method" from imapd.conf > > And finally there are NO spaces at the end (i verified with vi). > > Nothing worked. I'am getting frustrated. > > Isn't there a how-to that i maybe didnt worked through, that you can tell me ? > > I am using ( i forgot to mention last time): > Distro: SuSE 7.2 (Maybe next monday i try 7.3) > > openssl-0.9.6a (and dev) > cyrus-imapd-2.0.16 > cyrus-sasl-1.5.24 > pam-0.74-39 (and dev) > mysql-2.23.37 (client and dev) > > Greets > Mark Davis > > > Am Donnerstag, 11. Oktober 2001 14:36 schrieben Sie: > > Mark, > > > > Try substituting --with-pam for --with-passwd_method=PAM when > > configuring sasl. > > > > > > Also try removing: > > > > pwcheck_method: PAM > > > > from your /etc/imapd.conf . You should only require: > > > > sasl_pwcheck_method: pam > > > > Mark Davis wrote: > > >Hi all... > > > > > >I want to authenticate the users via a mysql-db. So i compiled pam_mysql > > > and made the files pop3/imap in the /etc/pam.d/ directory. > > > > > >I read all the mailings about pam / mysql... But i still have problems to > > > get the thing to work... > > > > > >I always get the following message in /var/log/messages or > > > /var/log/auth.log: > > > > > >Oct 10 15:33:24 mail imapd[10949]: unrecognized plaintext verifier PAM > > > > > >It seems, that sasl doesnt know what PAM is ?! > > > > > >I compiled sasl with: > > >$ ./configure \ > > >--prefix=/usr \ > > >--with-passwd_method=PAM > > > > > >and the result auf the configure-script looks as PAM should work (see > > > below). > > > > > >sasldb works fine... Any ideas ? All my configuration files are listed > > > below. > > > > > >Greets > > >Mark Davis > > > > > >$ ldd /usr/local/imapd/bin/imapd > > >libsasl.so.7 => /usr/local/lib/libsasl.so.7 (0x40017000) > > >libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x40026000) > > >libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x40054000) > > >libdb-3.3.so => /usr/lib/libdb-3.3.so (0x40115000) > > >libresolv.so.2 => /lib/libresolv.so.2 (0x40196000) > > >libnsl.so.1 => /lib/libnsl.so.1 (0x401a8000) > > >libc.so.6 => /lib/libc.so.6 (0x401be000) > > >libdl.so.2 => /lib/libdl.so.2 (0x402db000) > > >libcrypt.so.1 => /lib/libcrypt.so.1 (0x402df000) > > >/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) > > > > > > > > >$ more /usr/local/sasl/cyrus.conf > > >pwcheck_method: PAM > > > > > > > > >$ more /etc/imapd.conf: > > >configdirectory: /var/imap > > >partition-default: /var/spool/imap > > >admins: root cyrus > > >sasl_pwcheck_method: PAM > > >srvtab: /var/imap/srvtab > > >allowanonymouslogin: no > > >pwcheck_method: PAM > > >allowplaintext: yes > > > > > > > > >$ ./configure --prefix=/usr --with-passwd_method=PAM > > >... > > >checking for syslog... yes > > >checking for crypt... no > > >checking for crypt in -lcrypt... yes > > >checking for connect... yes > > >checking for pam_start in -lpam... yes > > >checking for security/pam_appl.h... yes > > >checking PAM support... yes > > >checking CRAM-MD5... enabled > > >checking SCRAM-MD5... disabled > > >checking for des_pcbc_encrypt in -ldes... no > > >checking for RSAPublicEncrypt in -lrsaref... no > > >checking for des_pcbc_encrypt in -lcrypto... yes > > >checking for openssl/des.h... yes > > >checking DIGEST-MD5... enabled > > >checking for res_search
RE: New server
--On Wednesday, October 03, 2001 2:25 PM -0400 Kiarna Boyd <[EMAIL PROTECTED]> wrote: > Wow. > Yes you are right if that is a base performance. > I have 2.0.16 currently for cyrus. Sendmail 8.22. > > Is there specific tuning I need to do? > Are there FAQ's available? > > My mail queue is high and I have about 20 imap seesions at peak. > > Nfs auto mounts to user home dirs. Mailboxes are local to the server > though. > > I show 7 sendmail processes each at around 6 %. You might want to inquire on comp.mail.sendmail to debug why Sendmail is taking so much CPU time. This may be unrelated to Cyrus. Larry
where is the documentation about IMAP folders o Shared folders?
Hi, I don't find documentation about IMAP folders o Shared folders neither in the software documentation nor FAQ (http://asg.web.cmu.edu/cyrus/imapd/install-FAQ.html) nor Linux-Cyrus-Howto (http://www.linuxdoc.org/HOWTO/Cyrus-IMAP.html) Thanks you for any information. Fabian
Re: Cyrus and very large folders
> On Sun, 21 Oct 2001 23:24:30 -0700, > Jurgen Botz <[EMAIL PROTECTED]> (jb) writes: jb> At one point in the past I used Netscape Messaging Server (now iPlanet) jb> and it had this problem at versions less than 4.x. With a few hundred jb> users, many of whom had mailboxes with a few thousand messages in them, jb> opening a mailbox was painfully slow. The problem is that normal Unix Well, my inbox currently has 3568 messages in it and PINE pops it open in a jiffy. You need to keep in mind that Cyrus caches things like the headers. See the four "cyrus.*" files in each folder. In fact, I typically use the auto-expire capabilities in Gnus (news/mail reader for Emacs/XEmacs) and rarely ever manually delete a message. I could not do this if Cyrus didn't handle large folders well. jb> Has anyone who uses Cyrus in a large organization environment found jb> this to be a problem? How do you define "large"? ;-) I think if you spread your message store across spindles, you should be okay. -- Amos
Re: Sieve error in :matches clause
Jeremy Howard wrote: > > William K. Hardeman wrote: > > You've probably noticed this yourself, but I'm suspecting cyrus is > treating > > the [ and ] as standard regex grouping characters, which would explain the > > number rejects. I don't really know anything about the Cyrus codebase, not > > being a programmer, but I do know that sieve can support regexes, from > some > > things I've seen on the list and from my perusal of websieve. However, it > > was my understanding that regex support in a sieve script had to be > > explicitly enabled before it works. > > > I suspect you're right, William. AFAICT this goes against the RFC however, > since you should only get regex when you use the :regex comparator. > > Ken--is this a bug... a feature... a misdiagnosis...? It appears to be a bug caused by using fnmatch(3) to perform the match. fnmatch(3) performs glob-style matching, which treats '?', '*' AND '[' as special -- see glob(7). The workaround is to escape the []: header :matches "subject" "*\\[spam score 10.0/10.0 -pobox\\]*" Feel free to bugzilla this, but I doubt it'll be at the top of anyone's list, since using fnmatch(3) is just too convenient. Ken -- 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
Re: Cyrus and very large folders
Amos Gouaux wrote: > Well, my inbox currently has 3568 messages in it and PINE pops it > open in a jiffy. You need to keep in mind that Cyrus caches things > like the headers. See the four "cyrus.*" files in each folder. Right, but this may still be a problem because those files are in the same directory as all the messages. Maybe you don't have a problem yet because you have "only" 3568 messages and there aren't many users with large folders, so once Cyrus has looked in that dir once all the entries are in the dcache. But when you have dozens of users with folder of 10K+ messages a machine with 1GB of RAM may not have enough dcache to hold it all and so every time Cyrus tries to access the header cache (cyrus.* file) in your folder it will have to go back to disk, read the whole huge directory, search it for the cache.* files, etc. I'm not saying that there is necessarily anything wrong with Cyrus... in fact, I think that for modern requirements the old designs of the filesystems are the problem, not the application. Applications shouldn't /have/ to work around this kind of thing. But if we're using UFS or ext2 (and I think even ext3) this is the reality we're still living with, and I'd like to know if anyone is running into this and seeing noticeable/problematic folder open times because of it. :j -- Jürgen Botz | While differing widely in the various [EMAIL PROTECTED] | little bits we know, in our infinite | ignorance we are all equal. -Karl Popper
ANN: Cyrus IMAPd rpm packages version 2.0.16-2rm
People: I have uploaded a new release of the rpm package set of Cyrus IMAPd server I'm maintaining. Version is 2.0.16, release is 2rm. The URL is http://rmrpms.tripod.com/cyrus-imapd/ These packages are prepared, built and tested on a Red Hat Linux 6.2 system, but I'm doing my best to make rebuilding the source rpm under Red Hat Linux 7 and 7.1 trouble-free. Support for interfacing with the Sendmail MTA and drac (Dynamic Relay Authorization Control Daemon) is selectable at build time (instructions are on the above URL and on the README.RPM file contained in the cyrus-imapd-doc sub-package). Source (recommended) and binary (Red Hat Linux 6.2/i386) packages are available. The README.RPM has been updated with help on common problems encoun- tered deploying Cyrus on Red Hat Linux servers. Reading it entirely is recommended. The packages are GPG signed. You can download my public key from http://rmrpms.tripod.com/RM-GPG-KEY or from http://www.rmorales.com.ar/RM-GPG-KEY Please report any problem, send patches, comments rants, ... to <[EMAIL PROTECTED]> Changes since last release (2.0.16-1rm): - From CVS: patch for /etc/imapd.conf file trailing spaces bug - From CVS: master daemon now calls initgroups() and setgid(); - Always ship sendmail.cyrus.mc in the source rpm this should help solve problems with /etc/sasldb and /etc/shadow perms - Change perms of /etc/sasldb to 640 root mail - s/Copyright/License/ - Fix links to cyradm and imapd.conf manpages in html documentation - Cyrus service stops are silent now (preun, triggerin) - Add a Packager tag - Update README.RPM - specfile cleanup & tweaks Standard info about the packages follows: Name: cyrus-imapd Version : 2.0.16 Release : 2rm Summary : A high-performance mail store with IMAP and POP3 support. License : BSD Group : System Environment/Daemons Build Date : Sat 20 Oct 2001 01:38:01 PM GMT+3 Build Host : mowgli.rmorales.com.ar Source RPM : cyrus-imapd-2.0.16-2rm.src.rpm Size: 3966180 Packager: Ramiro Morales <[EMAIL PROTECTED]> Description : The Cyrus IMAP server is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP system. All user access to mail is through software using the IMAP, POP3, or KPOP protocols. This is the main package, install also the cyrus-imapd-doc package (it contains the documentation in html and plain text formats) and the cyrus-imapd-utils package (it contains server administration tools and depends on the perl-Cyrus package). -- Name: cyrus-imapd-devel Version : 2.0.16 Release : 2rm Summary : Cyrus IMAPd development files. License : BSD Group : Development/Libraries Build Date : Sat 20 Oct 2001 01:38:01 PM GMT+3 Build Host : mowgli.rmorales.com.ar Source RPM : cyrus-imapd-2.0.16-2rm.src.rpm Size: 712956 Packager: Ramiro Morales <[EMAIL PROTECTED]> Description : This package contains header files and libraries necessary for developing applications which use the imclient library. The main package is cyrus-imapd. -- Name: cyrus-imapd-doc Version : 2.0.16 Release : 2rm Summary : Documentation files for Cyrus IMAPd administrators. License : BSD Group : Documentation Build Date : Sat 20 Oct 2001 01:38:01 PM GMT+3 Build Host : mowgli.rmorales.com.ar Source RPM : cyrus-imapd-2.0.16-2rm.src.rpm Size: 518955 Packager: Ramiro Morales <[EMAIL PROTECTED]> Description : This package contains the documentation files for the Cyrus IMAPd server in html and text formats. The main package is cyrus-imapd. -- Name: cyrus-imapd-utils Version : 2.0.16 Release : 2rm Summary : Cyrus IMAPd server admin utilities. License : BSD Group : Applications/System Build Date : Sat 20 Oct 2001 01:38:01 PM GMT+3 Build Host : mowgli.rmorales.com.ar Source RPM : cyrus-imapd-2.0.16-2rm.src.rpm Size: 59288 Packager: Ramiro Morales <[EMAIL PROTECTED]> Description : This package contains Cyrus IMAPd server administrative tools. It can be installed on systems other than the one running the server. This package depends on the perl-Cyrus package. The main package is cyrus-imapd. -- Name: perl-Cyrus Version : 2.0.16 Release : 2rm Summary : Cyrus IMAPd utility Perl modules. License : BSD Group : Applications/CPAN Build Date : Sat 20 Oct 2001 01:38:01 PM GMT+3 Build Host : mowgli.rmorales.com.ar Source RPM : cyrus-imapd-2.0.16-2rm.src.rpm Size: 43
Re: Cyrus and very large folders
I was running cyrus as my company mailserver for a while, I saw things start to slowdown when there were more then ~7K messages in one folder (and start to be significant when it got to more then ~20K messages/folder). This was on linux 2.0.x on a pentium 200 with 64MB ram serving ~200 users. it's a problem, but it's far less of a problem then attempting to parse a unix mail file to get the message you need, that starts to slow down significantly at <1000 messages (on a much faster linux box) David Lang On Mon, 22 Oct 2001, Amos Gouaux wrote: > Date: Mon, 22 Oct 2001 09:03:16 -0500 > From: Amos Gouaux <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: Cyrus and very large folders > > > On Sun, 21 Oct 2001 23:24:30 -0700, > > Jurgen Botz <[EMAIL PROTECTED]> (jb) writes: > > jb> At one point in the past I used Netscape Messaging Server (now iPlanet) > jb> and it had this problem at versions less than 4.x. With a few hundred > jb> users, many of whom had mailboxes with a few thousand messages in them, > jb> opening a mailbox was painfully slow. The problem is that normal Unix > > Well, my inbox currently has 3568 messages in it and PINE pops it > open in a jiffy. You need to keep in mind that Cyrus caches things > like the headers. See the four "cyrus.*" files in each folder. > > In fact, I typically use the auto-expire capabilities in Gnus > (news/mail reader for Emacs/XEmacs) and rarely ever manually delete > a message. I could not do this if Cyrus didn't handle large folders > well. > > jb> Has anyone who uses Cyrus in a large organization environment found > jb> this to be a problem? > > How do you define "large"? ;-) I think if you spread your message > store across spindles, you should be okay. > > > -- > Amos >
Re: Cyrus and very large folders
> Amos Gouaux wrote: >> Well, my inbox currently has 3568 messages in it and PINE pops it open >> in a jiffy. You need to keep in mind that Cyrus caches things like >> the headers. See the four "cyrus.*" files in each folder. > > Right, but this may still be a problem because those files are in > the same directory as all the messages. Maybe you don't have a > problem yet because you have "only" 3568 messages and there aren't many > users with large folders, so once Cyrus has looked in that > dir once all the entries are in the dcache. But when you have > dozens of users with folder of 10K+ messages a machine with 1GB > of RAM may not have enough dcache to hold it all and so every > time Cyrus tries to access the header cache (cyrus.* file) in > your folder it will have to go back to disk, read the whole huge > directory, search it for the cache.* files, etc. We're running cyrus 2.0.9 with 19000 users (in the same directory, because I was in a hurry..doh!) ...recently I discovered that one of my "nobody" boxes had 54,000 messages in it. Pine showed absolutely no delays in opening the mail...a webmail client I have got hosed but I believe it tries to actually figure out your message situation for itself (looping thru the number of messages instead of consulting a header file)..don't know for sure...anyway, had I increased the php timeout it would've eventually been fine. Of course expunge took a LONG time, but the server did great under the stress. Is the performance optimal? Probably not. It does work, however. My FS is ext2 on RH7.1, tho I'm seriously investigating a journaling FS for this machine. This is a pIII 800mhz with 896Mb RAM. My .02. jenn
Re: Master Segmentation Fault
Lee Hoffman wrote: > Thanks a bunch for the advice. I deleted db from /etc/nsswitch.conf and > viola, master stopped segfaulting on launch. ... > Oct 21 13:09:27 grass master[1520]: about to exec > /usr/local/cyrus/bin/imapd > Oct 21 13:09:27 grass master[1508]: process 1520 exited, signaled to > death by 11 Well, it's obvious that now that the master runs, all its children are still dying, probably for the same reason. Did you try setting LD_LIBRARY_PATH to point to where you have the DB-3 libraries (those that you linked with) prior to running master? Does "ldd imapd" show that those libraries are actually getting selected instead of libdb or libdb2? Do you have other "db" references in nsswitch.conf? Can't think of anything else... --mika
Re: separate imap / pop3 logins (without pam) ?
You can use separate configuration files for imap and pop3. Copy your current /etc/imapd.conf to /etc/pop3d.conf and make the changes for appropriate pop3 login. Then, in cyrus.conf modify the pop3d line to include '-C /etc/pop3d.conf'. For instance, you could specify separate sasldb files, although, then you have the headache of keeping them in sync. Cheers Chris Mark Davis wrote: >Hi! > >Next question: Is it possible to separate the imapd from the pop3 logins >(without pam)? > >I want to let all users use pop3. But i want to specify what users are >allowed to use imap... > >If i use pam: separation is quite simple via pop3/imap-files in /etc/pam.d, >but i can only use plain text passwords. >(SSL will be available too, so plain text passwords aren't too bad) > >But when i use sasldb to offer md5 or something, i can't use pam... Is it >possible to separate the pop3 logins from the imap logins and use sasldb ? >Or do you suggest any other authentication mechanism ? > >Greets >Mark Davis >
Re: Sieve error in :matches clause
> It appears to be a bug caused by using fnmatch(3) to perform the match. > fnmatch(3) performs glob-style matching, which treats '?', '*' AND '[' > as special -- see glob(7). The workaround is to escape the []: > > header :matches "subject" "*\\[spam score 10.0/10.0 -pobox\\]*" > > Feel free to bugzilla this, but I doubt it'll be at the top of anyone's > list, since using fnmatch(3) is just too convenient. > No, I'm not going to Bugzilla this--instead I'll read up on fnmatch(3) and add its capabilities to our documentation. Then it becomes a feature, not a bug :-)
Re: separate imap / pop3 logins (without pam) ?
There are two things you could set in your configuration files. I found these by looking through the sasl and cyrus source code, the only complete and always up-to-date documentation. It will take you an hour or two of poking around to get up to speed, but it more than pays for itself. 1) To use separate sasldb files, the parameter is 'sasl_sasldb_path' You can see this in action by checking out lib/db_berkeley.c ( or db_gdbm.c, etc etc ) in the SASL source. You will find a line where the option 'sasldb_path' is consulted. The Cyrus servers prepend 'sasl_' before getting these options from Cyrus configuration files ( see imap/config.c in Cyrus sources ). 2) To change the realm used by Cyrus in sasldb lookups, set 'servername' in configuration file. You can find the relavent code in imap/config.c in the Cyrus sources. Keep in mind, this parameter sets the servername displayed to users in greeting banners and might have other uses ( I didn't see any, but I didn't look hard). Values such as imap.mydomain.com and pop3.mydomain.com should be mostly harmless. BTW, Cyrus doesn't prepend 'sasl_' to this setting (its not really considered an SASL setting) Cheers Chris Mark Davis wrote: >Hi! > > >>You can use separate configuration files for imap and pop3. Copy your >>current /etc/imapd.conf to /etc/pop3d.conf and make the changes for >>appropriate pop3 login. Then, in cyrus.conf modify the pop3d line to >>include '-C /etc/pop3d.conf'. For instance, you could specify separate >>sasldb files, although, then you have the headache of keeping them in >> >sync. > >Good idea... I overlooked the possibility to insert a complete cmdline for >starting the demons.. That's really cool. > >But how do i change the location of the sasldb (No hint in the >doc-directory)? > >Isn't it even possible to use different realms for pop3/imap ? Then i only >have one file and "sasldblistusers |grep $USER" would show me the mechanism >and even if the user can use pop3 and/or imap. > >e.g. >user: mark realm: IMAP mech: PLAIN >user: mark realm: IMAP mech: DIGEST-MD5 >user: mark realm: POP3 mech: PLAIN >user: mark realm: POP3 mech: DIGEST-MD5 > >What would be the disadvantage ? Or is it even not advisable ? What is the >"realm" normally used for ? > >Oh, oh, oh... So many questions... I only hope other people on the >mailinglist will learn something too from it... > >Greets >Mark Davis >
creating non-production mail test system
I'm hoping that someone here may be able to give me some advice. I'm attempting to configure a machine inside our company to work as a testbed mail system. The goal is to use it to test upgrades to our mail software before moving it onto the company's production server. (This came about because I seriously botched my first attempt to upgrade sendmail to version 8.11.6 on the production server. This resulted in mail delivery problems for several hours, which upset a few people. :-) A quick overview of the system: A 700 MHz PIII with 512 MB of RAM. RedHat 6.2 installed with _almost_ all service patches. (Not all of them are relevant for our use.) Installed mail software: TrendMicro VirusWall 3.6 cyrus-sasl-1.5.24 cyrus-imapd-1.6.19 sendmail-8.9.3 Now I want to move to sendmail 8.11.6 and cyrus-imapd-2.0.16 without breaking anything. I also want to change my sendmail configuration to use SMTP-AUTH, and to install some spam filtering software. This all still has to work with the current VirusWall software. To test the transition, we added a DNS entry for a fake domain name which we named foo.bar (not the real name, but I'm paranoid about releasing that sort of information) and added a MX record for the test machine. Mail sent to [EMAIL PROTECTED] gets directed to the test machine just fine. Next I installed the virus software. Okay, everything still works. Now I attempt to install cyrus-sasl and cyrus-imapd. I used the very same packages from our working system, and configured everything to be identical to our production machine. /usr/lib/sasl/Cyrus.conf contains: pwcheck_method:passwd /etc/imapd.conf contains: configdirectory: /var/imap partition-default: /var/spool/imap admins: cyrusadmin allowanonymouslogin: no sasl_pwcheck_method: sasldb /etc/pam.d/imap contains: (although it isn't used) #%PAM-1.0 auth required /lib/security/pam_pwdb.so shadow nullok accountrequired /lib/security/pam_pwdb.so I used saslpasswd to create a shared secret for cyrusadmin and one for myself. These show up in the output from sasldblistusers /usr/sbin/sasldblistusers user: bacon realm: xx.aerodyne.com mech: PLAIN user: cyrusadmin realm: xx.aerodyne.com mech: PLAIN user: cyrusadmin realm: xx.aerodyne.com mech: DIGEST-MD5 user: bacon realm: xx.aerodyne.com mech: CRAM-MD5 user: bacon realm: xx.aerodyne.com mech: DIGEST-MD5 user: cyrusadmin realm: xx.aerodyne.com mech: CRAM-MD5 Now I want to create an imap mailbox for bacon on my machine using cyradm. cyradm -u cyrusadmin shamus.aerodyne.com Please enter your password: application-specific initialization failed: authentication failed If I try the tests suggested in the installation directions, I get imtest -m login -u cyrusadmin -p imap xx.aerodyne.com S: * OK xx.aerodyne.com Cyrus IMAP4 v1.6.19 server ready C: C01 CAPABILITY S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS X-NON-HIERARCHICAL-RENAME NO_ATOMIC_RENAME AUTH=PLAIN AUTH=LOGIN UNSELECT X-NETSCAPE S: C01 OK Completed Password: + go ahead L01 NO Login failed. Error=-1 Authenticated. Security strength factor: 0 The imapd.log file just shows Oct 22 18:13:34 xx imapd[7708]: badlogin: xx.aerodyne.com[198.4.242.xxx] PLAIN generic failure I currently have cyrus-imapd-1.6.19 installed on both the production server and my small testbed machine. I've rebuilt all of the software on this machine in the hopes that library inconsistencies will be minimal. Is there anything obvious which I've forgotten? Is it possible that I cyrus-imapd and cyrus-sasl are using incompatible databases? I have db-3.1.17 installed on the machine. Here are the libraries used by the software installed on the testbed machine. ldd /usr/cyrus/bin/imapd libsasl.so.7 => /usr/lib/libsasl.so.7 (0x4001d000) libdl.so.2 => /lib/libdl.so.2 (0x40028000) libdb.so.3 => /lib/libdb.so.3 (0x4002c000) libc.so.6 => /lib/libc.so.6 (0x40066000) libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0x4015c000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x40162000) libpam.so.0 => /lib/libpam.so.0 (0x4019) libresolv.so.2 => /lib/libresolv.so.2 (0x40198000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) ldd /usr/sbin/saslpasswd libsasl.so.7 => /usr/lib/libsasl.so.7 (0x4001d000) libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0x40028000) libdl.so.2 => /lib/libdl.so.2 (0x4002e000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x40032000) libpam.so.0 => /lib/libpam.so.0 (0x40061000) libresolv.so.2 => /lib/libresolv.so.2 (0x40069000) libdb.so.3 => /lib/libdb.so.3 (0x40078000) libc.so.6 => /lib/libc.so.6 (0x400b2000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) I apologize for the length of this message, but the more detail I provide, the more likely someone will see my error. Does any of this suggest a p
procmailrc
I have a global procmailrc I created which I execute with fetchmali. It works somewhat but all mail seems to go to the Debian folder? What do I seem wrong in this? PATH=path/mail SHELL=/bin/sh HOME=path/mail DELIVER="/usr/sbin/cyrdeliver" SPAM=/dev/null LOGNAME=$LOGNAME :0:lance.lock * ^To:|^cc:|Cc:.*debian-user | tail +2 | $DELIVER -e -a lance -m Listserv.Debian :0:lance.lock * ^To:.*strawbale | tail +2 | $DELIVER -e -a lance -m Listserv.Strawbale :0:lance.lock * ^To:.*mutt | tail +2 | $DELIVER -e -a lance -m Listserv.muttuser :0:lance.lock | tail +2 | $DELIVER -e -a lance -m user.lance
RE: Master Segmentation Fault - SOLVED!
I finally got it!!! The first piece was obviously to delete the line db from services in /etc/nsswitch.conf. The second piece of the puzzle was that I had to recompile sasl executing the following commands before configuring: export CPPFLAGS=-I/usr/local/BerkeleyDB.3.3/include export LDFLAGS=-L/usr/local/BerkeleyDB.3.3/lib Boom! Everything now works. Thanks again for all your help. Lee -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mika Iisakkila Sent: Monday, October 22, 2001 3:14 PM To: [EMAIL PROTECTED] Subject: Re: Master Segmentation Fault Lee Hoffman wrote: > Thanks a bunch for the advice. I deleted db from /etc/nsswitch.conf and > viola, master stopped segfaulting on launch. ... > Oct 21 13:09:27 grass master[1520]: about to exec > /usr/local/cyrus/bin/imapd > Oct 21 13:09:27 grass master[1508]: process 1520 exited, signaled to > death by 11 Well, it's obvious that now that the master runs, all its children are still dying, probably for the same reason. Did you try setting LD_LIBRARY_PATH to point to where you have the DB-3 libraries (those that you linked with) prior to running master? Does "ldd imapd" show that those libraries are actually getting selected instead of libdb or libdb2? Do you have other "db" references in nsswitch.conf? Can't think of anything else... --mika
