I'm still getting many messages in my dbmail.err file that look
problematic. This is with dbmail-2.2.4 + expunge patch. Do any of
these need bugs filed? They are happening pretty often, so more
debugging info shouldn't be hard to come by.
(There are no permission problems or disk space problems)
Some of these:
Error client socket has set error indicator in fgetc
Error dbmail_message_new_from_stream() failed
Error error deleting scoreboard lock file
[/tmp/dbmail_scoreboard_20977.LCK]
Error error reading extra command info
Warning no empty slot found
Bunch of these:
Error dbmail_message_new_from_stream() failed
Bunch of these:
Error Short write [0 < 118], is your /tmp filesystem full?
Error Short write [0 < 273], is your /tmp filesystem full?
Error Short write [0 < 3], is your /tmp filesystem full?
Error Short write [101 < 126], is your /tmp filesystem full?
Error Short write [10 < 314], is your /tmp filesystem full?
Error Short write [11 < 226], is your /tmp filesystem full?
Bunch of these:
** (process:981): CRITICAL **: dbmail_imap_session_get_msginfo:
assertion `ids &
& g_tree_nnodes(ids)>0' failed
** (process:9824): CRITICAL **: dbmail_imap_session_get_msginfo:
assertion `ids
&& g_tree_nnodes(ids)>0' failed
** (process:9925): CRITICAL **: dbmail_imap_session_get_msginfo:
assertion `ids
&& g_tree_nnodes(ids)>0' failed
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
