well that will be a bug i fear .. could you sent the message so we can
evaluate the problem? thanks
regards roel
Jeroen Hendriks heeft op zondag, 27 apr 2003 om 16:20
(Europe/Amsterdam) het volgende geschreven:
Hi,
While testing DBMail I noticed the following problem:
When reading a base64 encoded mail message the dbmail-imapd header
parser
failes parsing the header.
If the same mail message is being downloaded with dbmail-pop
everything goes
ok.
With loglevel 5 the following debug information is stored.
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: Fetching msgID 2441
(fetch num
2442)^M
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_query(): executing
[SELECT
messageblk FROM messageblks WHERE message_idnr = 2441 ORDER BY
messageblk_idnr]
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_query(): executing
[SELECT
messageblk FROM messageblks WHERE message_idnr = 2441 ORDER BY
messageblk_idnr]
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_start_msg(): starting,
stopbound: '<null>'
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: mime_readheader():
entering
mime loop
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: mime_readheader(): found
double newline; header size: 19 lines
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_start_msg(): found
multipart msg
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_start_msg(): found new
boundary: [07233], msgidx 912
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: update msgbuf updating
308679299694592 304762289389568 304762289389568 579635248531243008
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: update msgbuf: entire fit
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: update msgbuf succes
NOMORE
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_start_msg():
unexpected
end-of-data
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_fetch_headers(): error
fetching message, ID: 2441
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_fetch_headers(): got
error
at level 0
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_query(): executing
[SELECT
messageblk FROM messageblks WHERE message_idnr = 2441 ORDER BY
messageblk_idnr]
Apr 27 15:31:22 notes01 dbmail/imap4d[19908]: db_query(): executing
[SELECT
messageblk FROM messageblks WHERE message_idnr = 2441 ORDER BY
messageblk_idnr]
Apr 27 15:31:23 notes01 dbmail/imap4d[19908]: update msgbuf updating
308679299694592 304762289389568 304762289389568 4294967296
Apr 27 15:31:23 notes01 dbmail/imap4d[19908]: update msgbuf: entire fit
Apr 27 15:31:23 notes01 dbmail/imap4d[19908]: update msgbuf succes
NOMORE
Apr 27 15:31:23 notes01 dbmail/imap4d[19908]: db_fetch_headers():
message
recovered as plain text
Apr 27 15:31:23 notes01 dbmail/imap4d[19908]: db_query(): executing
[SELECT
rfcsize FROM messages WHERE message_idnr = 2441 AND status<2 AND
unique_id
!= '' A
ND mailbox_idnr = 1]
Apr 27 15:31:23 notes01 dbmail/imap4d[19908]: db_query(): executing
[SELECT
seen_flag, answered_flag, deleted_flag, flagged_flag, draft_flag,
recent_flag FROM
messages WHERE message_idnr = 2441 AND status<2 AND unique_id != ''
AND
mailbox_idnr = 1]
Apr 27 15:31:23 notes01 dbmail/imap4d[19908]: db_query(): executing
[SELECT
internal_date FROM messages WHERE mailbox_idnr = 1 AND message_idnr =
2441
AND uni
que_id!=""]
In the mail client is following header is displayed:
from: [EMAIL PROTECTED]
subject: dbmail IMAP server info: this message could not be parsed
followed by a dump of the non encoded message.
A Mysql dbdump with a test dbmail database containing the message
causing
the problem is availible on http://www.bofp.org/dbmail/dbmail.db.gz
(60Kb)
p.s. I have downloaded and tested it with a cvs version from yesterday
Did anyone had this problem before ? or is there a quick fix ?
Regards,
Jeroen Hendriks
Network engineer
e-factory bv
Tel.: +31 (0)475 - 340 975
Fax: +31 (0)475 - 320 351
Web: www.e-factory.nl
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_________________________
R.A. Rozendaal
IC&S
T: +31 30 2322878
F: +31 30 2322305
www.ic-s.nl
