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.

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.

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.

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

At 12:45 PM 5/9/2001 -0700, Randall Gellens wrote:
>At 3:26 PM -0400 5/9/01, Bob wrote:
>
>>  Randy,  I saw your response to a similar message, so I am reposting 
>> this one.  I have tried turning on the chunky writes option.
>
>Try setting chunky-writes to never.
>
>>
>>  In some cases, a poor modem connection with a lot of packet loss has 
>> been the problem.  However, in most of our cases, the connection is fine 
>> with a solid ping during the mail checks. This was a non issue with 
>> 2.5.3.  Any other possibilities here? Any suggestions?  Thanks for your 
>> time.  Any help would be much appreciated.  -Bob
>>
>>>  Date: Sun, 06 May 2001 20:52:52 -0400
>>>  To: [EMAIL PROTECTED]
>>>  From: Bob <[EMAIL PROTECTED]>
>>>  Subject: ERR POP EOF or I/O Error
>>>
>>>  Hello folks.  We've been having trouble since we upgraded to using 
>>> Qpopper 4.0.1 (on FreeBSD 4.3-STABLE).  We were using Qpopper 2.5.3 (on 
>>> FreeBSD 2.2.6-RELEASE).  Some users with no modem, computer, or 
>>> settings problems (who were able to receive mail via Qpopper 2.5.3) can 
>>> not receive mail.  The e-mail clients being used very (Outlook, Outlook 
>>> Express, Netscape). So far, nobody using Eudora has had a 
>>> problem.  Folks who are having the problem, who then install and try 
>>> Eudora work fine while using Eudora.  If they try their other e-mail 
>>> client it continues to fail.  Example of errors are listed below.  The 
>>> most common single error is...
>>>
>>>  <USERNAME> at <DNS & IP ADDRESS>: -ERR POP EOF or I/O Error
>>>
>>>  Some less frequent errors are...
>>>
>>>  I/O error flushing output to client <USERNAME> at <DNS & IP ADDRESS>: 
>>> Operation not permitted (1)
>>>
>>>  (null) at <DNS & IP ADDRESS>: -ERR POP EOF or I/O Error
>>>
>>>  We have set the following options...
>>>
>>>  set cache-dir = /var/spool/poptemp
>>>  set temp-dir = /var/spool/poptemp
>>>  set log-facility = local0
>>>  set chunky-writes = tls
>>>  set server-mode
>>>  set downcase-user
>>>  set statistics
>>>  set trim-domain
>>>  set timeout = 600
>>>
>>>  Any ideas and suggestions would be much appreciated.  Please reply to 
>>> the list.  Thanks in advance.
>>>
>>>  -Bob
>>
>>
>>
>>  _________________________________________________________
>>
>>  Do You Yahoo!?
>>
>>  Get your free @yahoo.com address at http://mail.yahoo.com



_________________________________________________________

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.yahoo.com



Reply via email to