Just a thought - anyone else interested about this? Paperclip icon indicating attachment can be pretty useful and many clients want it, but figuring out if it should be put there requires fetching BODY or the whole message. So how about giving client a few hints about that?
FETCH .. (FLAGS (ATTACHMENT)) MAY return \NoAttachment in FLAGS list if there's definitely no attachment in the message and \Attachment if there's definitely an attachment in the message. If neither is returned, client MUST NOT assume either. Rules for definite no: - There's no Content-Type - Content-Type is text/* - (Multipart message doesn't contain Content-Disposition: attachment)? Rules for definite yes: - There's Content-Disposition: attachment in message header or one of the multipart headers - (Content-Type is multipart/mixed)? I'm not sure if the rules in parenthesis are enough. Server SHOULD always check the main Content-Type rules to avoid client issuing FETCH BODY for all the messages. Rules requiring MIME parsing may be expensive and probably shouldn't be done just to get the attachment flag. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html -----------------------------------------------------------------
