How do the 'expunge_days' option in imapd.conf and the -X flag to
cyr_expire play together? Currently we're using this cyrus.conf entry:
delprune cmd=cyr_expire -E 3 -X 3 -D 3 at=0400
I'm not sure if we should use 'expunge_days: 3' from now on or if it
doesn't matter?
Cheers,
Hi,
I've got a question regarding the tcp_keepalive option that's new in Cyrus
2.4: we've always had problems with POP and IMAP processes that got stuck
when a connection was dropped in the right way. It's gotten better over
the years, but it still happens with 2.3.14. I'm thinking that
Hi Pascal,
thanks for your reply! I decided to ask my more specific questions in
separate mails, but I have a few follow-up questions for you.
--On 5. Januar 2012 19:50:28 +0100 Pascal Gienger
pascal.gien...@uni-konstanz.de wrote:
In principle it is simple, but I hit a hard ground today.
On Fri, 2012-01-06 at 10:22 +0100, Sebastian Hagedorn wrote:
How do the 'expunge_days' option in imapd.conf and the -X flag to
cyr_expire play together? Currently we're using this cyrus.conf entry:
delprunecmd=cyr_expire -E 3 -X 3 -D 3 at=040
I'm not sure if we should use 'expunge_days:
On Fri, January 6, 2012 11:04 am, Sebastian Hagedorn wrote:
Hi Pascal,
thanks for your reply! I decided to ask my more specific questions in separate
mails, but I have a few follow-up questions for you.
--On 5. Januar 2012 19:50:28 +0100 Pascal Gienger
pascal.gien...@uni-konstanz.de wrote:
Hi Eric,
--On 6. Januar 2012 15:00:44 +0100 Eric Luyten eric.luy...@vub.ac.be
wrote:
To give you an idea : 73k users, 508k mailboxes, 4.5 TB of messages, 48M
messages.
In an additional effort to grasp the dynamics of our central mail system
(when hosting over 10k users it pays to have
Ok,
I didn't notice that it is a separate patch, because the cyrus-imapd
package of RHEL/CentOS was compiled with that patch, in Ubuntu it isn't.
The patch works fine for several years now and I don't think that any
new features will be added. Why hasn't it been incorporated and merged
into
Do you know what format the seen files are in on the old server? I think
you should be able to copy them across with the rest of the mail spool
using rsync, but the default database format for seen might have changed.
The default in 2.4 appears to be skiplist.
Check the setting
On Fri, January 6, 2012 3:05 pm, Sebastian Hagedorn wrote:
Hi Eric,
--On 6. Januar 2012 15:00:44 +0100 Eric Luyten eric.luy...@vub.ac.be
wrote:
To give you an idea : 73k users, 508k mailboxes, 4.5 TB of messages, 48M
messages. In an additional effort to grasp the dynamics of our central
On Fri, Jan 06, 2012 at 03:20:06PM +0100, Marten Lehmann wrote:
Ok,
I didn't notice that it is a separate patch, because the cyrus-imapd
package of RHEL/CentOS was compiled with that patch, in Ubuntu it isn't.
The patch works fine for several years now and I don't think that any
new
On Fri, Jan 06, 2012 at 11:04:26AM +0100, Sebastian Hagedorn wrote:
With meta-partition on a fast SSD device this even would not have
occured (500 GB SSD needed in our case)
We don't have any of those, unfortunately ...
As nice as SSDs are, they wouldn't have helped - the IO hit is
On Fri, Jan 06, 2012 at 10:17:26AM -0500, Ron Vachiyer wrote:
however it doesn't create any .seen files like the 2.1.x version, it seems to
store seen information in the cyrus.index file in each users mailspool
directory. I am using the invoca rpm build, is this a particularity or is
there
On Fri, Jan 06, 2012 at 07:36:15AM -0500, Adam Tauno Williams wrote:
On Fri, 2012-01-06 at 10:22 +0100, Sebastian Hagedorn wrote:
How do the 'expunge_days' option in imapd.conf and the -X flag to
cyr_expire play together? Currently we're using this cyrus.conf entry:
delprune
Seen data is only stored in .seen files for shared or other user
mailboxes. The seen data for the mailbox owner is stored in the
cyrus.index. This has two benefits:
1) lower IO for the most common case. We need to update the
cyrus.index file anyway to record the new MODSEQ.
2)
Hello,
Sorry - I've been planning to do it for ages, and it just hasn't happened
due to other things always being more pressing. It's on the MUST HAVE
list for 2.5.
ok, but where can I find a patch for the current 2.4.9 release of Ubuntu
11.10? The latest release I can find at
On Fri, January 6, 2012 5:50 pm, Bron Gondwana wrote:
I'm not convinced it was the best idea (after the
troubles people have had with it)...
Hey, don't worry too much. We'll survive :-)
Eric (taking the opportunity to thank you for your continuing
efforts in developing and
On 01/06/2012 01:05 PM, Eric Luyten wrote:
On Fri, January 6, 2012 5:50 pm, Bron Gondwana wrote:
I'm not convinced it was the best idea (after the
troubles people have had with it)...
Hey, don't worry too much. We'll survive :-)
Agreed. Two hours of high load on a Sunday morning was
Hello,
Sorry - I've been planning to do it for ages, and it just hasn't
happened
due to other things always being more pressing. It's on the MUST HAVE
list for 2.5.
ok, but where can I find a patch for the current 2.4.9 release of Ubuntu
11.10? The latest release I can find at
Oh, if you've already moved the mailbox and the seen file hasn't
been moved yet... yeah, that's messy :(
The main problem is that the seen file is indexed by UNIQUEID
rather than mailbox name, otherwise you could just copy-paste
the sequence out and run
TAG UID STORE paste +Flags
On Fri, Jan 06, 2012 at 01:40:10PM -0500, Ron Vachiyer wrote:
To be clear, here is my scenario;
I have 8000 user accounts, 40+Gigs of email on a 2.1.17 server. They all
seem to be using .seen files stored in /var/lib/imap/user/u/user.seen files.
The mailspool is in
20 matches
Mail list logo