At 7:06 PM +0100 11/7/00, Mauk van der Laan wrote:
> Yes, I have the same problem here. Qpopper will sometimes
> hang and has to be killed. I did an strace on the hanging
> process and it appears to be waiting for input. It allways
> hangs after the client has sent its name and password.
> The old version (2.xx) and the latest (3.1) have the same
> problem.
>
> It happens only on two accounts. A possible reason for this
> problem migh be that they use the outlook version that comes
> with Office 97 (sigh) and they read each others email,
> but leave it on the server.
>
> Any comments?
>
> Mauk van der Laan
>
>
> At 09:31 7-11-2000 +0100, Oliver Fleischmann wrote:
>> Hi there!
>>
>> Since about four weeks we have moved our mail server from a slow
>> SUN solaris machine with sendmail and qpopper 3.0 beta something
>> and UW-imap to an i686 linux machine with Exim as MTA and qpopper
>> 3.1fc1 and a current UW-imap.
>>
>> Since then we experience some never dying qpopper processes laying
>> around, with the corresponding mailbox files locked. Though locking
>> doesn't seem to really work as there are not only the ".user.pop" files,
>> but also new "user" files with new mail. I'm sure, the users don't leave
>> open their pop3 connection for weeks.
>>
>> I suspect a locking incompatibility between qpopper and exim. Has
>> anybody else experienced such problems and has a solution?
>>
>> Your help would be very much appreciated.
>> Yours
>> Oliver
If it only happens with two users, can you configure a Qpopper with
debug tracing and run it on a different port, then have just these
two users change their Outlook to use the new port? That would be
a big help in tracking down what is going on. You could also
modify inetd.conf to strace Qpopper from the start, but only on the
new port.
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t tracefile'.
4. Send inetd a HUP signal.
This causes detailed tracing to be written to the syslog (if you
used '-d') or to the file specified as 'tracefile'.
I'd be very interested in seeing a trace and strace for a Qpopper
process which hangs.
