content of /etc/hosts.allow sshd: ALL exim: ALL in.telnetd:192.168.1. in.qpopper:192.168.1.
-----Original Message----- From: Daniel Senie [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 25, 2001 1:35 AM To: Subscribers of Qpopper Subject: RE: problem with qpopper 4.04 At 11:56 PM 12/23/01, you wrote: ># qpopper config file for xinetd >service pop-3 >{ > flags = REUSE NAMEINARGS > socket_type = stream > protocol = tcp > wait = no > user = root > server = /usr/sbin/in.qpopper > server_args = in.qpopper -s > # use this line once you create your certificate to enable STLS > # server_args = in.qpopper -s -l 1 -f /etc/mail/qpopper.conf >} This will result in TCP Wrappers being called (via libwrap). You need to add an entry in your /etc/hosts.allow to permit qpopper to run. It'll probably be something like: in.qpopper: ALL: ALLOW TCP Wrappers works based on the program name of the daemon, which would account for why the ipop3d worked and qpopper doesn't, assuming your /etc/hosts.allow is other than an empty file. [You might want to tell us what your /etc/hosts.allow looks like, if the above doesn't fix the problem] >-----Original Message----- >From: Kenneth Porter [mailto:[EMAIL PROTECTED]] >Sent: Monday, December 24, 2001 10:27 AM >To: Subscribers of Qpopper >Subject: Re: problem with qpopper 4.04 > > >On Sun, 2001-12-23 at 18:21, Peter Santiago wrote: > > qpopper's complaint.. > > Dec 23 22:43:46 gateway in.qpopper[6663]: Unable to obtain socket and > > address > > .... if I used gnupop3d....without changing anything... works fine... >really > > puzzled.... > >How are you launching it? What's your inetd/xinetd setup look like? Or >are you running it standalone? > >through xinetd.... if I launch it as stand-alone... wouldn't connect to >socket........... >
