Florian Weber wrote:
On Friday 08 April 2005 21:31, I wrote:
At last! That's the first time a problem wasn't due to my stupidity :o)
Which doesn't mean it'd go on like that - here is the first correction.
The jumping-around-problem: silly me. I still had instruction reordering
active in gcc. Switching it off got rid of the jumping and the strangely
disappearing linked list - but did not change anything in the backtrace.
Single stepping led me deep into gmime, but we already new that the crash
happens there :-[
Continuing on a spare copy of my database, I tried removing the offending
mails by hand: use strace to find out the message id that's causing the
crash, delete the corresponding messageblks and let dbmail-util repair the
damage (that's somewhat braindead, seriously messed up my cache, but did work
out after all). The results:
Using strace won't be necessary any longer. I've changed the code a bit so it
will log the offending physmessage_id.
Also, after hitting such a mail, dbmail-util won't barf any longer and just
continue with the next message.
- after removing all offending mails inside a folder, KMail will no longer
hang
That would be something to fix inside the imap code.
- dbmail-util will continue caching physmessages until the next bad message is
encountered (then crash again). The success is persistent.
Like I said, that shouldn't happen anymore. Pick up a snapshot if you like, or
wait for 2.1.1
- quite often gmime will spew a warning: "gmime-WARNING **: Invalid or
incomplete type: : defaulting to application/octet-stream". This does not
stop the processing
Right, I've also seen warning about invalid message-id headers. Ignore them. I
need to find out how to keep those from appearing on the console.
is it some specific message that's crashing dbmail-util?
That's a definite yes. Not only one but lots of them. The same messages
obviously cause the hangs (inside dbmail-imapd, I guess)
I can't say yet what is different about these mails. Could you recommend an
SQL command to get a complete email in readable form when given the
physmessage id? I'm just not used to reading messageblks ;-)
The one you sent me was pretty readable. Was that an example of a message that
caused dbmail-imapd to hangup? If not, could you sent me such a message as well?
I have a certain feeling that either during the migration to PostgreSQL 8 oder
to dbmail-2.1.0 I seriously messed up the DB. Thank god for backups.
It's definitely not in the migration. 2.1.0 doesn't change anything in your
existing database, it just adds a couple of tables. And those are at present
only used during insertion and in dbmail-util -b -y. In fact, you can easily
switch back to 2.0.4 on the same database after trying 2.1.0.
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
