Re: [Dovecot] 1.1.1-1 gotcha with Fedora Rawhide package

2008-06-27 Thread Dan Horák
Timo Sirainen píše v Pá 27. 06. 2008 v 09:43 +0300: > On Fri, 2008-06-27 at 07:35 +0200, Dan Horák wrote: > > Kenneth Porter píše v Čt 26. 06. 2008 v 16:24 -0700: > > > I just installed the Rawhide package on my CentOS 5 system. The one item > > > that bit me is that the config file defaults to u

Re: [Dovecot] 1.1.1-1 gotcha with Fedora Rawhide package

2008-06-27 Thread Timo Sirainen
On Fri, 2008-06-27 at 09:11 +0200, Dan Horák wrote: > > v1.1 changed, because using the same socket for IPv4 and IPv6 caused the > > The change is > > > IPv4 connections to use IPv4-mapped IPv6 addresses which then caused > > problems. > > > >

Re: [Dovecot] 1.1.1-1 gotcha with Fedora Rawhide package

2008-06-27 Thread Dan Horák
Timo Sirainen píše v Pá 27. 06. 2008 v 10:15 +0300: > On Fri, 2008-06-27 at 09:11 +0200, Dan Horák wrote: > > > v1.1 changed, because using the same socket for IPv4 and IPv6 caused the > > > > The change is > > > > > IPv4 connections to use IP

[Dovecot] Upgrade to 1.1 maildir & shared folders problems

2008-06-27 Thread sami
Hello, We recently upgraded to Dovecot 1.1 from 1.0.5 and we are having few issues: 1) Maildir's are not created anymore for new users if they dont excits, the directories where created before, is this a configuration issue? 2) Cannot subscribe to shared folders, if currently subscribed they wor

[Dovecot] Keeping \Seen flag private

2008-06-27 Thread Imobach González Sosa
Hi all, I wanna to set up shared folders for a couple of users and I'd like that everyone could keep the \Seen flag as private. So if user #1 reads some messages and user #2 not, those messages appear as "unseen" to #2 and "seen" to #1. I've implemented shared folders using namespaces with eve

Re: [Dovecot] Keeping \Seen flag private

2008-06-27 Thread Adam McDougall
Imobach González Sosa wrote: Hi all, I wanna to set up shared folders for a couple of users and I'd like that everyone could keep the \Seen flag as private. So if user #1 reads some messages and user #2 not, those messages appear as "unseen" to #2 and "seen" to #1. I've implemented shared f

Re: [Dovecot] Keeping \Seen flag private

2008-06-27 Thread Adam McDougall
Adam McDougall wrote: Imobach González Sosa wrote: Hi all, I wanna to set up shared folders for a couple of users and I'd like that everyone could keep the \Seen flag as private. So if user #1 reads some messages and user #2 not, those messages appear as "unseen" to #2 and "seen" to #1. I'

Re: [Dovecot] Keeping \Seen flag private

2008-06-27 Thread Imobach González Sosa
El Friday 27 June 2008 19:32:52 Adam McDougall escribió: > Adam McDougall wrote: > > Imobach González Sosa wrote: > >> Hi all, > >> > >> I wanna to set up shared folders for a couple of users and I'd like > >> that everyone could keep the \Seen flag as private. So if user #1 > >> reads some message

[Dovecot] 1.1 namespaces and message corruption

2008-06-27 Thread Kyle Wheeler
Hello, I've been trying out the new dovecot's namespace support, and I'm having some issues moving messages between namespaces. Specifically, when I move some messages from a Maildir-based namespace to an mbox-based namespace, the message gets corrupted: its contents are removed, and an entir

Re: [Dovecot] Keeping \Seen flag private

2008-06-27 Thread Asheesh Laroia
On Fri, 27 Jun 2008, Imobach González Sosa wrote: There's no problem in disallowing the users to update the Seen flag. What I want is that every user have their own Seen flags. Timo and others will know more; but for me, I would just deliver the messages to multiple people and see that Doveco

[Dovecot] managesieve server aware?

2008-06-27 Thread Cassidy Larson
Just upgraded to Dovecot 1.1 and thought I'd try out managesieve plugin. My situation is I have two front end proxy boxes and four storage nodes in the back. I have been able to load the managesieve plugin just like I should on the storage nodes, but not on the proxy boxes. My proxy boxes have m

Re: [Dovecot] managesieve server aware?

2008-06-27 Thread Cassidy Larson
Looks like I just need to simply my proxy config to get rid of the server {} blocks and it'll work like it should. -c

[Dovecot] courier IMAP to dovecot migration: folders not showing up

2008-06-27 Thread Jacob Yocom-Piatt
i have been running postfix + courier-imap + cyrus sasl for several years and have some prior experience with dovecot + postfix and had no problems. now that i'm trying to convert an existing courier-imap configuration to dovecot and all the various parts work together (e.g. mail delivery and d

Re: [Dovecot] Keeping \Seen flag private

2008-06-27 Thread Timo Sirainen
On Fri, 2008-06-27 at 15:09 +0100, Imobach González Sosa wrote: > Hi all, > > I wanna to set up shared folders for a couple of users and I'd like that > everyone could keep the \Seen flag as private. So if user #1 reads some > messages and user #2 not, those messages appear as "unseen" to #2 and

Re: [Dovecot] Upgrade to 1.1 maildir & shared folders problems

2008-06-27 Thread Timo Sirainen
On Fri, 2008-06-27 at 10:50 +0300, [EMAIL PROTECTED] wrote: > Hello, > > We recently upgraded to Dovecot 1.1 from 1.0.5 and we are having few > issues: > > 1) Maildir's are not created anymore for new users if they dont excits, > the directories where created before, is this a configuration issue

Re: [Dovecot] Dovecot corrupted index cache

2008-06-27 Thread Timo Sirainen
On Wed, 2008-06-25 at 09:40 -0700, Michael D. Godfrey wrote: > > A guess would be that this is likely due to the endianess of the > > multiple architectures that the index is being accessed with. We have > > the same issue here across i686/x86_64/sparc. I'm about to post to an > > older email th

Re: [Dovecot] Dovecot index, NFS, and multiple architectures

2008-06-27 Thread Timo Sirainen
On Wed, 2008-06-25 at 12:00 -0400, David Halik wrote: > I just reproduced the environment and the index corrupted immediately > across NFS because of the endian issue. > > Jun 25 11:53:34 host IMAP(user): : Rebuilding index file > /dovecot-index/index/user/.INBOX/dovecot.index: CPU architecture