HOWTO: POPFile with Pine

HOWTO
2003-02-04
2004-09-13
  • Joshua Yockey

    Joshua Yockey - 2003-02-04

    Yes, some of us still use Pine.

    This is for version 4.44 of the Pine client.  It should be basically the same for any recent version.

    Stage One, Getting it to connect:

    1) install and configure POPFile and create your buckets.

    2) Change the Separator Character (2nd item in configuration) to something other
    than a colon.  I chose _ (an underscore), which isn't in my remote username.  If
    you have one, try dash.  If you have both, you'll have to experiment.

    3) Because pine can filter on a header, you can set 'Subject Modification' on
    your buckets to 'Off'.

    4) Open up your pinerc file in an editor and find the 'incoming-folders' field. 
    Set it to (or add, if you already have one):

    "POPFILE" {127.0.0.1/pop3/user=<user>_<host>}INBOX

    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 "POPFILE" that will retrieve your email.

    Stage Two, Filtering:

    1) From the pine main menu, go to Setup/Rules.  At the Type of Rule prompt, hit
    'F' for filters.

    2) Type 'A' to add a filter.

    3) Change the nickname to 'POPFile-<bucket name>' or whatever makes you comfortable.

    4) Leave the Folder Type at 'Specific' but change the Folder List value to be
    'POPFILE' (or whatever you named the inbox folder to be in your pinerc file)

    5) Move the cursor down to one of the preset patterns (doesn't matter which) and
    type 'X' to add an extended header.  At the name prompt enter 'X-Text-Classification'.
    Enter the name of your POPFile bucket as the value.

    6) Move to the Filter Action area.  Leave the selection at 'Move' but change the
    Folder List value to be the bucket name (eg 'Folder List = spam')

    7) Move down to the end of the options to the move-only-if-not-deleted option and hit
    enter to set it to true.

    8) 'E' to Exit the filter setup.  You'll be prompted to create the new folder (if it's
    new) and add it to the Incoming folders.  Reply yes to both.  Set the nickname to be
    the bucket name (or whatever you like).

    9) Repeat steaps 2-8 for each POPFile bucket.

    10) Enter 'E' to exit setup.  Reply Yes to commiting changes.

    11) If you hit 'L' from the main menu to list folders and go to Incoming Folders you
    should now see your POPFile folder as well as a folder for each of your buckets.

    That should be it.  As you train POPFile, Pine will filter your mail whenever you open
    the POPFILE folder.

     
    • Joshua Yockey

      Joshua Yockey - 2003-02-04

      Adjustment:  For those folders that you want to filter to but you don't want to navigate through by default (I have 'spam' and 'virus'), create the folder, but don't add it to Incoming folders.  If you already have, you can edit the list in your pinerc file.  This lets you tab through the folders you actually want to read, and go to the bad folders through the Local Folders interface.

       
    • Anonymous - 2004-09-13

      I've followed the documentation to configure Pine but still can't seem to get it working.

      Here's how my config in Pine looks:

      (host.name & loginid are naturally replaced with the actual names, and the ":" has been changed to "_" in the POPFile configuration).

      personal-name                 = Abbas Jaffary
      user-id                       = host.name.com_loginid
      user-domain                   = 127.0.0.1
      smtp-server                   = smtp.host.name.com
      nntp-server                   = <No Value Set>
      inbox-path                    = {host.name.com}INBOX
      incoming-archive-folders      = "POPFILE" {127.0.0.1/pop3/user=loginid_host.name.com}INBOX

      I originally had the

      {127.0.0.1/pop3/user=loginid_host.name.com}INBOX

      line under "inbox path", but that did not work. 

      I then edited the "incoming archive folders" line under pinerc and left the "inbox path" the way it was.  With those settings, Pine acts normally but will not log in with the "host.name.com_loginid" string.  I have to log in normally, and this seems to bypass POPFile entirely.

      Thank you.

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks