New answers tagged mutt
Maildir store some data in the message filename. That data include message ID, sizes (with and w/o newlines) and flags. When unread message is opened, it is moved from new to cur and its name changes from 1406379300.M375059P35208.R93M.lan,S=679,W=699 to 1406379300.M375059P35208.R93M.lan,S=679,W=699:2,S IMAP server can track that changes cause it use ...
Use the following pattern: ~(~N). More generally: ~(PATTERN) messages in threads containing messages matching PATTERN, e.g. all threads containing messages from you: ~(~P) Note: you need to take Mutt 1.5.x (versions 1.4.x are really obsolete), even though declared as "development versions". And here's the part of the corresponding manual on patterns.
AFAIK, Mutt itself cannot do such checks, but there's a workaround! The idea is to redefine the $sendmail variable to use a wrapper that will check the mail before sending it. For instance, in your .muttrc file: set sendmail=$HOME/scripts/sendmail-mutt This script can either terminate with an error (non-zero exit status) or terminate successfully with ...
The common way to see your own messages in the threaded display, which makes sense, is done by sending a BCC to you. I use my_hdr Bcc: firstname.lastname@example.org and it works great.
In short, the "problem" arises from the fact that, IMAP4 encodes folder names using a modified UTF-7 coding. offlineimap does not convert folder names to something readable before creating local repositories (e.g. in UTF-8). This, in turn, derives unreadable folder names like the ones shown in the screenshot of this question. Hence, it's neither Mutt's nor ...
A simple example: Suppose you want to delete and purge messages from the testmbox mailbox, containing [DELETE-ME] in the subject line. You can do this: mutt -f testmbox -e "push <tag-pattern>~s[DELETE-ME]\n<tag-prefix><delete-message><sync-mailbox>\n" This works because: -e executes configuration commands 'push' is a ...
Top 50 recent answers are included