On Mon, 2003-11-24 at 22:10, Mark Crispin wrote: > > Well, one possibly useful field would be References header in > > message/rfc822 body parts. > > That's not a BODYSTRUCTURE issue; it is an ENVELOPE issue.
FETCH ENVELOPE can be easily worked around with FETCH[HEADER.FIELDS (whatever you want)]. Fetching more headers for message/rfc822 body parts isn't possible without a BODY/BODYSTRUCTURE first and then sending a separate FETCH BODY.PEEK[n.HEADER.FIELDS (more)] request for each body part. Well, another way to look at it: What if the fields returned in ENVELOPE (and embedded ENVELOPEs in BODYSTRUCTURE) were configurable by client for the current session? SET-ENVELOPE ((From addrlist) (To addrlist) Subject) vs. SET-ENVELOPE (From To Subject) "addrlist" meaning that header contains RFC2822 address-list and should be returned as a parsed list rather than string. The list could contain any headers the client would want. Default is of course RFC3501 ones.
signature.asc
Description: This is a digitally signed message part
