1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
|
- Other than multipart/mixed and PGP/MIME, Mutt should allow the user to
specify what to do with other types of multipart messages (i.e., so a user
can deal with S/MIME messages reasonably)
- option to not include attachments in replies
- handle message/external-body in some fashion
- handle message/partial reconstruction
- not possible to view the header of a single part message which contains
something that requires a mailcap entry to view
- need to clean up the error recovery when running out of space when syncing
a mbox/mmdf mailbox
- BODY struct should probably have a pointer to its corresponding HEADER
struct. this is needed for mh/maildir mailboxes so the correct pathname
can be found. Or perhaps all we need is a .hdr member of the STATE struct
so that all of the MIME handlers can look up the corresponding HEADERs if
need be?
- imap debugging
- add special check for maildir->maildir copy so the file can just be
renamed. hmm, this might not work if moving across filesystems. at the
very least the original filename should be used for the copy
- mailbox resync code for mh and maildir mailboxes
- limit by message size ?
- command to describe binding of an individual key
- fold long user-defined header fields
- history classes
- now that the limit pattern can be evaluated per message, newly delivered
messages can be classified without undoing the current limit
- document honored environment variables
- add -v flag to pass to sendmail... will this work with the sendmail
backgrouding?
- ordered tag
- honor ^L in the pager
- rfc822 parser needs to do something with the @host1@host2: portion of the
route-addr
- command completion for `enter-command'
- new forward command to include first attachment in the editor and attach
other attachments to the message
- honor `my_hdr Subject: foo' to get the default subject
- adjust the names of *adr() and *adrlist() and calling routines for
consistency
- not possible to use function keys in macros. perhaps using [...] for
function keys is a solution (example: macro index Y "[pageup][down]\n")
- using $mime_fwd to forward a message with nested message/rfc822 parts
doesn't work
- my_hdr disables use of $reverse_name
- option for using `lists' to determine default save name?
- mbox-hook entries should override $move
- remove use of -t on $sendmail and always pass recips on command line?
- generic string formatter to consolidate common code?
|