I've posted a few messages, and so have others, regarding setting
up a popd server on DEC OSF/1. I received this helpful 'how to'
from the DEC Customer Support folks, so I though I'd pass it along...
(hope I'm not breaking any rules or anything, but they DID sanitize
it first!)
---------------------------
Setting Up the POP server
-------------------------
1. create a group called 'pop' in /etc/group file, like this:
pop:*:30:pop,pop-user1,pop-user2
where 30 is the group ID. This ID must be unique in this file. If 30 is
being used, then choose another number.
Then add in all those POP users to this group, including 'pop' (this is for
step 2).
2. create an account called 'pop' with /usr/spool/pop as the home
directory, by editing the /etc/passwd file, and add this entry:
pop:*:57:30:MH POP:/usr/spool/pop:/:
where 57 is the user ID. This ID must be unique in this file. If 57 is
being used, then choose another number. 30 is the group ID for group 'pop'
set up in step 1.
3. create the /usr/spool/pop directory owned by 'pop'.
# cd /usr/spool
# mkdir pop
# chown pop pop
# chgrp pop pop
# chmod 777 pop
4. create a file in the /usr/spool/pop directory called POP owned by 'pop'.
Add an entry into the POP file in the following format for every user
who will use the POP server:
user::user:::::::0
# cd /usr/spool/pop
# vi POP
add in entry as shown above.
# chown pop POP
# chgrp pop POP
# chmod 666 POP
5. run /usr/lib/mh/popaka to obtain aliases for all of the users in
the POP file.
NOTE: An apparent bug in popaka causes it to look for the POP database
in the /usr/spool/pop/pop directory. To work around the bug, make
the /usr/spool/pop/pop directory and create a symbolic link in it
for POP pointing back to the POP file in the /usr/spool/pop directory.
# cd /usr/spool/pop
# mkdir pop
# chown pop pop
# chgrp pop pop
# chmod 777 pop
# cd pop
# ln -s ../POP
# /usr/lib/mh/popaka
6. enter the strings produced from running 'popaka' in the systemwide
alias file, /usr/adm/sendmail/aliases on OSF/1 or /etc/aliases on ULTRIX.
7. run 'newaliases' to update the mail aliases database.
# /etc/newaliases <on ULTRIX>
or
# /usr/sbin/newaliases <on OSF/1>
8. use 'popwrd' to enter a password for each POP user.
# /usr/lib/mh/popwrd pop-user1
9. make sure that 'pop' is the owner of /usr/lib/mh/spop with a mask
of 'rwsr-xr-x'.
# chown pop /usr/lib/mh/spop
# chmod 4755 /usr/lib/mh/spop
10. make sure the port name 'pop' is in /etc/services file.
pop 109/tcp postoffice
NOTE: if you make change to this file, don't forget to kill the
'inetd' and restart it again, like this:
# kill -9 inetd-pid
# /etc/inetd & <on ULTRIX>
or
# /usr/sbin/inetd & <on OSF/1>
11. run 'popd' in the background and redirect its output to a null file:
# /usr/lib/mh/popd -p 110 >& /dev/null &
NOTE: popd on ULTRIX & OSF/1 are based on pop3 protocol, by default its
using port 109. If the pop application is looking for port 110, then
use the '-p' option as shown above to indicate the port number.
If you are running in a Network Information Service (NIS) environmnet,
you must perform the following steps to enable users on client machines
to reply or send mail so that the return address will be correctly sent
to the POP server machine:
1. YP aliases for the POP user should point to the POP server machine.
2. Run quick 'mailsetup' (OSF/1 only, /usr/sbin/mailsetup)
or modify the send mail configuration file
(/usr/var/adm/sendmail/sendmail.cf on OSF/1 or /usr/lib/sendmail.cf on
ULTRIX) to specify the POP serve machine.
3. Check the /etc/svc.conf to make certain the 'local', yp' aliases are
there. If they are not there, add them.
Where POP mail reside?
OSF/1: they reside at /usr/spool/pop directory with pop-user as the file name,
with owner & group both 'pop'.
ULTRIX: at /usr/spool/mail directory (regular UNIX mail).
NOTE: i have seen the pop DELE function (delete mail) looks for the
pop mail at /usr/spool/pop. to get around with this problem,
make a soft link
ln -s /usr/spool/mail/login-name /usr/spool/pop/pop-user
Some users have asked, "How can my regular mh/sendmail users access mail
from the POP server?". Note that mh does not (by default) look in POP's
spooled area. To get mh to incorporate mail from POP's spooled area, you
must use some flags. 'inc -help' will list some flags and options for inc,
as will the appendix from "MH & xmh" published by O'Reilly & Associates.
This is from "MH & xmh" published by O'Reilly & Associates:
"Just as msgchk works across the network to a mail server
which runs POP, so does inc. It takes the same switches as
msgchk. You'll usually want to put the switches in your
MH profile. Of course, 'inc -rpop' and 'inc -norpop' drop
mail into your folder on the host where you run inc, not on
the mail server host.
Here's an example of a user, logged onto the local host as
ehuser, who brings mail from the mailbox for rschproj on the \]
remote server mailsrvr.cmp.xyz.edu:
%/usr/bin/mh/inc -norpop -host mailsrvr.cmp.xyz.edu
Name (mailsrvr.cmp.xyz.edu): rschproj
Password (mailsrvr.cmp.xyz.edu):
Incorporating new mail into inbox...
"
Here are the appropriate flags for inc:
-host <host> POP server host
-user <user> Username on POP server host
-pack <file> Write all messages to <file> instead of splitting
into folder
-nopack Put POP'd messages into folder
-rpop User authentification via trusted connection
-norpop Prompt for user's POP server host password
--
-----------------------------------------------------------------
| Mike Godsey mgodsey_at_medio.com |
| Medio Multimedia, Inc. |
| Redmond, WA |
| <A HREF="http://www.Medio.Net/users/mgodsey">Mike Godsey </A> |
-----------------------------------------------------------------
Received on Thu Feb 09 1995 - 19:13:25 NZDT