shared folders - question
Hello.. I'm trying to use shared folders in cyrus to view user mail by admin. And for doing this i enter as cyrusadmin (user1 wants to read user2 mail) setacl user/[EMAIL PROTECTED] [EMAIL PROTECTED] lr whene user2 creates some folder user1 can read it. But problem is when i want to remove access for user2 mailbox. I try to do in this way: ? deleteacl user/[EMAIL PROTECTED] [EMAIL PROTECTED] but this remove access only to INBOX folder, any other subfolder are still available. How can i find all mailbox which are available for partical user with cyrusadmin account ? select user/[EMAIL PROTECTED] FIND ALL.MAILBOXES * List all mailboxes for cyrusadmin bot not for [EMAIL PROTECTED] Could someone help me ? Thanks AK 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
Cyrus on PPC64 (SLES9)
Hi, I want to use Cyrus on an IBM OpenPower Machine/PPC64 with SLES9-Distribution. Since the binaries which come with SLES9 are very old (cyrus-imapd 2.2.3), I would like to compile them by myself but I can't find a matching type in the configure-File. Has anyone experiences with building cyrus-imapd on PPC64? Thanks in advance, Markus 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: Do I need idled on or not?
On Fri, Feb 10, 2006 at 12:05:22PM -0600, Richard Wohlstadter wrote: Andreas Hasenack wrote: Note that idled has nothing to do with IDLE support or not: IDLE is always there. The only difference is in the method: without the daemon, the check is done at some poll interval (default 60s IIRC). Is the IDLE daemon more reliable than the polling? I've noticed in It's faster. Thunderbird that IDLE is not very reliable. Many times I've had folders set to IDLE show 'x' new messages and when I click the folder there is actually more new messages than shown in the count. I did some sniffer tests to see the polling in action and sometimes I'll see cyrus indicate to thunderbird that a new message is there and thunderbird completely ignores the message. Maybe newer versions of thunderbird behave better (I tested 2 releases ago) but if anyone else has seen this behavior I was wondering if you tried IDLED daemon and it handled things better. I tried it once with fetchmail, where it worked very well. I didn't have to tell fetchmail to poll the mailbox, it just waited for cyrus' trigger. With idled, that trigger was instantaneous, while with cyrus' poll method (no idled daemon) it could obviously take as long as the poll interval. Now I access the imap server directly and idle isn't that important to me anymore because I have tons of mailboxes which can receive new mail. 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
lockers and bouncing messages
After upgrading to 2.2.12 this weekend, I'm seeing some sporadic bounce messages for incoming mail: Feb 13 10:12:13 smtp2 postfix/lmtp[29737]: EDC1B1702DF: to=[EMAIL PROTECTED], relay=cyrus-be1.onid.oregonstate.edu[128.193.4.141], delay=3, status=bounced (host cyrus-be1.onid.oregonstate.edu[128.193.4.141] said: 563 lockers (in reply to end of DATA command)) I'm using the following backends: annotation_db: skiplist duplicate_db: berkeley-nosync mboxlist_db: skiplist quota_db: quotalegacy seenstate_db: skiplist subscription_db: flat tlscache_db: berkeley-nosync This is a Debian stable system using libdb4.3 (4.3.27-2). I assume this message is coming from the db4.3 based duplicate_db, but I don't understand why it is generating a bounce message in the lmtp response. The sending mail server is probably interpreting 563 as a SMTP/LMTP status code. :( Here is what I see for db4 stats: # db4.3_stat -c -h /var/spool/cyrus/config/db 33224 Last allocated locker ID 0x7fff Current maximum unused locker ID 9 Number of lock modes 5 Maximum number of locks possible 5 Maximum number of lockers possible 5 Maximum number of lock objects possible 291 Number of current locks 309 Maximum number of locks at any one time 582 Number of current lockers 611 Maximum number of lockers at any one time 2 Number of current lock objects 10 Maximum number of lock objects at any one time 2508007 Total number of locks requested 2507716 Total number of locks released 0 Total number of lock requests failing because DB_LOCK_NOWAIT was set 370 Total number of locks not immediately available due to conflicts 0 Number of deadlocks 0 Lock timeout value 0 Number of locks that have timed out 0 Transaction timeout value 0 Number of transactions that have timed out 17MB 720KB The size of the lock region 471 The number of region locks that required waiting (0%) And yes, the number of lockers does appear to be increasing. I'm considering switching duplicate and tls_cache to skiplist. Maybe this email ends up just being another data point against using berkeley db (4.3 at least), but if anyone has any comments are suggestions, I'd love to hear them. Thanks, Andy 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: deliver in 2.3.1 cause Memory fault
Patrice wrote: Hi, I used this command on 2.2.12 to make a local delivery for warning messages. cat mymail.txt|deliver -- [EMAIL PROTECTED] with mymail.txt being correctly formatted. the deliver was working fine. the same command with 2.3.1 cause a Memory fault with no log. This bug has already been fixed in CVS. -- Kenneth Murchison Project Cyrus Developer/Maintainer Carnegie Mellon University 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: from 2.2.12 to 2.3.1, mailbox has invalid format
Nicolas KOWALSKI wrote: Hello, I am testing the migration from a 2.2.12 installation, compiled with the default options (./configure without any option), to a 2.3.1 installation, also compiled with the default options. The databases used are the default for both. The system is Debian 3.1, using db3 for the berkeley databases (but this should not matter because we do not use tls caching or duplicate suppression). When I start the server using the new binaries, accessing some mailboxes is not possible, the server sending a mailbox has invalid format error. If I run reconstruct on these mailboxes, everything runs fine afterwards. Did I forget something ? Should I run reconstruct unconditionnaly on all mailboxes to prevent any inconsistencies during upgrades ? You shouldn't have to do a reconstruct unless there truely is something wrong with the mailbox. The various services are supposed to do an on-the-fly upgrade of the mailboxes. -- Kenneth Murchison Project Cyrus Developer/Maintainer Carnegie Mellon University 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
Murder cluster questions
I have some questions, mainly around murder and versions. We're looking to expand to a Murder cluster, but are still running 2.2 versions of the software. Obviously, i would like to use the latest version for any new installs, so I was wondering - both in the context of building the cluster as well as future upgrades - if there is a 'all same version' requirement (i.e. all servers must be upgraded at the same time) or whether the protocol was standard enough that it didn't matter (Between frontend and backends? Between backends (i.e. moving a mailbox)? Master vs frontend vs backend?) Naturally, this question doesn't involve using new features not present in the older versions. Thanks in advance for your responses! -- Brenden Conte System Programmer, CMT.CIO Rensselaer Polytechnic Institute (518)276-4264 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
cyrus store on an iscsi san?
Howdy, Is anyone running their cyrus mail store on an iSCSI SAN? Can you comment on performance, problems, gotchas? Thanks! -David 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: from 2.2.12 to 2.3.1, mailbox has invalid format
Ken Murchison [EMAIL PROTECTED] writes: Nicolas KOWALSKI wrote: I am testing the migration from a 2.2.12 installation, compiled with the default options (./configure without any option), to a 2.3.1 installation, also compiled with the default options. The databases used are the default for both. The system is Debian 3.1, using db3 for the berkeley databases (but this should not matter because we do not use tls caching or duplicate suppression). When I start the server using the new binaries, accessing some mailboxes is not possible, the server sending a mailbox has invalid format error. If I run reconstruct on these mailboxes, everything runs fine afterwards. You shouldn't have to do a reconstruct unless there truely is something wrong with the mailbox. The various services are supposed to do an on-the-fly upgrade of the mailboxes. Well, one of the mailboxes which trigger this error is mine, and it does work without any problem with our current Cyrus 2.2.12 installation. That's why I am surprised... What may I provide to help understanding/debugging what's going on ? Thanks, -- Nicolas 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
Setting QUOTA through PHP ...
g'day ... I'm trying to fix up the mailadmin interface we are using for Cyrus, and the last thing I know to be broken is PHPs internal 'imap_set_quota' command ... namely, it no longer accept a non-integer value for the quota, so you can't pass 'none' to it ... So, I'm looking at the Pear Net_Cyrus module, which looks like it should work ... I'm trying to do: $quota = new Net_Cyrus(); $quota-connect([EMAIL PROTECTED], $password, $mail_server_name, $mail_server_port); $quota-setQuota(user..$user, none); but, its not removing the quota, altho changing none - any #, it will set the quota properly ... so my syntax looks to be right ... tracing the code, it gets down to Net_IMAPProtocol.php, with the function being: function cmdSetQuota($mailbox_name, $storageQuota = null ,$messagesQuota = null ) { //Check if the IMAP server has QUOTA support if( ! $this-hasQuotaSupport() ){ return new PEAR_Error(This IMAP server does not support QUOTA's! ); } if( ($messagesQuota == null) ( $storageQuota == null) ){ return new PEAR_Error('$storageQuota and $messagesQuota parameters can\'t be both null if you want to use quota'); } $mailbox_name=sprintf(\%s\,$this-utf_7_encode($mailbox_name) ); //Make the command request $param=sprintf(%s (,$mailbox_name); if($storageQuota != null ){ $param=sprintf(%sSTORAGE %s,$param,$storageQuota); if( $messagesQuota != null ){ //if we have both types of quota on the same call we must append an space between // those parameters $param=sprintf(%s ,$param); } } if($messagesQuota != null ){ $param=sprintf(%sMESSAGES %s,$param,$messagesQuota); } $param=sprintf(%s),$param); return $this-_genericCommand('SETQUOTA', $param ); } Putting a 'print $param' just before the _genericCommand, the output is: user.cotton (STORAGE none) So, it would be passing: SETQUOTA user.cotton (STORAGE none) to the backend ... again, if none == an integer #, the quota gets set, so it looks like the syntax itself is right, but 'none' is wrong ... Is anyone doing this with PHP that has gotten around the above issue? Is there something obviously wrong with the way the SETQUOTA is being generated? Thanks ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 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
Removing quotas in 2.3.1 broken?
Greets. I'm having problems removing quotas in Cyrus 2.3.1. I'm using Simon's 2.3.1-2 RPM. It looks like the command attempts to remove the mailbox quota but instead ends up doing something else. What I'm not sure of so lots of logs and details provided: Before starting I run quota -f to make sure everything is sane: bash-3.00$ /usr/lib/cyrus-imapd/quota -f Quota % Used Used Root 6000 user.drfickle 600 4120 user.lnxgeek 6000 user.osubeav 8007 user.scottrus Using cyradm I look at the existing quota for user.scottrus, remove it, then look at it again. [EMAIL PROTECTED] users]# cyradm --user cyrus localhost Password: localhost.localdomain lq user.scottrus STORAGE 7/80 (0.000875%) localhost.localdomain sq user.scottrus none remove quota localhost.localdomain lq user.scottrus / localhost.localdomain quit The last listquota command above returns odd results. I would expect to see blank line as with mailboxes that have been created without a quota limit set. Looking at the trace though everything looks okay: 11398677184 RLIST 1139867718* LIST (\Noselect) . 4 OK Completed (0.000 secs 0 calls) 11398677225 GETQUOTA user.scottrus 1139867722* QUOTA user.scottrus (STORAGE 7 80) 5 OK Completed 11398677276 SETQUOTA user.scottrus () 11398677276 OK Completed 11398677307 GETQUOTA user.scottrus 1139867730* QUOTA user.scottrus () 7 OK Completed However the quota command still shows some odd results for user.scottrus after attempting to remove the quota: bash-3.00$ /usr/lib/cyrus-imapd/quota -f Quota % Used Used Root 6000 user.drfickle 600 4120 user.lnxgeek 6000 user.osubeav 7 user.scottrus -- Scott Russell [EMAIL PROTECTED] IBM Linux Technology Center System Admin 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: Setting QUOTA through PHP ...
Marc G. Fournier wrote: So, it would be passing: SETQUOTA user.cotton (STORAGE none) to the backend ... again, if none == an integer #, the quota gets set, so it looks like the syntax itself is right, but 'none' is wrong ... Is anyone doing this with PHP that has gotten around the above issue? Is there something obviously wrong with the way the SETQUOTA is being generated? I'm looking at the same issue but in doing so ran into another quota problem, see my previous post about quotas in 2.3.1. For what you're running into see http://pear.php.net/bugs/bug.php?id=2657. After I figure out why cyradm from 2.3.1 cannot remove quotas I plan to try and patch cmdSetQuota in IMAPProtocol.php. Of course, if you patch it first please pass it along or append it to the bug! :) -- Scott Russell [EMAIL PROTECTED] IBM Linux Technology Center System Admin 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: Murder cluster questions
Brenden Conte wrote: I have some questions, mainly around murder and versions. We're looking to expand to a Murder cluster, but are still running 2.2 versions of the software. Obviously, i would like to use the latest version for any new installs, so I was wondering - both in the context of building the cluster as well as future upgrades - if there is a 'all same version' requirement (i.e. all servers must be upgraded at the same time) or whether the protocol was standard enough that it didn't matter (Between frontend and backends? Between backends (i.e. moving a mailbox)? Master vs frontend vs backend?) Naturally, this question doesn't involve using new features not present in the older versions. I don't believe that any changes to the MUPDATE protocol have been made between 2.2 and 2.3, so upgrading single components *shouldn't* be a problem. However, given that the cyrus.index and cyrus.cache files contain additional info in 2.3, I probably wouldn't move mailboxes from 2.3 backends to 2.2 backends. Note that we haven't done a migration such as this at CMU (yet) so what I've said is purely an educated guess. I haven't spent a lot of time thinking through all of the particulars. -- Kenneth Murchison Project Cyrus Developer/Maintainer Carnegie Mellon University 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
Cyrus autocreate mailboxes
Hi, i search for a way to autocreate submailboxes in cyrus imap 2.2.14! My users are managed in Web-cyradm with a MySQL backend. I have tried to patch the cyrus-ebuild on my gentoo server, that was successful. But with the options... ---zap--- autocreateinboxfolders: sent|drafts|spam|templates autosubscribeinboxfolders: sent|spam ---zap--- nothing happened. Only the INBOX is there if i try to add a user through web-cyradm. Did I make an error? Thanks P. Schwarz 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: Murder cluster questions
I have some questions, mainly around murder and versions. We're looking to expand to a Murder cluster, but are still running 2.2 versions of the software. Obviously, i would like to use the latest version for any new installs, so I was wondering - both in the context of building the cluster as well as future upgrades - if there is a 'all same version' requirement (i.e. all servers must be upgraded at the same time) or whether the protocol was standard enough that it didn't matter (Between frontend and backends? Between backends (i.e. moving a mailbox)? Master vs frontend vs backend?) Naturally, this question doesn't involve using new features not present in the older versions. I don't believe that any changes to the MUPDATE protocol have been made between 2.2 and 2.3, so upgrading single components *shouldn't* be a problem. However, given that the cyrus.index and cyrus.cache files contain additional info in 2.3, I probably wouldn't move mailboxes from 2.3 backends to 2.2 backends. Note that we haven't done a migration such as this at CMU (yet) so what I've said is purely an educated guess. I haven't spent a lot of time thinking through all of the particulars. We've run a murder with 2.3 backends, 2.2 frontends and used both 2.3 and 2.2 (at different times) for the murder master with out problems. We've made no attempt at running a mix of backend versions, though as Ken mentioned it shouldn't be a problem as long as you don't transfer mailboxes. -Patrick 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: Cyrus autocreate mailboxes
Mark Schwarz wrote: But with the options... ---zap--- autocreateinboxfolders: sent|drafts|spam|templates autosubscribeinboxfolders: sent|spam ---zap--- nothing happened. Only the INBOX is there if i try to add a user through web-cyradm. Did I make an error? You didn't show your hold imapd.conf but you also need autocreatequota. See man imapd.conf. -- Scott Russell [EMAIL PROTECTED] IBM Linux Technology Center System Admin 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: Cyrus autocreate mailboxes
Mark Schwarz wrote: Hi, i search for a way to autocreate submailboxes in cyrus imap 2.2.14! My users are managed in Web-cyradm with a MySQL backend. I have tried to patch the cyrus-ebuild on my gentoo server, that was successful. But with the options... ---zap--- autocreateinboxfolders: sent|drafts|spam|templates autosubscribeinboxfolders: sent|spam ---zap--- nothing happened. Only the INBOX is there if i try to add a user through web-cyradm. Did I make an error? No, you can't use web-cyradm and the autocreate patch *yet* (I've been trying :P). Please see http://savannah.nongnu.org/bugs/?func=detailitemitem_id=15258 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: Cyrus autocreate mailboxes
On Tue, 2006-02-14 at 01:06 -0500, Ed wrote: Mark Schwarz wrote: Hi, i search for a way to autocreate submailboxes in cyrus imap 2.2.14! My users are managed in Web-cyradm with a MySQL backend. I have tried to patch the cyrus-ebuild on my gentoo server, that was successful. But with the options... ---zap--- autocreateinboxfolders: sent|drafts|spam|templates autosubscribeinboxfolders: sent|spam ---zap--- nothing happened. Only the INBOX is there if i try to add a user through web-cyradm. Did I make an error? No, you can't use web-cyradm and the autocreate patch *yet* (I've been trying :P). Please see http://savannah.nongnu.org/bugs/?func=detailitemitem_id=15258 I just have my system automatically send an email to the account as it's created which autocreates the folders, sieve scripts, subscriptions etc. Of course you need to have the 'auto' patches installed... Craig 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