A few days ago I asked a question regarding the configuration of the POP server
on our Alpha.
Replies to date were received from:
Michel Cyr
Chris Davies
Steve Swinnea
Simon Greaves
Cardell
Mike Godsey - forwarded from Cardell
Matt Harrington
Jim Wright
Stuart Bishop
Jean-Loup Risler
Richard Rogers
Sorry if I missed anyone - all replies appended at end in full
Most said don't use the DEC out of the box POP server get pop3d - available from
various sites. Various implentations were mentioned from:
hubcap.clemson.edu
Qualcomms pop3 server from ftp.qualcomm.com - now called popper
berkley - possibly same as rmit below?
ftp.bf.rmit.edu.au/pub/src/pop3d (a simple one).
There are already some details in the archive about setting up pop - so I was
told.
The basic mistake I was making was not having a pop user whose home directory is
where the pop database resides.
I got the clemson version and the one from rmit. Both compiled first time and
once I'd figured out the PC client the one I tried first (clemson) worked first
time. This works with no pop user, no etra database so I'll stick with this
until I need more.
The Mike Godsey included article was a detailed list of what to do to get the
distributed pop working. Richard Rogers noted that the documentation for OSF/1
v3.0 does not contain a manually setting up sendmail bit which v2 did and the v2
version explained how to set things up.
I think the best answer is to use a different pop implementation. Pop users ned
a username on the server machine but that is no difficulty here as she needs one
to be able to make things available for backup.
Thanks to all who replied
John.
Complete replies follow here
----------------------------
If you really want to save time configuring pop3 consider this
download pop3d (/pub/src on hubcap.clemson.edu (130.127.8.1) )
compile
install in /etc/inetd.conf :
pop-3 stream tcp nowait root /etc/pop3d pop3d
Make shure you have an entry in /etc/services :
pop-3 110/tcp # Post Office version 3
Et Voila !!!
The pop3d that comes with OSF is painfull to install ... and administer
This pop3d needs NO admin
Good luck
Michel Cyr
SIDOCI enr.
IST-Integration inc.
(514)252-4333 ex 258
Michel.Cyr_at_sidoci.qc.ca
----------------------------------------------
POP3D stuff deleted....
>Does anyone know how to set up the mailer to work with POP as well as SMTP?
>
>All ideas gratefully received and I'll post a summary if I get any answers.
John. I know you probably don't want to hear about a totally different sol-
ution, but have you tried Qualcomm's POP3 server? It runs on OSF/1 (I did
some of the port) and supports numerous extensions to POP3, but the vanilla
setup is very lean and easy to install. I had it up and working (after the
port) in about 30 minutes. You use regular accounts, there are no databases,
or any other special constructs. Just a tweak to the /etc/services file, the
inetd.conf file and installing the popper server file.
You might want to consider it. Check out ftp.qualcomm.com in the /pub/quest
subdir, I think there is a unix/servers directory after that. It has been
a bit since I have been there.
Chris
----------------------------------------------
John Richards <john_at_zyqad.co.uk> wrote:
: Hello all,
:
: I've got a problem with configuring the POP3 mail supplied with OSF/1 v3.0.
: I can start the popd but I can't build a pop database that the system will use.
:
: no entry for ~pop
You need to add a user with login-id "pop". The pop database ~pop/POP
resides in pop's home directory and pop mail is spooled to this
directory via a mail alias. It's been a long time since I set this up
and I switched to regular POP3 service so this is all pretty fuzzy.
Steve Swinnea
swinnea_at_che.utexas.edu
Department of Chemical Engineering
The University of Texas at Austin
---------------------------------------------
The answer is you need to add an account for user pop. I haven't done this
under OSF, and I'm the first to admit I don't know a lot about pop, but some
of our machines here came with pop installed and working so from one of their
passwd files...
pop:*:273:76:Post Office Protocol:/usr/spool/pop:/bin/csh
You might need to adjust home dir etc to suit, but it's a starting point.
Only other suggestion just now is to get hold of the freeware POP distribution
and read it's docs. I think you need to put stuff in sendmail.cf too.
Sorry this is a bit vague...
Simon
---------------------------------------------------------------------
John,
One of the things that you may have to do is make a directory in your pop dir
called pop, what I mean is:
mkdir ~pop/pop
In this dir make a link called POP that's linked to the ~pop/POP. I think there
is a bug that makes it look for ~pop/pop/POP instead of ~pop/POP. Below I've
included a good detailed list of directions to get a pop server up that was
posted on the group a while ago.
Following these directions worked for me, except for the command that actually
started popd:
# /usr/lib/mh/popd -p 110 >& /dev/null &
^ I had a problem with this &, but after I took it
out the server worked fine. If you know why the & is incorrect here I'd
appreciate some insight.
Cardell
------------------- Forwarded Message
From: Mike Godsey <mgodsey_at_medio.com>
Reply-To: Mike Godsey <mgodsey_at_medio.com>
Message-Id: <199502100013.QAA02100_at_dns.medio.com>
Followup-To: poster
Subject: SUMMARY: setting up POP server
To: alpha-osf-managers_at_ORNL.GOV (Alpha OSF Managers List)
Date: Thu, 9 Feb 1995 16:13:03 -0800 (PST)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 6587
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> |
-----------------------------------------------------------------
------- End of Forwarded Message
---------------------------------------------
I have the same system, administratively. I gave pop mail users regular
accounts. They never really log in. I use the pop mail server pop3d. I
plugged it in, and it works. I don't know where it's available from, but I
could find out if you want.
---------------------------------------------
If you scan the mailing list's archives you'll find a post
which describes how to properly set up the POP server.
Matt
--
Matt Harrington matt_at_sbl.salk.edu
The Salk Institute http://sbl.salk.edu/~matt
San Diego, CA
---------------------------------------------
i've never tried to use the dec-supplied popd, but i've always been
amazed at the amount of suffering endured by people trying to set it
up. i use a version of popd which i believe came from berkeley.
no databases or other nonsense - it just reads the passwd info.
unless you have to support many "pop-only" pseudo-accounts, i'd suggest
punting on the dec stuff and getting another popd.
Jim Wright Keck Center for Integrative Neuroscience
jwright_at_phy.ucsf.edu Department of Physiology, Box 0444
voice 415-502-4874 513 Parnassus Ave, Room HSE-811
fax 415-502-4848 UCSF, San Francisco, CA 94143-0444
---------------------------------------------
On Tue, 20 Jun 1995, John Richards wrote:
> Does anyone know how to set up the mailer to work with POP as well as SMTP?
>
> All ideas gratefully received and I'll post a summary if I get any answers.
A SIMPLE pop server is available from ftp.bf.rmit.edu.au/pub/src/pop3d
(including a version for enhanced security). All it requires in compiling,
and a line added to inetd.conf. Note that:
- All user accounts have access to pop email
- The pop password is the same as their UNIX password.
I never bothered with the version that came with OSF/1, as I had
ported this one before realizing that it was there.
_____
// // __ For a good time call http://www.bf.rmit.edu.au/~zen //
// / \ I\ I zen_at_rmit.edu.au //
// (-- I \I Unix Systems Administrator //
// \__/ I I alias Stuart Bishop Business Faculty, RMIT //
((_______________________________________________________________________//
---------------------------------------------
Hi,
>
>I've got a problem with configuring the POP3 mail supplied with OSF/1 v3.0.
>
As far as I can see, POPPER is much simpler to install than POP3. In fact I
had no problem at all!
POPPER is available at ftp.qualcomm.com (they also distribute Eudora)
Just one thing: add the flag -D_BSD in the CC directive.
Good luck,
Jean-Loup
---------------------------------------------------------------------
Jean-Loup Risler Tel: (33 1) 69 82 31 34
CNRS Fax: (33 1) 69 07 49 73
Centre de Genetique Moleculaire Email: risler_at_cgmvax.cgm.cnrs-gif.fr
91198 Gif sur Yvette Cedex France
---------------------------------------------------------------------
---------------------------------------------
On Tue, 20 Jun 95 14:44:07 +0100 John Richards <john_at_zyqad.co.uk> wrote:
>Hello all,
>
>I've got a problem with configuring the POP3 mail supplied with OSF/1 v3.0.
>
>The man pages are distinctly skimpy on the subject and I can't find anything in
>the online docs either.
>
>John
You're right - I set it up under version 2 of OSF/1, and it was
documented then! If you have access to a v2 document set (or the
v2 O.S. CD, it's all in Network Configuration, chapter 19, on
Manually Setting Up The Mail System (a lot of later chapters on
"Manually Setting Up..." appear to have been deleted in the v3
equivalent manual).
In case you haven't got access to the old manual, here's the
essentials of the relevant section:
1. Create an account called pop, whose home directory is
/var/spool/pop (this directory owned by pop).
2. chown pop /usr/lib/mh/spop
3. Create ~pop/POP
4. add the user entries into the POP database in the format
user::user-file:::user_at_client-address::::0
Note: I left "user_at_client-address" blank, i.e. null string, and
set the user-file in a subdirectory, so it became
user::subdir/user:::::::0
5. Run popaka for each user entered in the POP databse; this returns
a string.
6. Enter the string returned by popaka in the system-wide alias file
(/var/adm/sendmail/aliases) and run newaliases.
7. Run popd in the background, redirecting output to a null file.
Note: if you have problems, don't redirect it, you can get real-time
diagnostics from it...and your users' passwords.
The manual says nothing about running popwrd at this stage; I'd suggest
it's a good idea...
Richard
-----------------------------------
Richard M Rogers
Computing Services
Staffordshire University
Tel. 01785 (+44 1785) 353396
E-mail: R.M.Rogers_at_staffs.ac.uk or cstrmr_at_staffs.ac.uk
Received on Wed Jun 21 1995 - 17:46:25 NZST