Thought so! Delete those records from dbmail_subscription: delete from dbmail_subscription where mailbox_id in (53,126);
The fact that this could happen at all, means you either are running with MyISAM tables, or your foreign key restrictions are not (fully) in place. Jorge Bastos wrote: > Paul, > > --- > mysql> select * from dbmail_mailboxes where mailbox_idnr in (126,53); > Empty set (0.00 sec) > --- > > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Paul J Stevens > Sent: terça-feira, 5 de Fevereiro de 2008 8:18 > To: DBMail mailinglist > Subject: Re: [Dbmail] DBMail 2.3.2 released > > > Jorge, > > In your logs I see a lot of these: > > Feb 4 22:15:16 lira dbmail/imap4d[4175]: Debug:[db] > dm_db.c,db_acl_has_right(+4342): checking ACL [read_flag] for user [2] on > mailbox [126] > Feb 4 22:15:16 lira dbmail/imap4d[4175]: Debug:[sql] > dbmysql.c,db_query(+301): > query [SELECT owner_idnr FROM dbmail_mailboxes WHERE mailbox_idnr = 126] > Feb 4 22:15:16 lira dbmail/imap4d[4175]: Debug:[db] > dbmodule.c,db_query(+154): > last query took [0] seconds > Feb 4 22:15:16 lira dbmail/imap4d[4175]: Debug:[sql] > dbmysql.c,db_get_result(+249): row is NULL > Feb 4 22:15:16 lira dbmail/imap4d[4175]: Error:[imapsession] > dbmail-imapsession.c,dbmail_imap_session_get_mbxinfo(+786): failure > retrieving > mbxinfo for unreadable mailbox > > > And the same for mailbox 53. > > What are those mailboxes? Could you run a select for me: > > select * from dbmail_mailboxes where mailbox_idnr in (126,53); > > > > Jorge Bastos wrote: >> No luck Paul, >> I don't if this something with me. >> After started 2.3.2, all work's OK when I select mailbox's that are > empty's, >> but if I select one with messages, I get a "cannot synchronize" in > outlook, >> and in the logs there's something, can you take a look and see if there's >> something that need some tune? >> >> Jorge >> >> >> >> >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf >> Of Paul J Stevens >> Sent: segunda-feira, 4 de Fevereiro de 2008 16:00 >> To: DBMail mailinglist >> Subject: Re: [Dbmail] DBMail 2.3.2 released >> >> Jorge Bastos wrote: >>> Hi Paul, >>> >>> This has the problem that i was facing when i was trying to upgrade, >> right? >> >> I should hope so. >> >> Stop postfix/dbmail/amavis etc. >> Backup your database, >> Install dbmail-2.3.2 >> Apply the sql/mysql/2_2_5-2_3_0.mysql changes >> Start postfix/dbmail/amavis etc. >> >> There is also a 2_3_0-2_3_2.mysql file, but that one is *only* for people >> who >> have email stored by 2.3.0 or 2.3.1 and need that mail. >> >> The schema change from 2.3.1 to 2.3.2 entailed the hash-collision > detection >> and >> prevention as discussed on the list. >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> DBmail mailing list >> [email protected] >> https://mailman.fastxs.nl/mailman/listinfo/dbmail > > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
