Sounds like some sort of fs error. If you can do nothing else, and it is present, try moving the current directory out of the way, and recreating the directory and then run reconstruct then delete....
Of course there is always the method of dump mailboxes.db file, edit, reimport, but that won't necessarily solve the underlying cause of your problem, just give you a quick fix to get rid of the mailbox.
HTH, B
Will Prater wrote:
On Dec 2, 2003, at 1:37 PM, Andrew Morgan wrote:
On Tue, 2 Dec 2003, Will Prater wrote:
List,
I have a stuck mailbox. I have tried every method to delete it.
Here is an example of output from cyradm
---- localhost.mercurycloud.net> dm user/graeme.mercurycloud.net deletemailbox: System I/O error localhost.mercurycloud.net> cm user/graeme.mercurycloud.net createmailbox: Mailbox already exists localhost.mercurycloud.net> ----
I think I need to edit the db3 databse? Any ideas?
Thanks
Have you tried running reconstruct on the mailbox first? I'd try to make the mailbox work correctly, then try to delete it.
Same results
----
> su cyrus -c '/usr/local/cyrus/bin/reconstruct -f user/graeme.mercurycloud.net'
user.graeme^mercurycloud^net: System I/O error No such file or directory
----
Any more ideas on this one?
Thanks
-- Robert Scussel 1024D/BAF70959/0036 B19E 86CE 181D 0912 5FCC 92D8 1EA1 BAF7 0959
