Please confirm my understanding here. In a text/plain message,
BODY[TEXT] and BODY[1.TEXT] refer to the same data (the message body),
and BODY[] and BODY[1] refer to the same data (the full message,
header and body). But in a multipart/* message which contains a
message/rfc822 part as its only
Hi.
I am working on a SUSE 9 box, and am trying to make imap, but get the following
error:
linux:/home/benedict/imap/imap-2002e # make lsu
make sslnopwd
make[1]: Entering directory `/home/benedict/imap/imap-2002e'
++
+++
+ Building in
On Thu, 15 Jan 2004, Paul Jarc wrote:
Please confirm my understanding here. In a text/plain message,
BODY[TEXT] and BODY[1.TEXT] refer to the same data (the message body),
and BODY[] and BODY[1] refer to the same data (the full message,
header and body).
No. In a text/plain message,
Mark Crispin [EMAIL PROTECTED] wrote:
On Thu, 15 Jan 2004, Paul Jarc wrote:
Please confirm my understanding here. In a text/plain message,
BODY[TEXT] and BODY[1.TEXT] refer to the same data (the message body),
and BODY[] and BODY[1] refer to the same data (the full message,
header and body).
On Thu, 15 Jan 2004, Paul Jarc wrote:
Now, IIUC, if the top-level message is message/rfc822, then [TEXT] is
(the header and body of) the encapsulated message, [1] is the same,
and [1.HEADER] and [1.TEXT] are the encapsulated header and body
individually.
Yes.
If the encapsulated message
Mark Crispin [EMAIL PROTECTED] wrote:
On Thu, 15 Jan 2004, Paul Jarc wrote:
If the encapsulated message itself is also message/rfc822, then
[1.TEXT] is the header and body of the doubly-encapsulated message,
and there is no way to refer to the header and body individually.
Wrong.
The
