Removing a mailbox with a very long name
D.J.Mayo at bath.ac.uk
Thu Nov 25 03:45:28 EST 2010
On 24/11/10 23:01, Bron Gondwana wrote:
> On Wed, Nov 24, 2010 at 04:13:11PM +0100, Michael Menge wrote:
>>> We're running Cyrus 2.3.13.
> Any reason why so old? There were some fixes for this shipped
> more in the later 2.3 series releases, because we had the same
> issue at FastMail!
2.3.14 had bugs (didn't work with group: ACLs) and 2.3.15 wouldn't
compile happily on Solaris due to issues with compression libraries, as
I recall. By then, the servers were live so we stayed at that version.
If we did upgrade from 2.3.13 -> 2.3.16 is there anything that would
prevent us from downgrading again if we hit problems? The changelog does
show quite a few improvements!
>> Do you use delete_mode: delayed ?
>> this will rename the folder to $DELETEPREFIX.$OLDNAME.$TIMESTAMP
>> which would result in a longer Name.
>> You can try to rename it to a shorter name and
>> deleting the renamed folder?
> That's what I was going to say! That's how we wound up dealing
> with the worst offenders.
cyradm wouldn't let me even type a name that long! Perhaps I could have
done it via a telnet session, but after DELETE returned "Invalid mailbox
name" I kinda assumed nothing would work.
> If you live anywhere near the Apple campus you could go over and
> have a few choice words with thier mail client developers too...
> FYI: more recent Cyrus rejects the creation of any mailbox with
> INBOX.INBOX (any case) in the internal name (so user.foo.Inbox is
> still fine, but user.foo.Inbox.Inbox is not)
Yes - this would be handy.
>> An other ideas is to remove the mailboxname from the mailbox.db and
>> deleting it on the filesystem.
>> Use on your own risk
>> cyr_dbtool $configdirectory/mailboxes.db skiplist delete
> Yep! That will definitely work.
That's what I did in the end, and it worked a treat!
University of Bath Computing Services, UK
More information about the Info-cyrus