Re: Cyrus IMAP 2.1.4 released
On Wed, May 01, 2002 at 11:57:00AM -0300, Marc G. Fournier wrote: And again, you have an external program that is going through and pre-reading each and every users email, and adding/changing the message, which I believe will severely reduce the number of sites that implement it at the MTA level ... procmail isn't an option as a replacement for Sieve, since you then have to 'break the black box' by providing each email account with a shell account ... That's not true. You can configure procmail with cyrus keeping the black box environment. I am using it this way letting users change their filters over a cgi with limited capabilities. I am not allowing users to call external programs although it could be easily implemented. To implement this has to be done carefully of course. Werner
cant dm or sam mailbox
I have incorrectly setup one mailbox such that it is not in username but at the rootlevel. It also contains a period character. I can list it using lm I can't delete it or change it's acl values. It tells me: command failed: Mailbox does not exist I have tried to encapsulate it in quotes and various other strategies to name it but I always get this error. Is there anything I can do about it? Cheers, Daniel.
Re: cyrus, mysql, is anyone out there?
On Thu, 2002-05-02 at 03:48, Dustin Puryear wrote: Okay, one final try. Is anyone in the world that happens to be on this list using mysql with cyrus? I can't be the only one. If you do exist, and I'm happy to see that you do, I have cyrus compiled with mysql support. Unfortunately, when I try to auth against Cyrus via POP3 or whatever I get an error that Cyrus can't select the mysql database. I have used it but not this version. I have imapd.conf with: sasl_pwcheck_method: mysql sasl_mysqluser: mail sasl_mysqlpasswd: secret sasl_mysqlhost: localhost sasl_mysqldatabase: mail sasl_mysqltable: accountuser sasl_mysqluidcol: username sasl_mysqlpwcol: password test this works echo select password from accountuser where username = 'dom0001' | mysql -u mail -p -h localhost mail (or seomthing like that) Remeber with sasl V1 it will be via plain text.
Re: Virtual Mailboxes
On Thu, 2002-05-02 at 05:56, Igor Brezac wrote: On Thu, 2 May 2002, Devdas Bhagat wrote: I'd like to avoid this if I can, but I may have to go this route. What is the cyrus mailbox name for [EMAIL PROTECTED] vs [EMAIL PROTECTED]? user/user.dom.ain , user/user2.dom.ain The rewrite code is basically s/@/./, with calls in the appropriate places in the authentication mechanisms. Personally I use the alternative hierarchy separator a patch to lmtp to allow @ and of I go (this gets rid of realms in in lmtp though which Im not sure of the effect). It just means I dont have to rewrite names all the time. -- Simon
Re: cyrus, mysql, is anyone out there?
Hello, Dustin ! I just wanted to let you know, that you're not alone. I've been using cyrus+mysql for more than two years now. And I can tell you that it is still confusing if I setup a new box and try to install the various packages and patches that are needed in such a setup. However right now I'm using the following constellation on our primary mx: RedHat 6.2 MySQL-3.23.43-1 postfix-1.1.2-1 cyrus-imapd-sql-1.6.24-7 cyrus-sasl-1.5.21-8 On the backup mx, I use: RedHat 7.1 mysql-3.23.36-1 postfix-1.1.3-1 cyrus-imapd-2.0.16-4 cyrus-sasl-1.5.24-17 pam_mysql-0.4.7-1 Both machines work very nice. The first one uses a patched version of cyrus-imapd that authenticates against a MySQL database. Unfortunately the maintainer switched to qmail and this package is now unsupported. The constellation on the second server is indeed *very* cool since it uses PAM to authenticate. However it also has its drawbacks as the 2.x version of cyrus doesn't have a reconstruct -m command anymore, I cannot use my old rsync-scripts to hold both servers in sync As I said, I just wanted to let you know that there are more people using cyrus-mysql. And as I've seen, there were numerous threads on this subject in this mailinglist, as it seems to be a very confusing story . But I guess you've already searched the archives. Cheers, David On 05/02/2002 04:58 AM, Dustin Puryear wrote: Correction. The second fetchmail resulted in: May 1 18:58:17 freebsd pop3d[89249]: badlogin: localhost[::1] plaintext dom0001 cannot select MySQL database As well as the first one! So, this seems to be a cyrus/mysql issue. Regards, Dustin At 09:48 PM 5/1/2002 -0500, you wrote: Okay, one final try. Is anyone in the world that happens to be on this list using mysql with cyrus? I can't be the only one. If you do exist, and I'm happy to see that you do, I have cyrus compiled with mysql support. Unfortunately, when I try to auth against Cyrus via POP3 or whatever I get an error that Cyrus can't select the mysql database. I have imapd.conf with: sasl_pwcheck_method: mysql sasl_mysqluser: mail sasl_mysqlpasswd: secret sasl_mysqlhost: localhost sasl_mysqldatabase: mail sasl_mysqltable: accountuser sasl_mysqluidcol: username sasl_mysqlpwcol: password I've also verified that this information is correct: freebsd# mysql -u mail -psecret \ ? -e 'select username,password from accountuser' mail +--+--+ | username | password | +--+--+ | 0001 | password | | dom0001 | password | +--+--+ I didn't make any modifications to pam. Should this just work? If I try to check my mail using: freebsd# cat .fetchmailrc poll localhost protocol pop3 username dom0001 password password With fetchmail I get: May 1 18:50:11 freebsd pop3d[89212]: badlogin: localhost[::1] CRAM-MD5 no secret in database May 1 18:50:11 freebsd pop3d[89212]: badlogin: localhost[::1] plaintext dom0001 cannot select MySQL database The first line appears to be pop3d reporting that there is no md5 entry in the sasl database. Also, notice the 'select MySQL database' issue. (The fetchmail output is at the bottom of this mail, it's a bit long.) Now, if I force password authentication I get: freebsd# fetchmail --auth=password -vvv -c fetchmail: 5.9.6 querying localhost (protocol POP3) at Wed May 1 18:53:08 2002: poll started fetchmail: POP3 +OK [EMAIL PROTECTED] Cyrus POP3 v2.0.16 server ready fetchmail: POP3 USER dom0001 fetchmail: POP3 +OK Name is a valid mailbox fetchmail: POP3 PASS * fetchmail: POP3 -ERR Invalid login fetchmail: Invalid login fetchmail: Authorization failure on dom0001@localhost fetchmail: POP3 QUIT fetchmail: POP3 +OK fetchmail: 5.9.6 querying localhost (protocol POP3) at Wed May 1 18:53:11 2002: poll completed fetchmail: normal termination, status 3 But no errors via syslog. In the first attempt, fetchmail reports: freebsd# fetchmail -vvv -c fetchmail: 5.9.6 querying localhost (protocol POP3) at Wed May 1 18:50:08 2002: poll started fetchmail: POP3 +OK [EMAIL PROTECTED] Cyrus POP3 v2.0.16 server ready fetchmail: POP3 CAPA fetchmail: POP3 +OK List of capabilities follows fetchmail: POP3 SASL DIGEST-MD5 CRAM-MD5 fetchmail: POP3 EXPIRE NEVER fetchmail: POP3 LOGIN-DELAY 0 fetchmail: POP3 TOP fetchmail: POP3 UIDL fetchmail: POP3 PIPELINING fetchmail: POP3 RESP-CODES fetchmail: POP3 USER fetchmail: POP3 IMPLEMENTATION Cyrus POP3 server v2.0.16 fetchmail: POP3 . fetchmail: POP3 AUTH CRAM-MD5 fetchmail: POP3 + PDk3MjA5NDcuMTM2NjQxMDhAZnJlZWJzZC5kcGJveC5kaHMub3JnPg== fetchmail: POP3 ZG9tMDAwMSA4MDA3ZjM0MDhjNmFjOTgzOWFiMjliNDk5NzNlN2I0NA== fetchmail: POP3 -ERR authenticating: no secret in database fetchmail: authenticating: no secret in database fetchmail: POP3 USER dom0001 fetchmail: POP3 +OK Name is a valid mailbox fetchmail: POP3 PASS * fetchmail: POP3 -ERR Invalid login fetchmail: Invalid login
what's next
Hi all, I have installed cyrus-imapd-2.0.9-3.rpm with cyrus-sasl-1.5.24-23.rpm under redhat7.2. What should I do then to make imap works with sendmail? unplug
Re: Cyrus IMAP 2.1.4 released
On Thu, 2 May 2002, Werner Reisberger wrote: On Wed, May 01, 2002 at 11:57:00AM -0300, Marc G. Fournier wrote: And again, you have an external program that is going through and pre-reading each and every users email, and adding/changing the message, which I believe will severely reduce the number of sites that implement it at the MTA level ... procmail isn't an option as a replacement for Sieve, since you then have to 'break the black box' by providing each email account with a shell account ... That's not true. You can configure procmail with cyrus keeping the black box environment. I am using it this way letting users change their filters over a cgi with limited capabilities. I am not allowing users to call external programs although it could be easily implemented. To implement this has to be done carefully of course. Okay, you've peaked my interest ... I had tried before to use procmail, and found that I had to change permissions on deliver itself to make it work ... how are you tying procmail into cyrus, and what verison of cyrus?
Re: Master prefork problems; CLOSE_WAIT problems
--On Thursday, May 02, 2002 9:52 AM +1000 Jeremy Howard [EMAIL PROTECTED] wrote: I've seen a couple of problems over the last few weeks with master apparently failing to correctly maintain the prefork pool. We particularly see this problem with pop3d, which has more connects/disconnects than IMAP because of the nature of the protocol. The first issue is that in shut_down() sockets are not closed. It seems that this can leave sockets in CLOSE_WAIT state in certain error situations where popd_reset() is not called. The second issue is that we sometimes see sockets remain in a CLOSE_WAIT state because there is still data to be read. It appears that prot_fill() should be called in popd_reset() and shut_down(). The third issue is that when a process fails to shutdown correctly, such as if it segfaults, master does not seem to correctly keep track of the child process count. As a result, eventually the pool runs out and no more connections are accepted. Do the resolutions to the first two issues sound correct (we have made these changes and it seems to have fixed things for us)? Does anyone have a fix for the third issue? YES! I believe you have hit the nail on the head on all 3 of the issues above! Good job! We have been particularly bitten by the third issue with the master process losing track of the number of child processes in each service maintained. There has to be a better way for the master process to manage its children. I was thinking that it would be nice if the cyrus server used shared memory to keep track of the children, which ones were active or idle, which ones haven't checked in with the master in awhile (possible problem), etc. If the master had a incoming client queue, the children could pick up the next client and run with it. Furthermore, all the client information, such as number of clients each one has handled, etc would be available to the master, which is the only cyrus process that currently has SNMP support. This would make SNMP stats far more useful. Anyways, I wish I had the time right now to dive into the master/child communicatin problem, but I am glad somebody else has seen the problem too! Scott -- +-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-+ Scott W. Adkinshttp://www.cns.ohiou.edu/~sadkins/ UNIX Systems Engineer mailto:[EMAIL PROTECTED] ICQ 7626282 Work (740)593-9478 Fax (740)593-1944 +-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-+ PGP Public Key available at http://www.cns.ohiou.edu/~sadkins/pgp/ msg07532/pgp0.pgp Description: PGP signature
Installation Cyrus-IMAP 2.0.16 fails
Hello, With Linux-2.4.12/SuSE7.3PPC I have the following errors while compiling cyrus-IMAP 2.0.16 (compiling of Cyrus-sasl 1.5.27 went apparently well) ./configure --with-auth=unix == no problem make depend == no apparent problem Now things start to get worse: g3-99:/temp/cyrus-imapd-2.0.16 # make all CFLAGS=-O ### Making all in /temp/cyrus-imapd-2.0.16/man make[1]: Entering directory `/temp/cyrus-imapd-2.0.16/man' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/temp/cyrus-imapd-2.0.16/man' ### Making all in /temp/cyrus-imapd-2.0.16/et make[1]: Entering directory `/temp/cyrus-imapd-2.0.16/et' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/temp/cyrus-imapd-2.0.16/et' ### Making all in /temp/cyrus-imapd-2.0.16/sieve make[1]: Entering directory `/temp/cyrus-imapd-2.0.16/sieve' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/temp/cyrus-imapd-2.0.16/sieve' ### Making all in /temp/cyrus-imapd-2.0.16/acap make[1]: Entering directory `/temp/cyrus-imapd-2.0.16/acap' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/temp/cyrus-imapd-2.0.16/acap' ### Making all in /temp/cyrus-imapd-2.0.16/lib make[1]: Entering directory `/temp/cyrus-imapd-2.0.16/lib' gcc -c -I.. -I/usr/local/include -DHAVE_CONFIG_H -I. -I. -O \ cyrusdb_db3.c cyrusdb_db3.c:44: db.h: Aucun fichier ou r?pertoire de ce type make[1]: *** [cyrusdb_db3.o] Error 1 make[1]: Leaving directory `/temp/cyrus-imapd-2.0.16/lib' make: *** [all] Error 1 Thus cyrusdb_db3.o is unfindable. Where can I fish it? The same with make install: etc ... etc ... for file in ./acap.h; \ do \ /usr/bin/install -c -m 644 $file /usr/local/include/cyrus || exit 1; \ done make[1]: Leaving directory `/temp/cyrus-imapd-2.0.16/acap' ### Making install in /temp/cyrus-imapd-2.0.16/lib make[1]: Entering directory `/temp/cyrus-imapd-2.0.16/lib' ./../install-sh -d /usr/local/lib /usr/bin/install -c -m 644 libcyrus.a /usr/local/lib /usr/bin/install: cannot stat `libcyrus.a': Aucun fichier ou répertoire de ce type make[1]: *** [install] Error 1 make[1]: Leaving directory `/temp/cyrus-imapd-2.0.16/lib' make: *** [install] Error 1 Where is libcyrus.a ?? -- Alain Barthélemy SBB-ISP
Cyradm scripting? (Bulk account creation)
Hi, There seem to be a few people who have asked this already, but I can't find a definitive (easy!) response. I want to create 250 mailboxes (and associated sasldb passwords), and I'm not keen on doing it by hand. Some people are saying this is possibly by using TCO or Perl. My TCL and Perl scripting abilities are similar to those of a newly-born infant, so without something pre-written I'm going to be struggling! I'd like to either read the mailbox names from a file, or just make them up (eg. johnsmith001, johnsmith002). Any help much appreciated! Thanks, Russell
Re: Cyradm scripting? (Bulk account creation)
If you have expect on your machine, I have an expect script. Drawback is the cyradm password is hard coded in there. c* - Original Message - From: Russell Packer [EMAIL PROTECTED] To: Info Cyrus [EMAIL PROTECTED] Sent: Thursday, May 02, 2002 8:49 AM Subject: Cyradm scripting? (Bulk account creation) Hi, There seem to be a few people who have asked this already, but I can't find a definitive (easy!) response. I want to create 250 mailboxes (and associated sasldb passwords), and I'm not keen on doing it by hand. Some people are saying this is possibly by using TCO or Perl. My TCL and Perl scripting abilities are similar to those of a newly-born infant, so without something pre-written I'm going to be struggling! I'd like to either read the mailbox names from a file, or just make them up (eg. johnsmith001, johnsmith002). Any help much appreciated! Thanks, Russell
Cyrus - Squirrelmail - serverside threading
Hi, i'am using cyrus-imapd 2.0.16 Is there a serverside threading available? Webmailer squirrelmail v1.2.6 offers a function www.squirrelmail.org ChangeLog: [...] - Added a server-side thread sorting option per folder - Added a server-side sorting global option [...] Tnx Benn -- #250319 - http://counter.li.org
Re: Cyradm scripting? (Bulk account creation)
http://sourceforge.net/projects/cyrus-utils check out the Files section, and look at imapcreate and masssaslpass On Thu, 2002-05-02 at 06:49, Russell Packer wrote: Hi, There seem to be a few people who have asked this already, but I can't find a definitive (easy!) response. I want to create 250 mailboxes (and associated sasldb passwords), and I'm not keen on doing it by hand. Some people are saying this is possibly by using TCO or Perl. My TCL and Perl scripting abilities are similar to those of a newly-born infant, so without something pre-written I'm going to be struggling! I'd like to either read the mailbox names from a file, or just make them up (eg. johnsmith001, johnsmith002). Any help much appreciated! Thanks, Russell
Re: Cyrus IMAP 2.1.4 released
On Thu, May 02, 2002 at 09:07:45AM -0300, Marc G. Fournier wrote: That's not true. You can configure procmail with cyrus keeping the black box environment. I am using it this way letting users change their filters over a cgi with limited capabilities. I am not allowing users to call external programs although it could be easily implemented. To implement this has to be done carefully of course. Okay, you've peaked my interest ... I had tried before to use procmail, and found that I had to change permissions on deliver itself to make it work ... how are you tying procmail into cyrus, and what verison of cyrus? Currently with 2.013. To know how I us it you can download the package vfilter (it's small) and read the readme and install docs. Sorry, but it's a lot to write to explain it fully. You can get vfilter from http://sourceforge.net/projects/cyrus-utils/ or ftp://ftp.pure.ch/filter/ Werner
Re: Virtual Mailboxes
On Thu, 02 May 2002, simon wrote: Personally I use the alternative hierarchy separator a patch to lmtp to allow and of I go (this gets rid of realms in in lmtp though which Im not sure of the effect). It just means I dont have to rewrite names all the time. This is actually in Debian's packaged version. It is not enabled by default, and it is undocumented on purpose :) But if one reads changelogs, they will figure out how to enable it. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh
2.1.4 compilation failure on FreeBSD
cyrusdb_skiplist.c: In function `getsyncfd': cyrusdb_skiplist.c:190: `O_DSYNC' undeclared (first use in this function) FreeBSD doesn't support O_DSYNC - is there any risk in redefining it to O_FSYNC? Would it stand to reason that platforms that don't support fdatasync would also not support O_DSYNC?
Re: Cyrus - Squirrelmail - serverside threading
Quoting Bernd Schmelter [EMAIL PROTECTED]: Hi, i'am using cyrus-imapd 2.0.16 Is there a serverside threading available? Yes. THREAD=ORDEREDSUBJECT and THREAD=REFERENCES Telnet to your server and issue the CAPABILITY command to see a complete list of features. 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: Digest and Subject marker
On Wed, 1 May 2002, Mathias Koerber wrote: ... This will allow easy identification *and* filtering on the subject. When I asked the list-owner on this, it was suggested that I´d run this ... There are lot of headers that identify the source already, without adding junk to the Subject line too. I sort all the info-cyrus into a separate Cyrus folder with an Exim filter. Tom
cyradm: Permission Denied
I installed postfix with cyrus packages. I've gone through the HowTo and now I'm having problems adding the users mailboxes. This is what I've completed: - Installed postfix, cyrus-sasl-gssapi, cyrus-sasl-md5, cyrus-sasl-devel, cyrus-sasl-java, cyrus-sasl, cyrus-sasl-plain. - I've created all of the local accounts for the email clients. - Created the email passwords with sasl. When I execute, 'cyradm -u cyrus-adm localhost'. I enter my password and I get a prompt. I enter 'cm test' and I get the error, createmailbox: Permission denied. I'm not exactly sure where the denial is coming from. I double checked the permissions in /var/imap, and /var/spool/mail. I can't seem to figure out why I'm getting this error. Help! Please! Thanks, Robert Lasirona
