Michael Monnerie wrote:
> CREATE RULE drop_physmessages_with_messages AS ON DELETE TO
> dbmail_messages DO DELETE FROM dbmail_physmessage WHERE id =
> OLD.physmessage_id;
Like I said: don't do that. Try the trigger/rule I posted. It is totally
valid to have physmessages that are used by several me
Michael Monnerie wrote:
>
> DELETE FROM dbmail_physmessage WHERE id NOT IN (SELECT physmessage_id
> FROM dbmail_messages);
This should be added to the integrity check while running dbmail-util -t.
> --> DELETE 94966
>
> So 95k messages were still there, nearly 3GB of wasted space!
>
> I lo
Paul you have duplicated info for Changelog in day 2007-07-02___
DBmail mailing list
DBmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
CREATE RULE drop_physmessages_with_messages AS ON DELETE TO
dbmail_messages DO DELETE FROM dbmail_physmessage WHERE id =
OLD.physmessage_id;
That seems to help. I've created a new user, uploaded 100MB of e-mail,
then just deleted it. And there are no dead physmessages around:
DELETE FROM dbmail_
Hi, I copied some e-mail to an account using imapsync, here's the last
that happened:
Error trying to append: * BYE dbmail IMAP4 server signing off due to timeout
at /usr/bin/imapsync line 1097
Not connected at /usr/bin/imapsync line 1097
Use of uninitialized value in split at
/usr/lib/perl5/si
On Fri, 2007-07-06 at 11:30 -0400, John T. Guthrie III wrote:
> >
> > > Hello all,
> > >
> > > I was wondering if anyone has had any experience with trying to have one
> > > instance of DBmail use database replication to "forward" messages to a
> > > second
> > > instance of DBmail that is located
