Hello all,
Using a webmail client I insert messages in the database directly
(dbmail_messages, dbmail_physmessage, dbmail_messageblks). DBMail 2.2
has all kinds of (very useful) cache tables, like dbmail_envelope and
dbmail_datefield.
The dbmail_util program repairs these messages without cache entries:
dbmail-util -b. I did this manually, first dbmail-util -b and then
dbmail-util -by.
Repairing DBMAIL for cached envelopes...
Ok. Found [89] missing envelope values.
The problem is that now every physmessage has 2 (two!) dbmail_envelope
entries.
mysql> select * from dbmail_envelope where physmessage_id = '353694';
+----------------+--------+--------------------------------+
| physmessage_id | id | envelope |
+----------------+--------+--------------------------------+
| 353694 | 353651 | ("Thu, 08 May ... smail.net>") |
| 353694 | 353740 | ("Thu, 08 May ... smail.net>") |
+----------------+--------+--------------------------------+
2 rows in set (0.00 sec)
This results in messages being listed twice in our webmail overview.
I've three questions:
1. Is it a bug in dbmail-util that two entries in dbmail_envelope are
inserted?
2. Should I trust that dbmail_envelope has only one entry per
physmessage? This increases speed because no "GROUP BY physmessage_id"
has to be done.
3. Is it a problem if a message doesn't have cached headers/envelope for
normal imap access?
We use DBMail 2.2.10.
Kind regards,
Bert Slagter
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
