Re: Deleting records from db

2003-02-27 Thread Lawrence Greenfield
   >I encountered this exact situation (directories manually deleted, 
   >leading to an unreconstructable mailbox) about a month ago. The solution 
   >we chose was to export the mailboxes db (ctl_mboxlist -d), delete the 
   >bogus entries from the textfile, then import it back in.
   >
   >However, this may not be the Right Way to fix it. In our case the server 
   >was down anyway (the damaged mailbox had killed an overnight quota check 
   >and corrupted the quota db), so this "brute force and ignorance" approach 
   >made sense at the time.

I would "mkdir" the appropriate directories. This will let reconstruct
run correctly. You can then delete the mailboxes.

So:

% mkdir /var/spool/imap/user/leg
% cyradm localhost
cyradm> reconstruct user.leg
cyradm> sam user.leg  all
cyradm> dm user.leg

Larry



Re: Deleting records from db

2003-02-26 Thread Sebastian Konstanty Zdrojewski
Thank you. I am in a similar situation like yours, because the server is 
still in test mode, so I can apply this solution. Thanks for help! :)

Have a nice day,

En3pY

Simon Brady wrote:

On Wed, 26 Feb 2003, Sebastian Konstanty Zdrojewski wrote:

 

Hi,

I tried with this:

localhost.localdomain> reconstruct user.mailboxname
reconstruct: Operating System Error
The imapd.log file appended the following line:

Feb 26 16:08:48 nexus imapd[30158]: Reconstructing 
'user.massimiliano_rovatti' (not recursive) for user 'postmaster'

Sorry for boring... I would like to get out of this problem without 
deleting the entire database...
   

I encountered this exact situation (directories manually deleted, 
leading to an unreconstructable mailbox) about a month ago. The solution 
we chose was to export the mailboxes db (ctl_mboxlist -d), delete the 
bogus entries from the textfile, then import it back in.

However, this may not be the Right Way to fix it. In our case the server 
was down anyway (the damaged mailbox had killed an overnight quota check 
and corrupted the quota db), so this "brute force and ignorance" approach 
made sense at the time.

--
Simon Brady mailto:[EMAIL PROTECTED]
ITS Technical Services
University of Otago, Dunedin, New Zealand
 

--

Sebastian Konstanty Zdrojewski
IT Analyst
Neticon S.r.l.
via Valtellina, 16 - 20159 Milano
Tel. +39 02 68.80.731
FAX +39 02.60.85.70.41
Cell. +39 349.33.04.311
ICQ # 97334916
--
Web: http://www.neticon.it/
E-mail: [EMAIL PROTECTED]




Re: Deleting records from db

2003-02-26 Thread Simon Brady
On Wed, 26 Feb 2003, Sebastian Konstanty Zdrojewski wrote:

> Hi,
> 
> I tried with this:
> 
> localhost.localdomain> reconstruct user.mailboxname
> reconstruct: Operating System Error
> 
> The imapd.log file appended the following line:
> 
> Feb 26 16:08:48 nexus imapd[30158]: Reconstructing 
> 'user.massimiliano_rovatti' (not recursive) for user 'postmaster'
> 
> Sorry for boring... I would like to get out of this problem without 
> deleting the entire database...

I encountered this exact situation (directories manually deleted, 
leading to an unreconstructable mailbox) about a month ago. The solution 
we chose was to export the mailboxes db (ctl_mboxlist -d), delete the 
bogus entries from the textfile, then import it back in.

However, this may not be the Right Way to fix it. In our case the server 
was down anyway (the damaged mailbox had killed an overnight quota check 
and corrupted the quota db), so this "brute force and ignorance" approach 
made sense at the time.

--
Simon Brady mailto:[EMAIL PROTECTED]
ITS Technical Services
University of Otago, Dunedin, New Zealand



Re: Deleting records from db

2003-02-26 Thread Sebastian Konstanty Zdrojewski
Hi,

I tried with this:

localhost.localdomain> reconstruct user.mailboxname
reconstruct: Operating System Error
The imapd.log file appended the following line:

Feb 26 16:08:48 nexus imapd[30158]: Reconstructing 
'user.massimiliano_rovatti' (not recursive) for user 'postmaster'

Sorry for boring... I would like to get out of this problem without 
deleting the entire database...

Best regards,

En3pY

Dmitry Alyabyev wrote:

Sebastian Konstanty Zdrojewski wrote:

 

Hello,

I have an annoying problem: my collegue deleted phisically the
directories from the user's directory, so the system, while attempting
to delivery a message to a mailbox returns a "I/O Error". Correct until
here.
I need to remove the entries from the mailbox database, but I can't find
the way. Anybody has an idea?
   

do reconstruct the mailbox

 

--

Sebastian Konstanty Zdrojewski
IT Analyst
Neticon S.r.l.
via Valtellina, 16 - 20159 Milano
Tel. +39 02 68.80.731
FAX +39 02.60.85.70.41
Cell. +39 349.33.04.311
ICQ # 97334916
--
Web: http://www.neticon.it/
E-mail: [EMAIL PROTECTED]




Re: Deleting records from db

2003-02-26 Thread Dmitry Alyabyev
Sebastian Konstanty Zdrojewski wrote:

> Hello,
> 
> I have an annoying problem: my collegue deleted phisically the
> directories from the user's directory, so the system, while attempting
> to delivery a message to a mailbox returns a "I/O Error". Correct until
> here.
> 
> I need to remove the entries from the mailbox database, but I can't find
> the way. Anybody has an idea?

do reconstruct the mailbox

-- 
Dimitry



Deleting records from db

2003-02-26 Thread Sebastian Konstanty Zdrojewski
Hello,

I have an annoying problem: my collegue deleted phisically the 
directories from the user's directory, so the system, while attempting 
to delivery a message to a mailbox returns a "I/O Error". Correct until 
here.

I need to remove the entries from the mailbox database, but I can't find 
the way. Anybody has an idea?

I am using the following configuration:

   * Cyrus IMAPD 2.1.11
   * Cyrus SASL 2.1.9
   * Berkeley DB 4.1.24
   * Postfix 1.1.12
   * Users are authenticated through LDAP (pam_ldap)
   * Aliases are managed by LDAP
   * Delivery to mailbox made through LMTP
TIA, En3pY

--

Sebastian Konstanty Zdrojewski
IT Analyst
Neticon S.r.l.
via Valtellina, 16 - 20159 Milano
Tel. +39 02 68.80.731
FAX +39 02.60.85.70.41
Cell. +39 349.33.04.311
ICQ # 97334916
--
Web: http://www.neticon.it/
E-mail: [EMAIL PROTECTED]