On Tue, Mar 19, 2002 at 09:37:08AM -0000, Neil R Porter wrote:
> (pop3)<><><><><><><><><><><><><>
> # qpopper config file for xinetd
> service pop3
> {
> flags = REUSE NAMEINARGS
> socket_type = stream
> protocol = tcp
> wait = no
> user = root
> server = /usr/sbin/in.qpopper
> server_args = in.qpopper -s
> config-file = /etc/qpopper.config
...
I don't think that line actually does anything, and I don't know where
you got that syntax from. Here's a working snippet of xinetd.conf
configuration.
service pop
{
flags = REUSE
socket_type = stream
protocol = tcp
wait = no
user = root
groups = yes
server = /usr/local/libexec/popper
server_args = -s -R -T 300 -f /usr/local/etc/pop.options
# cut off popper if load goes above this value
max_load = 100
# only allow this many simultaneous popper connections
instances = 100
}
Note that I use the "-f" flag to set the popper config file. I also
disable reverse lookups and set timeouts to 5 minutes; I recommend you
do that somewhere too (though you can just as well do it in your config
file.)
> (snippet from /etc/qpopper.config)<><><><><><><><><><><><><>
> # Set this to the full path to the mail spool directory.
> #
> # The default is determined at compile time.
> #
> set spool-dir = /var/spool/mail
> <><><><><><><><><><><><><><><>
>
> So, have I used the correct way to try to get qpopper to user the
> qpopper.config
No.
> and secondly, if so, why is it ignoring it? If indeed
> this is the problem.
That's most likely your problem. Fix that and see if the rest falls
into place.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED]
"What do we need to make our world come alive?
What does it take to make us sing?
While we're waiting for the next one to arrive..." - Sisters of Mercy
