User Tools

Site Tools

Trace:
configuration_changes_needed_when_using_maildir

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
configuration_changes_needed_when_using_maildir [2021/03/11 02:43] – created hc9configuration_changes_needed_when_using_maildir [2024/09/02 23:15] (current) – ' hc9
Line 1: Line 1:
-==== Configuration Changes Needed When Using Maildir ====+====== Configuration Changes Needed When Using Maildir ======
  
-If you forward your mail from the SDF cluster using a forward as described in the [[http://sdf.org/?tutorials/metaarray|MetaArray]] tutorial, you may have to update your mail client's configuration, as mbox format is used there. If you use procmail, for example, .procmailrc configuration will be slightly different. Lockfiles are not needed in recipes (the trailing ':' after the zero), and directories are used as destinations for mail. Some of the environment variables are different, as well:+If you forward your mail from the SDF cluster using a forward as described in the [[http://sdf.org/?tutorials/metaarray |MetaArray]] tutorial, you may have to update your mail client's configuration, as mbox format is used there. If you use procmail, for example, .procmailrc configuration will be slightly different. Lockfiles are not needed in recipes (the trailing ‘:’ after the zero), and directories are used as destinations for mail. Some of the environment variables are different, as well:
  
 <file config environment variables> <file config environment variables>
Line 14: Line 14:
 </file> </file>
  
-The above will send all mail by default to the directory '~/Maildir/.inbox' (just replace USERNAME with your own user name and LETTER with the first letter of your user name).+The above will send all mail by default to the directory ‘''~/Maildir/.inbox''’ (just replace USERNAME with your own user name and LETTER with the first letter of your user name).
  
 Here is a .forward that works with procmail on the MetaArray: Here is a .forward that works with procmail on the MetaArray:
Line 24: Line 24:
 Again, replace USERNAME as appropriate. Again, replace USERNAME as appropriate.
  
-If you use mutt, your .muttrc will need to be updated. Here is a minimal maildir config you can incorporate into an existing .muttrc. Note the two 'set spoolfile' lines - the commented one will tell mutt to pull from your system mail spool, however the next, uncommented one that references the '.inbox/' directory will work with the .procmailrc snippet, above. The '.Sent' and '.Drafts' folders are just standard folder names that are compatible with most IMAP implementations, but if you don't use IMAP they can be named anything.+If you use mutt, your .muttrc will need to be updated. Here is a minimal maildir config you can incorporate into an existing .muttrc. Note the two ‘''set spoolfile''’ lines - the commented one will tell mutt to pull from your system mail spool, however the next, uncommented one that references the ‘.inbox/’ directory will work with the .procmailrc snippet, above. The ‘.Sent’ and ‘.Drafts’ folders are just standard folder names that are compatible with most IMAP implementations, but if you don't use IMAP they can be named anything.
  
 <file config .muttrc/snippet> <file config .muttrc/snippet>
Line 46: Line 46:
 The changes to the mailboxes command and c/C/M macros allow mutt to work with maildir folders, even if the folder names change at some point. The changes to the mailboxes command and c/C/M macros allow mutt to work with maildir folders, even if the folder names change at some point.
  
-==== Converting Mbox to Maildir ====+===== Converting Mbox to Maildir =====
  
-If you want to convert your existing mbox-style mailboxes to maildir format, you can use 'mbox2maildir' to do so. The syntax for using it is as follows:+If you want to convert your existing mbox-style mailboxes to maildir format, you can use ‘''mbox2maildir''’ to do so. The syntax for using it is as follows:
  
 ''mbox2maildir [//mbox file//] [//maildir directory//]'' ''mbox2maildir [//mbox file//] [//maildir directory//]''
Line 78: Line 78:
 </code> </code>
  
-You can see that mbox2maildir has converted each message in the mbox file to its own file and placed each in the maildir-standard 'cur' sub-directory.+You can see that mbox2maildir has converted each message in the mbox file to its own file and placed each in the maildir-standard ‘cur’ sub-directory.
  
-==== Converting Maildir to Mbox ====+===== Converting Maildir to Mbox =====
  
-As you might guess, converting maildir-format folders to mbox is done by the 'maildir2mbox' utility. It operates using environment variables, not command line options, so to be clear it might be best to specify them with the command:+As you might guess, converting maildir-format folders to mbox is done by the ‘maildir2mbox’ utility. It operates using environment variables, not command line options, so to be clear it might be best to specify them with the command:
  
 <code> <code>
Line 96: Line 96:
 </code> </code>
  
-$Id: maildir.html,v 1.5 2019/07/23 01:30:22 slugmax Exp $ [[http://sdf.org/?tutorials/maildir|Configuration Changes Needed When Using Maildir]] - legacy link +$Id: maildir.html,v 1.5 2019/07/23 01:30:22 slugmax Exp $ [[http://sdf.org/?tutorials/maildir|Configuration Changes Needed When Using Maildir]] - traditional link (using [[wp>Revision_Control_System|RCS]])
  
configuration_changes_needed_when_using_maildir.1615430588.txt.gz · Last modified: 2021/03/11 02:43 by hc9