Question about managing over-quotas mailboxes and deleted mails
Hi, i want to ask is there some way to solve the problem with users that have over-quota in their mailboxes. I'm not sure if they delete there messages with purge delete or not. I suppuse if they don't delete the messages then mailbox going to be over quota. Is there some way to understand if some message is marked like deleted, or not? We can increase the quota, but i want to understand what is the real reason for over quota for these users. Thanks in advanced! Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus upgrade from 2.1.18 to 2.2.13 moved email messages
> "Alain Spineux" <[EMAIL PROTECTED]>: > You would have won some time if you had read one of my previous post > in another thread about pitfall you can meet when migrating. The > thread title is "Migration 32 to 64 bit". It could still help you to > understand what you did :-) Thanx, I'll study it. I assume it's this one...? http://permalink.gmane.org/gmane.mail.imap.cyrus/28354 (this is my home "server" (a Pentium II 233MHz, that have been running more or less continously since 1999), so I don't have any test systems to migrate to. But I _do_ have an rsync copy of the spool, on a separate HD. So I would eventually have been able to recover most of the messages, I think) > Be aware that we are not all debian user, and dont know the script and > tips provided by debian to help in migration. Anyway specify the > source of your information and actions is a gooud practice. I've tried to follow the instructions for the upgrade from 2.1 to to 2.2 in /usr/share/doc/cyrus-common-2.2/UPGRADE.Debian.gz (installed by the cyrus-common-2.2 package of debian etch), which refers to the database upgrade steps of the "Upgrading from cyrus 1.5.x in the same document. The final step in the 1.5.x upgrade section, refers to the /usr/share/doc/cyrus-common-2.2/README.Debian.database.gz (installed by the same package) for database upgrades. This document describes the conversion of the /var/lib/cyrus and the SUBS and SEEN databases from bdb to skiplist, and the /var/lib/cyrus databases was when things messed up for me, and I started posting messages to the list. (Side note: I already was on skiplists for the SEEN databases in 2.1.x. I can't quite remember, but I think it was after losing the BDB SEEN databases for the second or third time. I have had no problems since then, but the deliver.db (still in BDB) has gone corrupt on me a couple of times) And Alain: thanx again! You have been very helpful in this! - Steinar Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus upgrade from 2.1.18 to 2.2.13 moved email messages
> Sebastian Hagedorn <[EMAIL PROTECTED]>: > -- Steinar Bang <[EMAIL PROTECTED]> is rumored to have mumbled on 28. November > 2007 20:55:16 +0100 regarding Cyrus upgrade from 2.1.18 to 2.2.13 > moved email messages: >> What previously was mail/s/user/sb/ is now mail/u/s/user/sb/ > That means you are using fulldirhash. It's an option in /etc/imapd.conf. Ok. Thanx for the info! What I do on debian, and debian-ish systems, is to RCS version all config files I touch. When an upgrade brings in a new version of the file, I check that in, and put in my custom settings (for cyrus, it's using imaps, and allowing 8 bit headers to survive). So when the packager introduces new settings I usually adopt them (it's on the principle that when the upstream package changes, it's less hassle to change with it, than to stay with settings and behaviour that may become unsupported at some point in time). >> And my restored mailbox.db probably points to the old structure...? So >> how to I create one that points to the new structure? > It might be easier to reverse the process. Disable the feature and run > rehash. No promises, though. I have to think about this, and try to understand what happened. Thanx again! Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Restricting admin logins
At the moment we patch the Cyrus IMAP server source so that administrators (admins in the config file) can only log in from certain IP addresses. I was wondering if there is a better way to do this or whether some means of achieving this is planned for future releases? We have two patches we currently use: 1/ adds a new flag to imapd which means 'do not allow administrative logins' and we use this flag on the instance on port 143 but not on another instance on port 144. Port 144 can then be firewalled to everyone apart from our administrative clients. 2/ adds a new config file option 'admins_ip' which is a list of subnets from which administrative logins are permitted. If it would be of benefit I would be happy to clean up either of these and submit it to the developers. Thanks, Andy Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
[POLL] timsieved STARTTLS implementation
Folks, I have recently been informed that Cyrus timsieved has had an incompatible MANAGESIEVE STARTTLS implementation since v2.1.10. The problem is that the server is supposed to automatically issue a CAPABILITY response at the completion of STARTTLS, but this functionality was removed in v2.1.10 (see bug #1338 for details). My question is this: If I fix timsieved to be compliant with the MANAGESIEVE text (which has always been consistent), will this break any client implementations? -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Restricting admin logins
On Nov 29, 2007 3:15 PM, Andy Fiddaman <[EMAIL PROTECTED]> wrote: > > At the moment we patch the Cyrus IMAP server source so that administrators > (admins in the config file) can only log in from certain IP addresses. > > I was wondering if there is a better way to do this or whether some means > of achieving this is planned for future releases? Yes have 3 imapd.conf, all common option in one imapd_common.conf and @include this file in the two other with different admins options Then start two different port and some firewall rules to achieve your need. > > We have two patches we currently use: > > 1/ adds a new flag to imapd which means 'do not allow administrative > logins' and we use this flag on the instance on port 143 but not on > another instance on port 144. Port 144 can then be firewalled to everyone > apart from our administrative clients. > > 2/ adds a new config file option 'admins_ip' which is a list of subnets > from which administrative logins are permitted. > > If it would be of benefit I would be happy to clean up either of these and > submit it to the developers. > > Thanks, > > Andy > > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Alain Spineux aspineux gmail com May the sources be with you Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
[no subject]
>Message: 3 >Date: Wed, 28 Nov 2007 17:12:38 +0200 >From: "Leon Kolchinsky" <[EMAIL PROTECTED]> >Subject: RE: Can't delete cyrus mailbox? >To: "'Craig White'" <[EMAIL PROTECTED]>, > >Message-ID: <[EMAIL PROTECTED]>Content-Type: text/plain; >charset="windows-1255" > > Hello All, > > > > I've moved my old mail server to a new hardware and everything is > working > > fine. Although I found some redundant mail accounts and deleted some of > > them. > > > > The problem is that I'm not able to delete cyrus mailbox this way: > > > > # cyradm --user cyrus --server localhost --auth plain > > Password: > > IMAP Password: > > > > localhost> lam user/cyrus > > cyrus lrswipcda > > > > localhost> lm user/cyrus > > user/cyrus (\HasNoChildren) > > > > localhost> dm user/cyrus > > deletemailbox: Operation is not supported on mailbox > > > > > > Any help please? > > check the unix permissions on the folder/files > > Craig > >Hi, > >No problem with permissions: > >drwx-- 2 cyrus mail 200 Nov 28 08:40 cyrus > ># ls -l /var/spool/imap/user/cyrus >total 36 >-rw--- 1 cyrus mail 8466 Jan 24 2006 1. >-rw--- 1 cyrus mail 1312 Nov 28 08:04 cyrus.cache >-rw--- 1 cyrus mail 161 Nov 28 08:40 cyrus.header >-rw--- 1 cyrus mail 136 Nov 28 08:04 cyrus.index >-rw--- 1 cyrus mail 8464 Nov 28 03:00 cyrus.squat > > ># cyradm --user cyrus --server localhost --auth plain >Password: >IMAP Password: > >localhost> lam user/cyrus >cyrus lrswipcda > >localhost> dm user/cyrus >deletemailbox: Operation is not supported on mailbox > > >Any help please? > > > >-- > >___ >Info-cyrus mailing list >Info-cyrus@lists.andrew.cmu.edu >https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > > >End of Info-cyrus Digest, Vol 28, Issue 75 >** Correct me if I'm worng but is it permissible to delete the mailbox you are currently logged in to? that could be the whole problem there and cyrus is the admin user so shouldn't it be protected by itself? Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Can't delete cyrus mailbox?
I imagine you know cyrus advise against admin account having mailbox ! Is "cyrus" and admin account in imapd.conf ? Maybe you could try to create a second admin account in imapd.conf, give him a password and use this account to remove the "cyrus" mailbox. OR dump the mailboes list using ctl_mboxlist, remove any reference to cyrus milbox and then restore the modified configuration. Finally remove the remaining directory manually Regards On Nov 28, 2007 4:12 PM, Leon Kolchinsky <[EMAIL PROTECTED]> wrote: > > > Hello All, > > > > > > I've moved my old mail server to a new hardware and everything is > > working > > > fine. Although I found some redundant mail accounts and deleted some of > > > them. > > > > > > The problem is that I'm not able to delete cyrus mailbox this way: > > > > > > # cyradm --user cyrus --server localhost --auth plain > > > Password: > > > IMAP Password: > > > > > > localhost> lam user/cyrus > > > cyrus lrswipcda > > > > > > localhost> lm user/cyrus > > > user/cyrus (\HasNoChildren) > > > > > > localhost> dm user/cyrus > > > deletemailbox: Operation is not supported on mailbox > > > > > > > > > Any help please? > > > > check the unix permissions on the folder/files > > > > Craig > > > > > Hi, > > No problem with permissions: > > drwx-- 2 cyrus mail200 Nov 28 08:40 cyrus > > # ls -l /var/spool/imap/user/cyrus > total 36 > -rw--- 1 cyrus mail 8466 Jan 24 2006 1. > -rw--- 1 cyrus mail 1312 Nov 28 08:04 cyrus.cache > -rw--- 1 cyrus mail 161 Nov 28 08:40 cyrus.header > -rw--- 1 cyrus mail 136 Nov 28 08:04 cyrus.index > -rw--- 1 cyrus mail 8464 Nov 28 03:00 cyrus.squat > > > # cyradm --user cyrus --server localhost --auth plain > Password: > IMAP Password: > > localhost> lam user/cyrus > cyrus lrswipcda > > localhost> dm user/cyrus > deletemailbox: Operation is not supported on mailbox > > > Any help please? > > > > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Alain Spineux aspineux gmail com May the sources be with you Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Restricting admin logins
On Thu, Nov 29, 2007 at 03:54:29PM +0100, Alain Spineux wrote: > On Nov 29, 2007 3:15 PM, Andy Fiddaman <[EMAIL PROTECTED]> wrote: > > > > At the moment we patch the Cyrus IMAP server source so that administrators > > (admins in the config file) can only log in from certain IP addresses. > > > > I was wondering if there is a better way to do this or whether some means > > of achieving this is planned for future releases? > > Yes have 3 imapd.conf, all common option in one imapd_common.conf > and @include this file in the two other with different admins options > Then start two different port and some firewall rules to achieve your need. Hey, that's a pretty funky idea :) We use a nginx proxy with an authentication daemon which rejects all login attempts as admin. Our imap machines are firewalled so that the only ways you can talk to them are imap or pop via the nginx proxy or send incoming emails to our mxes which will inject them via lmtp to the spam scanning machines which do the final delivery. I do like the different configs for a simpler network layout in a smaller system though. Very clever! Bron. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: TMPFS for socket and log directories?
On Nov 29, 2007, at 21:34, Vincent Fox wrote: > We had sym-linked imap/proc directory to a size-limited > TMPFS a while back. > > Now I'm thinking to do the same for imap/socket and imap/log > > Any reasons against? Other candidates? You're probably not going to see wins on the socket data, since that directory is probably very well cached and doesn't get any/many writes. imap/log will only give you a win if you're doing any debugging logging for someone, which I hope you're not doing very often as it is. I think that proc is probably the biggest win, since it's quite write- happy. -rob Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
TMPFS for socket and log directories?
We had sym-linked imap/proc directory to a size-limited TMPFS a while back. Now I'm thinking to do the same for imap/socket and imap/log Any reasons against? Other candidates? Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
