Hi,
I'm seeing a difference in implementation between Courier IMAP and both
UW IMAP (or whatever it is that RedHat ships with 7.1, it looks and smells
like UW IMAP) and Microsoft Exchange IMAP when it comes to retrieving the
MIME headers from an attachment of type message/rfc822. Courier retrieves
the MIME header from the header of the attached message, but the other two
retrieve the attachment headers. For example, the following message
(in between ##### lines for clarity).
######################################################
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 22 May 2002 08:36:26 +0100
From: Me <[EMAIL PROTECTED]>
MIME-Version: 1.0
To: You <[EMAIL PROTECTED]>
Subject: Re: Hi
Content-Type: multipart/mixed;
boundary="------------12345"
This is a multi-part message in MIME format.
--------------12345
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi
--
[EMAIL PROTECTED]
--------------12345
Content-Type: message/rfc822
Content-Disposition: inline
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 21 May 2002 17:54:14 +0100
From: You <[EMAIL PROTECTED]>
MIME-Version: 1.0
To: Me <[EMAIL PROTECTED]>
Subject:Hi
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi
--
[EMAIL PROTECTED]
--------------12345--
######################################################
I added this message to a folder on Courier, UW and Exchange using
IMAP. I then fetched body[2.mime] and body[2.header] from the message
on each IMAP server. Here's the output from each IMAP server:
Courier
#############################################
a1 fetch * body[2.mime]
* 3 FETCH (BODY[2.MIME] {98}
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
)
* 3 FETCH (FLAGS (\Seen \Recent))
a1 OK FETCH completed.
a1 fetch * body[2.header]
* 3 FETCH (BODY[2.HEADER] {225}
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 21 May 2002 17:54:14 +0100
From: You <[EMAIL PROTECTED]>
MIME-Version: 1.0
To: Me <[EMAIL PROTECTED]>
Subject:Hi
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
)
a1 OK FETCH completed.
#############################################
UW
#############################################
a1 fetch * body[2.mime]
* 3 FETCH (BODY[2.MIME] {61}
Content-Type: message/rfc822
Content-Disposition: inline
)
* 3 FETCH (FLAGS (\Recent \Seen))
a1 OK FETCH completed
a1 fetch * body[2.header]
* 3 FETCH (BODY[2.HEADER] {225}
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 21 May 2002 17:54:14 +0100
From: You <[EMAIL PROTECTED]>
MIME-Version: 1.0
To: Me <[EMAIL PROTECTED]>
Subject:Hi
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
)
a1 OK FETCH completed
#############################################
Exchange
#############################################
a1 fetch * body[2.mime]
* 2 FETCH (BODY[2.MIME] {32}
Content-Type: message/rfc822
FLAGS (\Seen \Recent))
a1 OK FETCH completed.
a1 fetch * body[2.header]
* 2 FETCH (BODY[2.HEADER] {175}
Message-ID: <[EMAIL PROTECTED]>
From: You <[EMAIL PROTECTED]>
To: Me <[EMAIL PROTECTED]>
Subject: Hi
Date: Tue, 21 May 2002 17:54:14 +0100
MIME-Version: 1.0
Content-Type: text/plain
)
a1 OK FETCH completed.
#############################################
As you can see 2.mime gets the mime attachment header with UW and with
Exchange but using Courier it retrieves the mime header fields within
the RFC822 message header within the attachment.
Who's right?
Brian
--
[EMAIL PROTECTED]
This e-mail and any attachment is for authorised use by the intended recipient(s)
only. It may contain proprietary material, confidential information and/or be subject
to legal privilege. It should not be copied, disclosed to, retained or used by, any
other party. If you are not an intended recipient then please promptly delete this
e-mail and any attachment and all copies and inform the sender. Thank you.
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users