On Wed, Dec 05, 2007 at 11:34:10AM +, David Carter wrote:
> RFC 3501, section 6.3.5:
>
>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 implementation supports
>in
On Wed, 5 Dec 2007, Gabor Gombas wrote:
> Hmm, can a regular user rename his own INBOX? I'm pretty sure no admin
> actions were performed.
RFC 3501, section 6.3.5:
Renaming INBOX is permitted, and has special behavior. It moves
all messages in INBOX to a new mailbox with the given name,
On Tue, Dec 04, 2007 at 10:06:23PM -0500, Wesley Craig wrote:
> The internal Cyrus "mailbox ID" ought to be unique, but it's not. On the
> sub folder, remove the cyrus.header file and reconstruct. This will assign
> a new, unique mailbox ID.
Thanks, that did the trick.
> Any ideal how they e
On Wed, Dec 05, 2007 at 08:48:00AM +, David Carter wrote:
> On Tue, 4 Dec 2007, Wesley Craig wrote:
> Changes to the Cyrus IMAP Server since 2.3.9
> [...]
>
> * Fixed the special case of RENAMEing an Inbox, so that it doesn't
> keep the same mailbox uniqueid, thus allowing it to
On Tue, 4 Dec 2007, Wesley Craig wrote:
> The internal Cyrus "mailbox ID" ought to be unique, but it's not. On
> the sub folder, remove the cyrus.header file and reconstruct. This will
> assign a new, unique mailbox ID. Any ideal how they ended up with the
> same IDs?
Given that a user inbo
The internal Cyrus "mailbox ID" ought to be unique, but it's not. On
the sub folder, remove the cyrus.header file and reconstruct. This
will assign a new, unique mailbox ID. Any ideal how they ended up
with the same IDs?
:wes
On 04 Dec 2007, at 20:09, Gabor Gombas wrote:
> I'm having pro
Hi,
I'm having problems with replication. sync_client bails out, and the log
contains:
Dec 5 02:00:50 mail cyrus/sync_client[6121]: RENAME received NO response:
Rename failed domain!user.foo -> domain!user.foo.bar: Operation is not
supported on mailbox
Why does sync_client want to rename the
