Changes between Version 4 and Version 5 of MuttFaq/Folder


Ignore:
Timestamp:
Nov 1, 2013 9:58:44 AM (4 years ago)
Author:
MichaelRay
Comment:

Adding for offsets, however this might simply be making the original sketchy spacing/indenting more prominent and may need further revision. Minor grammar/style/spacing.

Legend:

Unmodified
Added
Removed
Modified
  • MuttFaq/Folder

    v4 v5  
    22In mbox-format this means the folder you are about to access doesn't conform to the RFC2822 specification.
    33Either it really is not meant to be a mailbox, or the folder has been corrupted.
    4 Typical corruption is incorrect 1st line, which should look like this.
    5  From user@adr date
    6 (note no ":" after "From") or missing empty line between header & body (empty == not even blanks, absolutely no char).
     4Typical corruption is incorrect 1st line, which should look like this:
     5
     6{{{
     7 From user@domain date
     8}}}
     9
     10(note the missing ":" after "From") or missing empty line between header & body (empty == not even blanks, absolutely no characters).
    711
    812For maildir-format this typically results from missing required subdirs.
    913See FolderFormat for how they should be setup correctly!
    1014
    11 Some people mistakingly create folders of one format (for example by procmail) and try to use some other format in mutt.
     15Some people mistakenly create folders of one format (for example by procmail) and try to use some other format in mutt.
    1216Example:
    1317 * bad procmail-config: creating regular flat-file mbox instead of maildir, the trailing "/" makes the difference, "man procmailrc"!!!
     
    2125 * '''getmail''': it is likely you do not have the unixfrom variable set in your getmailrc.
    2226  * In ~/.getmail/getmailrc under [destination] set unixfrom to yes; e.g.,
    23  [destination]
     27 
     28{{{
     29[destination]
    2430 type = MDA_external
    2531 path = /usr/bin/procmail
    2632 unixfrom = yes
    27 
    28 You can ''add missing'' '''"From "''' lines of already delivered eMails by means of piping them through formail like
     33}}}
     34
     35You can ''add missing'' '''"From "''' lines of already delivered emails by means of piping them through formail like
    2936 cat mailbox | formail -b > new_mailbox
    3037Depending on how broken the mailbox is, may or may not work. In doubt add 'From ' lines manually.
     
    3946
    4047=== Why are "new" flags of mbox folders wrong in folder-list view? ===
    41 As written in [[MuttWiki|manual.txt]], the flags are determined by
     48
     49As indicated in the [[MuttWiki|manual.txt]], flags are determined by
    4250comparing the timestamps of last access and modification. This can get messed up
    4351if the folders are "touched" by other programs than mutt, like "biff" or backup software.
     
    5462
    5563=== How to make mutt open a specific folder on startup? ===
     64
    5665For casual use consider
     66{{{
    5767 mutt -f path/folder
     68}}}
    5869To do it every time rtfm
     70{{{
    5971 $spoolfile
     72}}}
    6073Note for both: '''$folder''' can help you shorten the paths you have to specify,
    6174and lookout for the many other useful [[MuttGuide/Folders|folder shortcuts]].
    6275
    6376=== How to save copies of outgoing/sent eMails? ===
     77
    6478RTFM '''$copy, $record''' for more. By default NONE is saved anywhere,
    6579make sure you set them before you need them.
    6680
    6781=== How to save copies of outgoing/sent eMails to the current folder? ===
     82
    6883You need the current_shortcut patch (see PatchList).
    6984With that patch, "^" points to the current folder.
     
    7489
    7590=== I can't modify my inbox folder, Mutt claims it's read-only, but permissions are ok? ===
     91
    7692Often this happens due to locking problems. To manipulate folders
    7793the access has to be exclusive to avoid corruptions by concurrent
     
    7995the folder causing trouble the permissions are disallowing write
    8096access or that your
     97{{{
    8198 $mutt_dotlock
     99}}}
    82100either doesn't point to a suitable filelock-program, or the
    83101permissons for the lock-programm are not correct. Normally it
    84102should look like this:
     103{{{
    85104               user    group     filename
    86105 -r-xr-sr-x    bin      mail     mutt_dotlock
    87106 drwxrws--x    root     mail     /var/mail
     107}}}
    88108The important bit is that mutt_dotlock's group must match
    89109/var/mail's, and mutt_dotlock's sgid-bit is set. Only the admin
    90110can
    91  chgrp mail mutt_dotlock; chmod g+s mutt_dotlock
     111{{{
     112 $ sudo chgrp mail mutt_dotlock; sudo chmod g+s mutt_dotlock
     113}}}
    92114If it's not your own system, ask the sysadmins to install mutt_dotlock
    93115correctly.
     
    95117Alternatively you can try to use MaildirFormat (remember to have the
    96118[[MailConcept|MDA as well as the MUA]] use the same
    97 format). It has no locking issues, but the individual msgs are
    98 organized differently than classical
    99 [[FolderFormat|MBOX-format]].
     119format). It has no locking issues, but the individual messages are
     120organized differently than classical [[FolderFormat|MBOX-format]].
    100121
    101122=== How to make mutt check for new mail more often?[[BR]]    What's the difference between $timeout and $mail_check? ===
     123
    102124After every keyboard input mutt updates the status of all folders.
    103125To receive "New mail in ..." notifications even without needing to press a key,
     
    114136
    115137=== How to get informed about new mail? ===
     138
    116139When new mail arrives, an automatic (no key pressed) "New mail in ..."
    117140notification is shown at the screen bottom.  This happens '''only''' in the
     
    124147
    125148=== Stop asking to "move read messages to mbox"! ===
     149
    126150RTFM "move", i.e. "'''set move=no'''"
    127151
    128152=== How to create new folders? ===
     153
    129154Just copy or save (see /Action) to the folder you want. If it
    130155doesn't exist, mutt will create it for you with the FolderFormat
     
    132157
    133158=== How to use the "trash" folder? ===
     159
    134160Mutt doesn't provide a "trash" system by itself. A reason might be that people forget to purge it from time to time.
    135161Anyway, if you really want to use such a thing, there exist MacroSamples.
    136162There is also a trash folder patch (see PatchList), here's an example setup that automatically selects different
    137163trash and record folders depending on the current mailbox (the ^ is from the current_shortcut patch):
     164{{{
    138165 folder-hook .         'set record="!" trash="=trash/trash"'
    139166 folder-hook IN/.      'set record="^" trash="^.trash"'
    140167 folder-hook \.trash$  'unset trash'
    141 
     168}}}
    142169=== How to import messages from pine, thunderbird, kmail, evilution, ...? ===
    143 mutt understands some standard FolderFormat""s. Find out what format the other
     170
     171Mutt understands some standard FolderFormat""s. Find out what format the other
    144172MUA uses, and when it's compatible, just copy them over to a place for
    145173mutt to find them (and configure it per MuttGuide/Folders). If it's a proprietary
     
    149177
    150178=== I left off a trailing '/' in my .procmailrc, and procmail delivered[[BR]] many emails to a Maildir folder in MH format. How do I fix this? ===
     179
    151180Install the '''nmh''' program on your system, e.g. via your system's package manager.
    152181
    153182Then set up $HOME/.mh_profile as follows:
    154 
     183{{{
    155184 Path:                $HOME/$MAIL
    156185 Inbox:               $HOME/$INBOX
    157186 Unseen-Sequence:     unseen
    158 
     187}}}
    159188where
    160189
     
    166195
    167196Change to the directory which contains the MH messages you want to be able to view, and type the following on the command line, assuming the '''bash''' shell:
    168 
     197{{{
    169198 for msg in *; do cat $msg | $RCVSTOREPATH/rcvstore -unseen; done
    170 
     199}}}
    171200where '''$RCVSTORE''' is the location of the '''rcvstore''' program (perhaps '''/usr/lib/nmh/''').
    172201
     
    174203
    175204=== What's the difference between '+' and '='? ===
     205
    176206Technically NONE, it's just for convenience not to need SHIFT to type it depending on keyboard layout (DE, EN).
    177207