mailing list archives

meli community discussions

⚠️ if something does not work as intended when interracting with the mailing lists,
reach out Github mirror Gitea repo @epilys:matrix.org

[Imap-protocol] [noob] body[n.header] vs. body[n.mime]?

E-mail headers
From: Petite Abeille <petite_abeille@mac.com>
To: imap-protocol@u.washington.edu
Date: Fri, 08 Jun 2018 12:34:47 -0000
Message-ID: 7A5C9702-B74C-4AA7-9075-449D07B0435B@mac.com permalink / raw / eml / mbox 
Hello,

What's body[n.mime] suppose to return, and when? 

Given the following message:

http://pastebin.com/raw.php?i=M2tTnLEm

With the following parts (as reported by reformime [1]):

1 multipart/mixed
1.1 text/plain
1.2 message/rfc822
1.2.1 multipart/report
1.2.1.1 text/plain
1.2.1.2 message/delivery-status
1.2.1.3 message/rfc822
1.2.1.3.1 text/plain

When does body[n.mime] apply, and what is it suppose to return?

For example, what should one return when asked for body[1.2.mime] vs. body[1.2.header]?

Also, is the part numbering as performed by reformime in line with what IMAP part specifiers expects?

Thanks in advance.


[1] http://www.courier-mta.org/reformime.html
Reply
E-mail headers
From: dave@cridland.net
To: imap-protocol@localhost
Date: Fri, 08 Jun 2018 12:34:47 -0000
Message-ID: 3461.1324470057.646971@puncture permalink / raw / eml / mbox 
On Wed Dec 21 12:05:23 2011, Petite Abeille wrote:
> For example, what should one return when asked for body[1.2.mime]  
> vs. body[1.2.header]?

In this message, I've attached your original message, and this will  
be BODY[2].

I'd expect BODY[2.MIME] to be

"Content-Type: message/rfc822\r\nContent-Disposition:  
inline\r\nContent-Description: [Imap-protocol] [noob] body[n.header]  
vs.\r\n body[n.mime]?\r\n\r\n"

On the other hand, BODY[2.HEADER] will be your message's header (as  
it exists as BODY[HEADER] in the original message I forwarded from my  
INBOX).

For reference's sake, BODY[2.1] is your original message text,  
whereas this text is BODY[1].

And to complete the example, a FETCH of UID, MODSEQ, ENVELOPE, and  
BODYSTRUCTURE from a draft of this message (ie, the text size of this  
section will have changed) reads:

* 55 FETCH (FLAGS (\\Recent \\Draft \\Seen $MDNSent) UID 55 MODSEQ  
(33) ENVELOPE ("Wed, 21 Dec 2011 12:12:30 +0000" "Re: [Imap-protocol]  
[noob] body[n.header] vs. body[n.mime]?" (("Dave Cridland" NIL "dave"  
"cridland.net")) (("Dave Cridland" NIL "dave" "cridland.net"))  
(("Dave Cridland" NIL "dave" "cridland.net")) (("Petite Abeille" NIL  
"petite_abeille" "mac.com")("IMAP Protocol Interest List" NIL  
"IMAP-Protocol" "u.washington.edu")) NIL NIL  
"<7A5C9702-B74C-4AA7-9075-449D07B0435B@mac.com>"  
"<3461.1324469550.264077@puncture>") BODYSTRUCTURE (("TEXT" "PLAIN"  
("DELSP" "yes" "CHARSET" "us-ascii" "FORMAT" "flowed") NIL NIL "7BIT"  
530 15 NIL NIL NIL)("MESSAGE" "RFC822" NIL NIL "[Imap-protocol]  
[noob] body[n.header] vs. body[n.mime]?" "7BIT" 6661 ("Wed, 21 Dec  
2011 13:05:23 +0100" "[Imap-protocol] [noob] body[n.header] vs.  
body[n.mime]?" (("Petite Abeille" NIL "petite_abeille" "mac.com"))  
((NIL NIL "imap-protocol-bounces" "mailman2.u.washington.edu"))  
(("Petite Abeille" NIL "petite_abeille" "mac.com")) (("IMAP Protocol  
Interest List" NIL "IMAP-Protocol" "u.washington.edu")) NIL NIL NIL  
"<7A5C9702-B74C-4AA7-9075-449D07B0435B@mac.com>") ("TEXT" "PLAIN"  
("CHARSET" "US-ASCII") NIL NIL "7BIT" 885 33 NIL NIL NIL) 119 NIL  
("INLINE" NIL) NIL) "MIXED" ("BOUNDARY"  
"3461.1324469550.264010@puncture") NIL NIL))\r\n'

Does that help clarify?

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
-------------- next part --------------
An embedded message was scrubbed...
From: Petite Abeille <petite_abeille@mac.com>
Subject: [Imap-protocol] [noob] body[n.header] vs. body[n.mime]?
Date: Wed, 21 Dec 2011 13:05:23 +0100
Size: 6589
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20111221/3a30aaa4/attachment.mht>
Reply