This example should help carify the syntax of the settings defined in the
previous section, with a set of artificial data.
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:
user-domain=foofoo.org
smtp-server=192.168.1.25
inbox-path={192.168.1.25/user=${USER}}INBOX
folder-collections="INBOX Folders" {192.168.1.25/user=${USER}}inbox/[],
"Mailbox Folders" {192.168.1.25/user=${USER}}[]
default-fcc="{192.168.1.25/user=${USER}}Sent Items"
postponed-folder={192.168.1.25/user=${USER}}Drafts
#customized-hdrs=From: Foo Foo <foofoo@foofoo.org>
ldap-servers=192.168.1.100 "/base=/impl=1/rhs=0/ref=0/nosub=0/type=
/srch=contains/time=/size=/cust=/nick=/matr=/catr=/satr=/gatr="
rsh-open-timeout=0 |
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.
Using the default configuration provided in this example, when you compose a
new message, and type in a name in the "To:" box. Pine will first check your
local addressbook for the nickname. If it doesn't find it, it will then run an
LDAP query by default, using the default name you typed as the search string.
Depending on the speed of the LDAP server, you should get a response
relatively quickly. From the results you can choose the entry you were looking
for, and continue writing your email.
NOTE: If you type in an email address in the "To:" box, it will NOT do an LDAP
search or any other addressbook search (ie. user@smtp.email.org).
If you just want to do a search, without actually composing a new message, you
can go directly to your addressbook, select the LDAP server, and type the
search string from there (ie (M)ain, (A)ddressbook).
In case you do not want Pine to do an automatic LDAP lookup everytime you
compose a new message, you can change the parameter "/impl=1" in the
"ldap-server" setting to "/impl=0". This will allow you to do a manual LDAP
query if you wish.