~V [MIN]-[MAX]
See the Mutt manual
(section 4.2, Patterns)
if you don't understand what that means.
Additionally, since different user agents (and different users)
do attachments differently, it provides three variables which
help mutt to decide what exactly it should consider an
attachment:
attach_count_containers_ok
- If set, Mutt's attachment counter will consider
MIME components which contain other components
(e.g., multipart/* and message/*) as attachments.
attach_count_inline_ok
- If set, Mutt's attachment counter will consider
MIME components with a disposition of "inline" as
attachments.
attach_count_recurse
- If set, Mutt's attachment counter will examine
message/* components for attachments.
The default is to recurse containers, but not to count
containers themselves, and not to count attachments marked
as inline.
The attachments patch tries hard to conserve memory. Messages
are scanned for attachments when they're parsed for the index
or during a search. When a mesasge leaves view, the attachment
information is thrown away. It's not slow, though, and it
doesn't waste memory.
There is a bug in attach.2 relating to deletion
of attachments within messages. (They won't be deleted upon
folder synchronizaion.) This is fixed in attach.3.
Thanks to David Ellement for noting this and testing the revised
patch.