At 01:16 PM 12/5/01, Clifton Royston wrote: >On Wed, Dec 05, 2001 at 06:16:39PM +0100, Tom Van de Wiele wrote: > > Okay, so I downloaded, installed and ran qpopper 4.0.3. But it gives me > > the same problem :-/ > > > > Now I compiled in debugging, and this is what syslog gave me: > > > > Dec 5 18:09:53 alexandria popper[13612]: I/O error flushing output to > > client pascale.fr at 192.168.1.20 [192.168.1.20]: Operation not > > permitted (1) [pop_send.c:685] > > > > Microsoft Entourage and Outlook still crash while trying to collect the > > mail... > > I didn't say it would stop them from crashing. They're buggy programs. > > What *should* have improved is that now they should not be locked out >of the spool file for several minutes as a result. That "I/O error" >message above indicated that qpopper now detects that the client has >gone away so that the mail spool should be back in place immediately.
There's code in the next release of qpopper to give up more quickly when detecting the TCP session has been terminated by the other end, which should help some. I've been running with those mods for a while. > > HELP please... > > You'll still need to track it down to what message or messages in the >mailbox cause them to crash; I would start by looking for viruses or >for spam messages with large attachments and deleting those. It would appear the problems are between Microsoft and the email, and the only issue with qpopper is in how quickly it releases the mail spool after a client program croaks. I'd say Microsoft is probably the proper place to go for support. Perhaps a newer version will fix the problem (though it'll doubtless introduce others). ----------------------------------------------------------------- Daniel Senie [EMAIL PROTECTED] Amaranth Networks Inc. http://www.amaranth.com
