Linuxdoc Linux Questions
Click here to ask our community of linux experts!
Custom Search

6. Example Configuration

This example should help carify the syntax of the settings defined in the previous section, with a set of artificial data.

6.1. Gather your information

Let us assume the following default information (You may provide your own if you have it available):

  Printed Name = "Foo Foo"
  Account/User Name = "foofoo"
  Domain Name = ""
  Exchange/IMAP/LDAP Server = ""

NOTE: In order for the transition to be seamless, you have to make sure you match the information precisely as it is stored on the Exchange Server. (ie if your name on the Exchange server is "John B. Doe", make sure you set your printed name to the exact value)

Let us also assume, you have been using Outlook up to this point, and you have accumulated some messages in your "INBOX", "Sent Items", and "Drafts". Not too mention a couple of personal folders you created in your "INBOX" on the server to categorize your mail: "TODO", "DONE", and "Personal".

6.2. Setting up a local ~/.pinerc configuration file

Here are the settings you should find in your ~/.pinerc file. In most cases, each setting will be empty (ie "key=" with no value specified). Here is what they would look like plugging in the default information.
  folder-collections="INBOX Folders" {}inbox/[],
                     "Mailbox Folders" {}[]
  default-fcc="{}Sent Items"
  customized-hdrs=From: Foo Foo <>
  ldap-servers= "/base=/impl=1/rhs=0/ref=0/nosub=0/type=

NOTE: If you want to try SMTP Authentication with the above configuration, you would replace:


6.3. Setting up a site-wide Pine configuration

This configuration affects all the users on the system and requires a bit more work to setup. Only a UNIX SysAdmin should attempt this configuration.

NOTE: In order for this configuration to work properly, the Microsoft domain account information must be synced up with the Unix account information (ie. usernames and full names must match).

Looking at the default provided information you should notice that "Printed Name", and "Account/User Name" now have to be generalized. For "Printed Name", in removing it from the configuration file, Pine will default to the personal name found in the /etc/passwd file. For "Account/User Name", you can use "${USER}", which points to the environment variable which holds the users login name. So with that you get the following configuration:
  folder-collections="INBOX Folders" {${USER}}inbox/[],
                     "Mailbox Folders" {${USER}}[]
  default-fcc="{${USER}}Sent Items"
  #customized-hdrs=From: Foo Foo <>
  ldap-servers= "/base=/impl=1/rhs=0/ref=0/nosub=0/type=

NOTE: In this configuration we want to comment out the "customized-hdrs" setting since we want the user information to be retrieved from the system /etc/passwd file.

The last step in this configuration is determining whether to put the settings in /etc/pine.conf or /etc/pine.conf.fixed. That choice is yours, and depends on how much control you need to give to the users. If your company only uses Exchange, maybe all the settings should go in fixed, but then users couldn't use Pine for anything else. Remember, if you put a setting in pine.conf.fixed, the user does not have the option to change it.