The following issue has been CLOSED
======================================================================
http://www.dbmail.org/mantis/view.php?id=276
======================================================================
Reported By: sr
Assigned To:
======================================================================
Project: DBMail
Issue ID: 276
Category: IMAP daemon
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 13-Oct-05 13:07 CEST
Last Modified: 08-Feb-06 07:45 CET
======================================================================
Summary: Possible parsing bug
Description:
Hi all,
dbmail seems unable to parse a message from Applemail, returning on
Outlook Express the error "dbmail IMAP server info: this message could not
be parsed".
Here's the full header:
X-Virus-Scanned: by amavisd-new at recipientdomain.it
X-MailScanner-From: [EMAIL PROTECTED]
X-PAIM_S.n.c.-MailScanner: Found to be clean
X-PAIM_S.n.c.-MailScanner-Information: Please contact the ISP for more
information
X-Mailer: Apple Mail (2.623)
Date: Wed, 12 Oct 2005 15:49:13 +0200
Subject: Very Important Info
From: john doe <[EMAIL PROTECTED]>
Content-Type: multipart/mixed; boundary=Apple-Mail-12-493898493
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Mime-Version: 1.0 (Apple Message framework v623)
Received: from [10.0.0.66] ([10.0.0.66])
by Storage01.senderdomain.com (8.13.1/8.12.11) with ESMTP id
j9CDlPE2012327
for <[EMAIL PROTECTED]>; Wed, 12 Oct 2005 15:47:25 +0200
Received: from Storage01.senderdomain.com ([100.100.100.100] verified)
by popserver.it (CommuniGate Pro SMTP 4.2.3)
with ESMTP-TLS id 21501967 for [EMAIL PROTECTED]; Wed, 12
Oct 2005 15:47:57 +0200
Received: from mail.alias.popserver.it [200.200.200.200]
by localhost with POP3 (fetchmail-6.2.5)
for [EMAIL PROTECTED] (single-drop); Wed, 12 Oct 2005 15:50:21
+0200 (CEST)
X-ExtScanner: Niversoft's FindAttachments (free)
X-AttachExt: pdf
Received: from localhost (localhost [127.0.0.1])
by mailserver.recipientdomain.it (Postfix) with ESMTP id 3F342A6A
for <[EMAIL PROTECTED]>; Wed, 12 Oct 2005 15:50:21 +0200 (CEST)
Received: from mailserver.recipientdomain.it ([127.0.0.1])
by localhost (mailserver [127.0.0.1]) (amavisd-new, port 10024) with
ESMTP
id 11460-06 for <[EMAIL PROTECTED]>;
Wed, 12 Oct 2005 15:50:46 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
by mailserver.recipientdomain.it (Postfix) with ESMTP id B0500A7E
for <[EMAIL PROTECTED]>; Wed, 12 Oct 2005
15:50:46 +0200 (CEST)
Return-Path: [EMAIL PROTECTED]
Could this possibly be a bug?
======================================================================
----------------------------------------------------------------------
paul - 13-Oct-05 21:58
----------------------------------------------------------------------
It's very most likely not the header that's tripping up 2.0's mime parser,
but rather the multipart/mixed character of the message. I've seen this
happen when dbmail 2.0 encounters deeply nested multipart messages.
All this is a thing of the past in 2.1. However, 2.1's ability to deal
robustly with incorrect mime structure can lead to unexpected consequences
as well. Those need to be addressed at some point: they will cause
dbmail-imapd to happily present the incorrect structure to the client,
rather than fall back on text/plain.
----------------------------------------------------------------------
sr - 13-Oct-05 22:12
----------------------------------------------------------------------
I understand this is not going to be fixed in 2.0?
----------------------------------------------------------------------
paul - 14-Oct-05 11:48
----------------------------------------------------------------------
You understand correctly. Not by me anyway.
----------------------------------------------------------------------
aaron - 08-Feb-06 07:45
----------------------------------------------------------------------
Nobody's touching the 2.0 mime parser, it's just too painful.
Issue History
Date Modified Username Field Change
======================================================================
13-Oct-05 13:07 sr New Issue
13-Oct-05 21:58 paul Note Added: 0000942
13-Oct-05 22:12 sr Note Added: 0000943
14-Oct-05 11:48 paul Note Added: 0000944
08-Feb-06 07:45 aaron Status new => closed
08-Feb-06 07:45 aaron Note Added: 0000990
======================================================================
