how to set UIDVALIDITY after reconstruct.

2006-01-07 Thread Ramprasad
Hi, I would like to set UIDVALIDITY of all users mailbox after doing reconstruct. Is there a way I can restore UIDVALIDITY of many mailboxes ( ~15k accounts ) to those on a old server I am using cyrus 2.2.3-8 on both servers Thanks Ram

Re: Avoiding duplicates in pop download

2006-01-07 Thread Ken Murchison
Ramprasad wrote: On Fri, 2006-01-06 at 08:11 -0500, Ken Murchison wrote: Ramprasad wrote: Hi all, I have a cyrus server with users connecting and using pop or imap. Some of the pop users have set leave-a-copy flag ON in their email clients. Now I am planning to migrate the mailboxes to a

Virtual domain admins

2006-01-07 Thread Robert Fitzpatrick
Reading the doc at http://asg.web.cmu.edu/cyrus/download/imapd/install-virtdomains.html This suggests adding domain admins in imapd.conf, but I have read that you should not specify a user here that logins in to a mailbox actively. Should this be done? -- Robert Cyrus Home Page:

cyrus22 postfix lmtp virtdomains

2006-01-07 Thread Heiko Garrelfs
Hi, I'm new to this List, so firstly: hello everyone. And as you might suspect: I need some help :-) I read the archives, tried this and that but didn't get it to work. I am trying to set up a mailserver. Debian Sarge, postfix und Cyrus22 from experimental. ( Since Cyrus 21 does not support

Re: how to set UIDVALIDITY after reconstruct.

2006-01-07 Thread Ken Murchison
Ramprasad wrote: Hi, I would like to set UIDVALIDITY of all users mailbox after doing reconstruct. Is there a way I can restore UIDVALIDITY of many mailboxes ( ~15k accounts ) to those on a old server Not without re-writing cyrus.index by hand (for every mailbox). -- Kenneth Murchison

Possibly a bug in backend.c ?

2006-01-07 Thread Febo Aristots
Regarding yesterday's message from meabout cyrus sync_client always refuses to run with an 'Invalid Argument' I believe I've found a bug in backend.c, the module which is used by sync_client and other cyrus programs - at the very least is an inconsistent behaviour on my Fedora Core 1 servers... I