Re: Bug with rename INBOX -> INBOX.blah and replication

2006-12-04 Thread Ken Murchison
Bron Gondwana wrote: On Mon, 04 Dec 2006 19:42:52 -0500, "Ken Murchison" <[EMAIL PROTECTED]> said: Hi Rob, This is already a known problem (bug #2727?). I haven't come up with a "clean" fix yet, although I haven't thought about it much. My reading of this is that it affects SEEN state gener

Re: Bug with rename INBOX -> INBOX.blah and replication

2006-12-04 Thread Bron Gondwana
On Mon, 04 Dec 2006 19:42:52 -0500, "Ken Murchison" <[EMAIL PROTECTED]> said: > Hi Rob, > > This is already a known problem (bug #2727?). I haven't come up with a > "clean" fix yet, although I haven't thought about it much. My reading of this is that it affects SEEN state generally, not just

Re: Bug with rename INBOX -> INBOX.blah and replication

2006-12-04 Thread Ken Murchison
Robert Mueller wrote: Hi Ken There's a bug with replication and renaming INBOX -> INBOX.blah. From http://www.ietf.org/rfc/rfc3501.txt: Renaming INBOX is permitted, and has special behavior. It moves all messages in INBOX to a new mailbox with the given name, leaving INBOX emp

Bug with rename INBOX -> INBOX.blah and replication

2006-12-04 Thread Robert Mueller
Hi Ken There's a bug with replication and renaming INBOX -> INBOX.blah. From http://www.ietf.org/rfc/rfc3501.txt: Renaming INBOX is permitted, and has special behavior. It moves all messages in INBOX to a new mailbox with the given name, leaving INBOX empty. If the server imp