This shows you the differences between two versions of the page.
— | howtos:pine [2008/02/08 19:49] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Configure Pine for POPFile ====== | ||
+ | |||
+ | ===== Mail Configuration ===== | ||
+ | |||
+ | This is for version 4.44 of the Pine client. It should be basically the same for any recent version. | ||
+ | |||
+ | * install and configure POPFile and create your buckets. | ||
+ | |||
+ | * Change the Separator Character (2nd item in configuration) to something other than a colon. I chose _ (an underscore), | ||
+ | |||
+ | * Because pine can filter on a header, you can set ' | ||
+ | |||
+ | * Open up your pinerc file in an editor and find the ' | ||
+ | " | ||
+ | |||
+ | * Replace user and host as per the standard POPFile documentation. If you didn't use underscore as your separator, change that appropriately as well. Save it and restart pine. | ||
+ | |||
+ | * This will create a new inbox folder named " | ||
+ | |||
+ | |||
+ | ===== Mail Filters Configuration ===== | ||
+ | |||
+ | * From the pine main menu, go to Setup&# | ||
+ | |||
+ | * Type ' | ||
+ | |||
+ | * Change the nickname to ' | ||
+ | |||
+ | * Leave the Folder Type at ' | ||
+ | |||
+ | * Move the cursor down to one of the preset patterns (doesn' | ||
+ | |||
+ | * Enter the name of your POPFile bucket as the value. | ||
+ | |||
+ | * Move to the Filter Action area. Leave the selection at ' | ||
+ | |||
+ | * Move down to the end of the options to the move-only-if-not-deleted option and hit enter to set it to true. | ||
+ | |||
+ | * ' | ||
+ | |||
+ | * Repeat steps for each POPFile bucket. | ||
+ | |||
+ | * Enter ' | ||
+ | |||
+ | * If you hit ' | ||
+ | |||
+ | That should be it. As you train POPFile, Pine will filter your mail whenever you open | ||
+ | the POPFILE folder. | ||
+ | |||
+ | |||
+ | **Note:** For those folders that you want to filter to but you don't want to navigate through by default (I have ' | ||
Should you find anything in the documentation that is incomplete, unclear, outdated or just plain wrong, please let us know and leave a note in the Documentation Forum.