Thanks Chris, I'll try this. I've increased the timeout to 300 seconds (if the timeout, by default is less than 300 seconds!) with the -T 300 popper switch in inetd.conf, which now reads:
pop3 stream tcp nowait root /usr/sbin/tcpd /usr/local/sbin/popper - s -R -T 300 I didn't see the -T option in your inetd.conf line (maybe you have configured the timeout in a popper global configuration file?). But I have put the -R that I saw in your configuration into mine too - disabling the IP lookup can't hurt anything. I'll see what happens now... All the best, Derek -----Original Message----- From: Chris Payne [mailto:[EMAIL PROTECTED] Sent: 16 February 2004 13:53 To: Derek Conniffe Subject: Re: POPPER jamming I run a Linux SMP system, and had initial problems with this file hanging around. The problem was resolved by increasing the wait time on the inetd line for popper. pop3 stream tcp nowait.400 root /usr/local/lib/popper popper -s -R This may or may not be the same issue that you have, but it is worth a look. Regards, Chris Payne On 16 Feb 2004 at 11:16, Derek Conniffe wrote: > Hi all, > > I've been having a problem with qpopper for quite a while now with > qpopper version 4.0.5 and SuSE linux 7.1 with kernel 2.4.21 (SMP two > processors). > > > Thanks very much for your help, > > Derek > > -- > Derek Conniffe > Rivertower Limited -- Chris Payne Network Administrator Physical Resources Dept, University of Guelph [EMAIL PROTECTED] Tel: (519) 824-4120 x52882 Fax: (519) 837-0581 --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.583 / Virus Database: 369 - Release Date: 10/02/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.583 / Virus Database: 369 - Release Date: 10/02/2004
