Re: QPOPPER Will Not Work

[dbrady@pobox.com (Don Brady)]

inetd.conf has:

pop-3 stream tcp nowait root /usr/sbin/tcpd  /usr/sbin/in.qpopper 

 I was advised by another reader to make the following two directories owned
by root and part of group 'mail':  /var/spool/mail and /var/spool/pop. 

 This does in fact fix the problem - for a while.   After a while the group
of /var/spool/mail is reset by something (sendmail?) back to root.   At that
the problem occurs again - users cannot connect to the POP server - it
complains about permission problems when they try - "Do you own it?" it says
referring to /var/spool/pop/dbrady.pop for example.

 Any further insights would be appreciated.

 Thanks,

 Don






miquels@cistron.nl (Miquel van Smoorenburg)  wrote:

It sounds like qpopper is not running as root (it should). What
is the exact line from /etc/inetd.conf that calls qpopper ?


In article <[🔎] 3360197f.44850281@mail.ipass.net>,
Don Brady <dbrady@pobox.com> wrote:
> Well I spent most of the evening trying to get qpopper to work.   (The
>current package).
>
> First it complains that it cannot write to /var/spool/pop.
>
> So I make var/spool/pop writeable by all (hardly seems desirable).
>
> Then it complains that the password is wrong. Or that the lock file is
>still there.   In fact everytime it leaves var/spool/pop/dbrady.pop there
>and I have to delete it manually to try again  - even when it claims the
>problem was the password.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .