At 8:34 PM -0400 5/10/01, Bob wrote:
> The chunky-writes (never) option seems to make no difference. I
> did turn on the following option:
>
> set log-login = "v%0 POP login by user %1 at (%2) %3"
>
> I noticed that the error occurs before the POP login. For users
> with the POP EOF or I/O error problem no POP login line is
> generated. However, the username is included on the POP EOF error
> line.
That indicates the client had sent the USER command, but timed out
before it sent the PASS command. Are all these clients Outlook or
Outlook Express?
>
> Also, one client's screen (Outlook Express) displays authorizing
> until they get a message stating that the POP server hasn't
> responded (prompting STOP or WAIT). The user pressed WAIT several
> times then was prompted (again) for their password (no invalid
> password lines were generated in the log). It then downloaded
> messages.
So it's very intermittent.
>
> I had one user (with the POP EOF error) set their POP server back
> to a machine running 2.5.3. Copied their mail file over to the
> 2.5.3 machine and had them check their mail. They received their
> mail fine. Set the POP server back to the machine running 4.0.1
> (same mail file still there), checked the mail just fine with no
> error.
More evidence of it being intermittent.
>
> This is very frustrating. Any other suggestions? Is anyone else
> continuing to have this trouble? Any bug reports been filed? Are
> any of the older versions safe to use?
>
> Any help would be much appreciated. -Bob
If you can, have the users either try a different client (such as
Eudora or Netscape), or at least increase the network timeout.
Try turning on debug tracing in Qpopper, perhaps for only those users
who have problems. You can also try capturing packet traces.
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'.
