I posted something about this when I tried to upgrade to dbmail 2.0.3,
but no one responded. When dbmail 2.0.4 came out I thought I would give
it a shot to see if it fixed the problem, but alas it did not. So here
is a little more detail:
I have a working dbmail w/ postgresql install cirrca 2.0.1. When I
tried to update to dbmail 2.0.3 (and now 2.0.4) I could no longer
retrive messages via IMAP. From the older working dbmail I get a log
like this:
Mar 21 23:32:41 bait dbmail/imap4d[21158]: Fetching msgID 819563 (fetch
num 819564)
Mar 21 23:32:41 bait dbmail/imap4d[21158]: dbpgsql.c,db_query: executing
query [SELECT pm.rfcsize FROM dbmail_physmessage pm, dbmail_messages msg
WHERE pm.id
= msg.physmessage_id AND msg.message_idnr = '819563' AND msg.status< '2'
AND msg.unique_id != '' AND msg.mailbox_idnr = '11']
Mar 21 23:32:41 bait dbmail/imap4d[21158]: dbpgsql.c,db_query: executing
query [SELECT block.messageblk FROM dbmail_messageblks block,
dbmail_messages msg WHE
RE block.physmessage_id = msg.physmessage_id AND msg.message_idnr =
'819563' ORDER BY block.messageblk_idnr]
Mar 21 23:32:41 bait dbmail/imap4d[21158]: db_start_msg(): starting,
stopbound: '<null>'
Mar 21 23:32:41 bait dbmail/imap4d[21158]: mime_readheader(): entering
mime loop
Mar 21 23:32:41 bait dbmail/imap4d[21158]: mime_readheader(): found
double newline; header size: 23 lines
Mar 21 23:32:41 bait dbmail/imap4d[21158]: db_start_msg(): found
singlepart msg
Mar 21 23:32:41 bait dbmail/imap4d[21158]: dbmsgbuf.c,db_update_msgbuf:
update msgbuf_buf updating 131072, 1625, 487, 487
Mar 21 23:32:41 bait dbmail/imap4d[21158]: dbmsgbuf.c,db_update_msgbuf:
update msgbuf: entire fit
Mar 21 23:32:41 bait dbmail/imap4d[21158]: dbmsgbuf.c,db_update_msgbuf
update msgbuf succes NOMORE
Mar 21 23:32:41 bait dbmail/imap4d[21158]: db_start_msg(): exit
Mar 21 23:32:41 bait dbmail/imap4d[21158]: dbmsgbuf.c,db_dump_range:
Dumping range: (1,0) - (1,486)
Mar 21 23:32:41 bait dbmail/imap4d[21158]: dbpgsql.c,db_query: executing
query [SELECT block.messageblk FROM dbmail_messageblks block,
dbmail_messages msg WHE
RE block.physmessage_id = msg.physmessage_id AND msg.message_idnr =
'819563' ORDER BY block.messageblk_idnr]
From the new dbmail 2.0.4 I get a log like this:
Mar 21 23:20:26 bait dbmail/imap4d[20768]: Fetching msgID 54320 (fetch
num 54321)
Mar 21 23:20:26 bait dbmail/imap4d[20768]: dbpgsql.c,db_query: executing
query [SELECT messageblk FROM dbmail_messageblks blk, dbmail_messages
msg WHERE blk.p
hysmessage_id = msg.physmessage_id AND msg.message_idnr = '54320' ORDER
BY blk.messageblk_idnr ASC LIMIT 1]
Mar 21 23:20:26 bait dbmail/imap4d[20768]: mime_readheader(): entering
mime loop
Mar 21 23:20:26 bait dbmail/imap4d[20768]: mime_readheader(): mimeloop
finished
Mar 21 23:20:26 bait dbmail/imap4d[20768]: mime_readheader(): no valid
mime headers found
Mar 21 23:20:26 bait dbmail/imap4d[20768]: db.c,db_get_main_header:
error parsing header of message [54320]
Obviously, the problem appears to be that the new dbmail is not finding
valid headers, where as the old dbmail was.
Any ideas?
Thanks,
Matthew O'Connor
