Re: error flushing output to client
On Mon, 19 Sep 2005, GioiaBa wrote: > but I know for sure that Some of those, do NOT have Norton Antivirus 2005 > installed.. so there has to be another reason for this.. > but I know it is not simple to find out why it happens.. large messages, slow connections, short timeouts set on the clients (default is usually 60 seconds per message)
Re: error flushing output to client
Thanks Daniel well in fact, I don't konw the pc user environment for all users having these trouble sometimes.. but I know for sure that Some of those, do NOT have Norton Antivirus 2005 installed.. so there has to be another reason for this.. but I know it is not simple to find out why it happens.. any other hints will be appreciated.. thanks again.. : ) Daniel Senie Scrive: At 08:56 AM 9/19/2005, GioiaBa wrote: Hi list ! my problem is that I have these entries in my /var/log/maillog file # Sep 18 10:31:36 mail popper[13054]: I/O error flushing output to client user1 at adsl000.domain.com.au [xxx.xxx.xxx.xxx]: Operation not permitted (1) This error indicates the TCP session has gone away from under qpopper. In other words, the TCP session was closed because the remote endpoint (PC in this case) closed the connection. # and the client itself (using Oexpress or Outlook) gets an error that it disappears when it do 'send and receive' once again.. it happens not all days, and not for all the users.. I searched the list, and found someonelse having the same trouble, but I can't still have a solution... I'm running slackware 10 with log2db-0.6 ; qpopper4.0.5 ; sendmail 8.12.11 thanks anyone.. Generally this is caused by timeouts that are too short on the PC, or antivirus software doing dumb things, with the latter becoming epidemic of late. We've moved a lot of customers to POP on alternate port with TLS (TCP/995) to get their email away from the interference caused by the latest live updates to Norton Antivirus 2005. There may be a better solution to dealing with Norton (configuration, bug fix, or uninstall) but this work-around has at least made it possible to keep customers functional. Your problem may or may not be at all related to antivirus, but it's something to look at. GB
Re: error flushing output to client
At 08:56 AM 9/19/2005, GioiaBa wrote: Hi list ! my problem is that I have these entries in my /var/log/maillog file # Sep 18 10:31:36 mail popper[13054]: I/O error flushing output to client user1 at adsl000.domain.com.au [xxx.xxx.xxx.xxx]: Operation not permitted (1) This error indicates the TCP session has gone away from under qpopper. In other words, the TCP session was closed because the remote endpoint (PC in this case) closed the connection. # and the client itself (using Oexpress or Outlook) gets an error that it disappears when it do 'send and receive' once again.. it happens not all days, and not for all the users.. I searched the list, and found someonelse having the same trouble, but I can't still have a solution... I'm running slackware 10 with log2db-0.6 ; qpopper4.0.5 ; sendmail 8.12.11 thanks anyone.. Generally this is caused by timeouts that are too short on the PC, or antivirus software doing dumb things, with the latter becoming epidemic of late. We've moved a lot of customers to POP on alternate port with TLS (TCP/995) to get their email away from the interference caused by the latest live updates to Norton Antivirus 2005. There may be a better solution to dealing with Norton (configuration, bug fix, or uninstall) but this work-around has at least made it possible to keep customers functional. Your problem may or may not be at all related to antivirus, but it's something to look at.
error flushing output to client
Hi list ! my problem is that I have these entries in my /var/log/maillog file # Sep 18 10:31:36 mail popper[13054]: I/O error flushing output to client user1 at adsl000.domain.com.au [xxx.xxx.xxx.xxx]: Operation not permitted (1) # and the client itself (using Oexpress or Outlook) gets an error that it disappears when it do 'send and receive' once again.. it happens not all days, and not for all the users.. I searched the list, and found someonelse having the same trouble, but I can't still have a solution... I'm running slackware 10 with log2db-0.6 ; qpopper4.0.5 ; sendmail 8.12.11 thanks anyone..
Re: error flushing output to client
I am using enable-chunky-writes, enable-hash-spool=2, enable-temp-drop-dir, enable-standalone. The temp drop is not on a seperate partition right now, but I can try that too. Thnx On Thu, 3 Mar 2005, Tim Villa wrote: > Try enable-chunky-writes, and perhaps having the temp drop folder residing > on a separate partition from your mail spools. Both will address > performance issues - the first for the link, the second for the server disk > IO. > > At 02:44 2005/03/03, Netlink Tech wrote: > >Hello, > > > >Is this still active? > > > >Trying to find info on 'error flushing output to client' errors with > >qpopper 4.05, Linux, etc. > > > >Most of problems are slow connections and/or large messages and/or large > >number of messages. > > > >What is the solution to not have these problems. > > > >OR what is a suitable replacement for qpopper? > > > >Tried cucipop, but I have a number of users that use PINE to read e-mail, > >which causes problems with UIDL and messages appearing as new (another > >copy downloaded) to Outlook Express. > > > >Thanks, > >Curt > > -- > Tim Villa, Network / Systems Administrator > M252, Business School and Law School > The University of Western Australia CRICOS provider number 00126G > Phone: +61-8-6488-1796, Fax: +61-8-6488-1068 > Mail <mailto:[EMAIL PROTECTED]> WWW <http://timvilla.com/> > >
Re: error flushing output to client
Try enable-chunky-writes, and perhaps having the temp drop folder residing on a separate partition from your mail spools. Both will address performance issues - the first for the link, the second for the server disk IO. At 02:44 2005/03/03, Netlink Tech wrote: Hello, Is this still active? Trying to find info on 'error flushing output to client' errors with qpopper 4.05, Linux, etc. Most of problems are slow connections and/or large messages and/or large number of messages. What is the solution to not have these problems. OR what is a suitable replacement for qpopper? Tried cucipop, but I have a number of users that use PINE to read e-mail, which causes problems with UIDL and messages appearing as new (another copy downloaded) to Outlook Express. Thanks, Curt -- Tim Villa, Network / Systems Administrator M252, Business School and Law School The University of Western Australia CRICOS provider number 00126G Phone: +61-8-6488-1796, Fax: +61-8-6488-1068 Mail <mailto:[EMAIL PROTECTED]> WWW <http://timvilla.com/>
error flushing output to client
Hello, Is this still active? Trying to find info on 'error flushing output to client' errors with qpopper 4.05, Linux, etc. Most of problems are slow connections and/or large messages and/or large number of messages. What is the solution to not have these problems. OR what is a suitable replacement for qpopper? Tried cucipop, but I have a number of users that use PINE to read e-mail, which causes problems with UIDL and messages appearing as new (another copy downloaded) to Outlook Express. Thanks, Curt
Re: I/O error flushing output to client
On 3/17/04 1:03 AM, "Chuck Yerkes" <[EMAIL PROTECTED]> wrote: > Quoting george ([EMAIL PROTECTED]): >> On 3/16/04 6:34 PM, "Alan Brown" <[EMAIL PROTECTED]> wrote: >> >>> On Tue, 16 Mar 2004, Chuck Yerkes wrote: >>> Why 7.2? (when 9.0 has been out forever). RedHat AS 2.0 is old and is based on 7.2. 7.2 is from 2000 or so. >>> >>> Probably the same reason we use 7.2 at $orkplace - we have a >>> standardised desktop distribution and not enough hours available to >>> assess the impact of changing it drastically. >>> >>> (We're going to have to, as a lot of newer hardware simply isn't supported) >>> >> Gota spin in- >> If the tool works, why change for the sake of change? > > Security updates, performance improvements, management improvements, support, > better tools. > Tried and true systems that have no problems should not be updated just to update and "find" new security holes. I agree if a box has issues, the first thing would be to update. No question. But, no problems = no reason. Most people know their own systems. Nowadays most people are stretched so thin it's very nice to not be updating-changing all the time and just to sit back and watch the "little lights blink" with the knowledge you know what's going on. > Change for the sake of change is bad. > Stagnation for the sake of avoiding change is also bad. > >> We just bought SuSE 9.0. >> Our other SuSE box is 7.* PPC >> apple 8550 -still kickin >> (Hardware change - [drive space & ram] from 8550) > > Yeah, I still have a working and running Apple //+ and Sun 3 here. > The SPARC 10 is running a new OpenBSD, the Pentium/90 is running > FreeBSD 5.2.1; the Athlon/900 is running Redhat 9. > We have a few Cobalt boxes, ASIP, OSXS, Yellowdog, Snap, etc. here. (No, we are not brand loyal.) All are behind firewalls. (in and out) Some are only for fileservers, some for backup, etc. Most are not running the latest and greatest. We like it that way for a few reasons. > Unsecure software is a danger to all of us. If your company > gets screwed, well that's not my problem. When your server > attacks MINE, then it's my problem. And you don't want the > feeling I had a dozen years ago when I got a call from CERT > at the company I'd just started at telling us that a couple > sites had been attacked from our computer (our big server that > could NOT be easily rebuilt). > Everyone's situation is different. To automatically jump on someone for not running what you consider acceptable OS versions do not make people what to chime in or ask questions. Our best, most stable, longest running, easiest server by far? Home/Billing office office still has ASIP 6.3.3 running 9.2. Oh, that one is not behind a firewall. Never been, from 5.0. Am I afraid? Nope. It's very well tried and true, and very EOL. End topic. -- Thanks, George "...Linux, MS-DOS, and Windows XP" (also known as the Good, the Bad, and the Ugly)
Re: I/O error flushing output to client
On Wed, 17 Mar 2004, Chuck Yerkes wrote: > Change for the sake of change is bad. > Stagnation for the sake of avoiding change is also bad. If it makes you feel better, we firewall _all_ outbound as well as inbound connections and there is up-to-the-hour AV/spam running in both directions on the network mail bastion server. That's something forced on us by all the stupid windoze users, but it provides protection against any rogue boxes of any flavour OS. On top of the firewalling, excessive attempts to go past the firewall on unauthorised ports result in immediate lockout of the relevant switchport and that requires manual intervention to restore.
Re: I/O error flushing output to client
Quoting george ([EMAIL PROTECTED]): > On 3/16/04 6:34 PM, "Alan Brown" <[EMAIL PROTECTED]> wrote: > > > On Tue, 16 Mar 2004, Chuck Yerkes wrote: > > > >> Why 7.2? (when 9.0 has been out forever). RedHat AS 2.0 is old and > >> is based on 7.2. 7.2 is from 2000 or so. > > > > Probably the same reason we use 7.2 at $orkplace - we have a > > standardised desktop distribution and not enough hours available to > > assess the impact of changing it drastically. > > > > (We're going to have to, as a lot of newer hardware simply isn't supported) > > > Gota spin in- > If the tool works, why change for the sake of change? Security updates, performance improvements, management improvements, support, better tools. Change for the sake of change is bad. Stagnation for the sake of avoiding change is also bad. > We just bought SuSE 9.0. > Our other SuSE box is 7.* PPC > apple 8550 -still kickin > (Hardware change - [drive space & ram] from 8550) Yeah, I still have a working and running Apple //+ and Sun 3 here. The SPARC 10 is running a new OpenBSD, the Pentium/90 is running FreeBSD 5.2.1; the Athlon/900 is running Redhat 9. Unsecure software is a danger to all of us. If your company gets screwed, well that's not my problem. When your server attacks MINE, then it's my problem. And you don't want the feeling I had a dozen years ago when I got a call from CERT at the company I'd just started at telling us that a couple sites had been attacked from our computer (our big server that could NOT be easily rebuilt).
Re: I/O error flushing output to client
On 3/16/04 6:34 PM, "Alan Brown" <[EMAIL PROTECTED]> wrote: > On Tue, 16 Mar 2004, Chuck Yerkes wrote: > >> Why 7.2? (when 9.0 has been out forever). RedHat AS 2.0 is old and >> is based on 7.2. 7.2 is from 2000 or so. > > Probably the same reason we use 7.2 at $orkplace - we have a > standardised desktop distribution and not enough hours available to > assess the impact of changing it drastically. > > (We're going to have to, as a lot of newer hardware simply isn't supported) > Gota spin in- If the tool works, why change for the sake of change? We just bought SuSE 9.0. Our other SuSE box is 7.* PPC apple 8550 -still kickin (Hardware change - [drive space & ram] from 8550) -- Thanks, George "...Linux, MS-DOS, and Windows XP" (also known as the Good, the Bad, and the Ugly)
Re: I/O error flushing output to client
On Tue, 16 Mar 2004, Chuck Yerkes wrote: > Why 7.2? (when 9.0 has been out forever). RedHat AS 2.0 is old and > is based on 7.2. 7.2 is from 2000 or so. Probably the same reason we use 7.2 at $orkplace - we have a standardised desktop distribution and not enough hours available to assess the impact of changing it drastically. (We're going to have to, as a lot of newer hardware simply isn't supported)
Re: I/O error flushing output to client
Quoting Lisa Casey ([EMAIL PROTECTED]): > Dumb question here maybe, but I'ld appreciate some help. Our mail server > used to be running on FreeBSD which has a /etc/init.d file. We have moved it Nope. Look for it. Perhaps inetd.conf. Perhaps you had it start as a daemon. It depends which. > to a Redhat 7.2 server. I cannot find the file on this box where I would And that server has been patched in the last week or two for the latest kernel problems? Why 7.2? (when 9.0 has been out forever). RedHat AS 2.0 is old and is based on 7.2. 7.2 is from 2000 or so. Pity about the downgrade from FreeBSD. > change qpopper's timeout. There is no /etc/init.d or /etc/servers. In redhat, inetd is done by vixie's "xinetd". I forget for 7.2, but redhat tends to use a file per service and puts them in /etc/xinet.d/ No idea what /etc/servers would be. Never heard of it in 4 BSDs, Solaris, or 4 other unixes I touch.
Re: I/O error flushing output to client
On Tue, 16 Mar 2004, Lisa Casey wrote: > Dumb question here maybe, but I'ld appreciate some help. Our mail server > used to be running on FreeBSD which has a /etc/init.d file. We have moved it > to a Redhat 7.2 server. I cannot find the file on this box where I would > change qpopper's timeout. There is no /etc/init.d or /etc/servers. Hi Lisa, You wouldn't perhaps be referring to inetd.conf in /etc ? FreeBSD rc scripts are in /usr/local/etc/rc.d/ and have been for a while. Redhat (people haven't phased it out yet?) uses xinetd.conf and some other scripts in /etc/xinetd.d as well I believe. http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&safe=off&threadm=a3bbjc%24rhn%241%40news.bbsrc.ac.uk&rnum=1&prev=/groups%3Fq%3Dredhat%2B7.2%2Binetd.conf%26num%3D50%26hl%3Den%26lr%3D%26ie%3DUTF-8%26safe%3Doff%26sa%3DN%26tab%3Dwg Gerald
Re: I/O error flushing output to client
Hi, Dumb question here maybe, but I'ld appreciate some help. Our mail server used to be running on FreeBSD which has a /etc/init.d file. We have moved it to a Redhat 7.2 server. I cannot find the file on this box where I would change qpopper's timeout. There is no /etc/init.d or /etc/servers. Thanks, Lisa Casey > Increase the timeout on your popper. We had some accounts that were pretty > large that would take more than a minute to flush out. With the timeout at > 60 seconds that was the error msg it would record. > > I think recommended is 10 minutes (600 seconds) and we've got ours set at > 5 minutes now. > > Gerald >
Re: I/O error flushing output to client
> > Mar 16 09:49:35 mail popper[20769]: I/O error flushing output to client at > > 192.168.197.188 [192.168. > > 197.188]: Operation not permitted (1) > > > > what will the reason of this problem ? > > Increase the timeout on your popper. We had some accounts that were pretty > large that would take more than a minute to flush out. With the timeout at > 60 seconds that was the error msg it would record. > > I think recommended is 10 minutes (600 seconds) and Thanks Gerald for your reply i have increase the timeout value in /etc/xinet.d/pop3 to 600 second server_args = qpopper -s -T 600 Regards Muhammad Talha we've got ours set at > 5 minutes now. > > Gerald >
RE: I/O error flushing output to client
On Tue, 16 Mar 2004, Edward Chase wrote: > Is this a compile time option or run time? I'm sure you can modify the default at compile time, but there is a run time option to set this. You folks do have a copy of the free manual Qualcomm lets you download right? Gerald
RE: I/O error flushing output to client
On Tue, 16 Mar 2004, Muhammad Talha wrote: > Mar 16 09:49:35 mail popper[20769]: I/O error flushing output to > client at 192.168.197.188 [192.168. > 197.188]: Operation not permitted (1) > > what will the reason of this problem ? From: Gerald [mailto:[EMAIL PROTECTED] Increase the timeout on your popper. We had some accounts that were pretty large that would take more than a minute to flush out. With the timeout at 60 seconds that was the error msg it would record. I think recommended is 10 minutes (600 seconds) and we've got ours set at 5 minutes now. Gerald Is this a compile time option or run time?
Re: I/O error flushing output to client
On Tue, 16 Mar 2004, Muhammad Talha wrote: > Mar 16 09:49:35 mail popper[20769]: I/O error flushing output to client at > 192.168.197.188 [192.168. > 197.188]: Operation not permitted (1) > > what will the reason of this problem ? Increase the timeout on your popper. We had some accounts that were pretty large that would take more than a minute to flush out. With the timeout at 60 seconds that was the error msg it would record. I think recommended is 10 minutes (600 seconds) and we've got ours set at 5 minutes now. Gerald
I/O error flushing output to client
Dear all i am facing this problem with some of my clients Mar 16 09:49:35 mail popper[20769]: I/O error flushing output to client at 192.168.197.188 [192.168. 197.188]: Operation not permitted (1) what will the reason of this problem ? Regards Talha
I/O error flushing output to client....
I'm receiving an I/O error flushing output to client jdoe at 172.16.1.1 [172.16.1.1]: Operation not permitted (1). This user is using Outlook Express 6.0. When he tries to pop his mailbox, it times out. He is the only person experiencing this problem. Any insight would be greatly appreciated. Steve Peace
Re: I/O error flushing output to client
We saw this problem fairly frequently. The clients in question were running Outlook XP, connecting to a qpopper-4.0.4 server on the same very lightly loaded LAN. Diddling with chunky-writes or Outlook's timeout values did no good. A google search pointed to a bug in Outlook XP (shocking!), wherein Outlook gets confused if the server responds "too quickly". See the "I frequently get a timeout" question at: http://www.workgroupmail.com/faq_area.asp?area=Client%20Setup&id=34 and: http://home.hetnet.nl/~ojb-hamster/EnWIP/EnWeb/html/faq18om.htm The URLs above both suggest configuring the server to pause for 50ms between POP commands. I changed qpopper to do that, which boils down to a "usleep(50*1000)" call in popper.c, just before the pop_get_command() call. Haven't seen the problem since. I can provide a patch on request. Cheers, -- Ken Lalonde, Global Remittance Network, Toronto
debian bug #160494 / qpopper logs wrong error messages "I/O error flushing output to client ... Operation not permitted"
Hi
I posted this one on 2002-09-11 on the debian bts but got no reaction
from anyone.
qpopper generates log messages like this one:
Sep 11 12:16:47 mail2 popper[7396]: I/O error flushing output to client joe at
somehost.sld.tld [1.2.3.4]: Operation not permitted (1)
the error message (Operation not permitted) is wrong afaics:
the relevant code from qpopper, pop_send.c is:
void
pop_write_flush ( POP *p )
{
int rslt = 0;
[...]
rslt = fflush ( p->output );
[...]
if ( rslt == EOF ) {
[...]
int e = ferror ( p->output );
pop_log ( p, POP_NOTICE, HERE,
"I/O error flushing output to client %s at %s [%s]: "
"%s (%d)",
p->user, p->client, p->ipaddr, STRERROR(e), e );
[...]
}
[...]
}
from fflush(3):
Upon successful completion 0 is returned. Otherwise, EOF is returned
and the global variable errno is set to indicate the error.
from ferror(3):
The function ferror tests the error indicator for the stream pointed to
by stream, returning non-zero if it is set.
ok, this is what happens:
1. fflush fails for some reason, sets errno to the error number and
returns EOF.
2. qpopper checks the error state of p->output, ferror returns 1
(non-zero!) since there's some error.
3. qpopper uses e (1) instead of errno -> a wrong error message is
generated.
I suggest this patch:
--- pop_send.c.orig 2002-09-11 12:48:38.0 +0200
+++ pop_send.c 2002-09-11 12:51:32.0 +0200
@@ -685,11 +685,12 @@
if ( p->tls_started )
pop_log ( p, POP_NOTICE, HERE, "Error flushing data to client" );
else {
-int e = ferror ( p->output );
- pop_log ( p, POP_NOTICE, HERE,
- "I/O error flushing output to client %s at %s [%s]: "
- "%s (%d)",
- p->user, p->client, p->ipaddr, STRERROR(e), e );
+if ( ferror ( p->output ) != 0) {
+ pop_log ( p, POP_NOTICE, HERE,
+ "I/O error flushing output to client %s at %s [%s]: "
+ "%s (%d)",
+ p->user, p->client, p->ipaddr, STRERROR(errno), errno );
+ }
}
hangup = TRUE;
} /* flush failed */
--
Joern "Wulf" Heissler
Re: I/O error flushing output to client
At 4:18 PM +0200 5/16/02, Martin Kellermann wrote: >>> popper[]: I/O error flushing output to client blah at blah >>> [blah]: Operation not permitted (1) >>> >>> what does this really mean, and when will it occur? >> >> Client (remote machine) closed the connection, qpopper tried to >> write to the socket, but the TCP session was already closed by the >> kernel on the server in response to the close from the client. > > ok, sounds good :) thanks. > so i can safely ignore this messages, because the connection is ALWAYS > closed by the remote machine? > or can this error also be generated by a messed up local tcp socket or > another weird local problem? It could be generated in response to some network problem, yes. Most likely it is just a client that closes the connection without sending 'quit'. > can i suppress the "-ERR POP EOF or I/O Error" (that occurs, for example > when client telnets port 110, logs in and then kills telnet session without > logging out) without patching the sources? Not currently.
Re: I/O error flushing output to client
At 09:54 16.05.02 -0400, you wrote: >At 08:58 AM 5/16/02, Martin Kellermann wrote: >>hi all! >> >>i searched already alot concerning the following qpopper error, but did >>not find an >>satisfying answer. >>i ran qpopper 4.0.4 on linux 2.4.18 >>no ssl, mysql or any other "special" enabled. just simple pop3. >>sometimes the log shows: >> >>popper[]: I/O error flushing output to client blah at blah [blah]: >>Operation not permitted (1) >> >>what does this really mean, and when will it occur? > >Client (remote machine) closed the connection, qpopper tried to write to >the socket, but the TCP session was already closed by the kernel on the >server in response to the close from the client. ok, sounds good :) thanks. so i can safely ignore this messages, because the connection is ALWAYS closed by the remote machine? or can this error also be generated by a messed up local tcp socket or another weird local problem? >>i dont think it´s just some network connection troubles...or is it? > >See if your client gave up. That's the usual cause. something else: can i suppress the "-ERR POP EOF or I/O Error" (that occurs, for example when client telnets port 110, logs in and then kills telnet session without logging out) without patching the sources? some of my clients are using a "broken" mailer software that behaves like explained, and my logs are full of " -ERR POP EOF or I/O Error"... thanx MK
Re: I/O error flushing output to client
At 08:58 AM 5/16/02, Martin Kellermann wrote: >hi all! > >i searched already alot concerning the following qpopper error, but did >not find an >satisfying answer. >i ran qpopper 4.0.4 on linux 2.4.18 >no ssl, mysql or any other "special" enabled. just simple pop3. >sometimes the log shows: > >popper[]: I/O error flushing output to client blah at blah [blah]: >Operation not permitted (1) > >what does this really mean, and when will it occur? Client (remote machine) closed the connection, qpopper tried to write to the socket, but the TCP session was already closed by the kernel on the server in response to the close from the client. >i dont think it´s just some network connection troubles...or is it? See if your client gave up. That's the usual cause. - Daniel Senie[EMAIL PROTECTED] Amaranth Networks Inc.http://www.amaranth.com
I/O error flushing output to client
hi all! i searched already alot concerning the following qpopper error, but did not find an satisfying answer. i ran qpopper 4.0.4 on linux 2.4.18 no ssl, mysql or any other "special" enabled. just simple pop3. sometimes the log shows: popper[]: I/O error flushing output to client blah at blah [blah]: Operation not permitted (1) what does this really mean, and when will it occur? i dont think it´s just some network connection troubles...or is it? thanx MK
Re: error flushing output to client
On Mon, 2002-04-08 at 08:52, Nathan Martinez wrote: > I have run across a problem with one of our clients. They are using > Microsoft Outlook 2000 in Workgroup mode. Each time that they try to get > their mail, this error shows up in my logs: > > Apr 8 18:45:10 mail in.qpopper[18979]: I/O error flushing output to client > laptop at 172.18.203.200 [172.18.203.200]: Operation not permitted (1) > > This user has quite a bit of mail (50MB), but it should still work. Has > anyone ran across this problem before? Thanks for your help. Looks like a classic client-side timeout. Qpopper is busy copying the spool right after the password is issued, and Outlook is timing out waiting for this to complete.
error flushing output to client
I have run across a problem with one of our clients. They are using Microsoft Outlook 2000 in Workgroup mode. Each time that they try to get their mail, this error shows up in my logs: Apr 8 18:45:10 mail in.qpopper[18979]: I/O error flushing output to client laptop at 172.18.203.200 [172.18.203.200]: Operation not permitted (1) This user has quite a bit of mail (50MB), but it should still work. Has anyone ran across this problem before? Thanks for your help. -Nathan Martinez
I/O error flushing output to client
Hello, This is probably not really a pop related question, cause it seems to be a client problem. It happens very seldom but sometimes I see (qpopper 4.03) stat messaes like this in the tracefile: Oct 31 08:48:37.722 2001 [26841] I/O error flushing output to client at []: Operation not permitted (1) .. .. [The I/O error message appears a few thousand times] .. Oct 31 08:48:37.990 2001 [26841] I/O error flushing output to client at []: Operation not permitted (1) Oct 31 08:48:37.990 2001 Oct 31 08:48:37.990 2001 [26841] Stats: 5 13930 5 10697211 Oct 31 08:48:37.990 2001 Oct 31 08:48:38.265 2001 [26841] I/O error flushing output to client at []: Operation not permitted (1) It seems that the client can't receive all the data, but why. There is no auxiliary information into the syslog for the relevant time. Also there occured no mail delivery. So it seems to be no locking issue. There are only a few users for which this happens. I suppose strong that it is a client-side problem. Why the I/O error message appears consecutively so many times ? Have anyone detected the same ? - oliver
Re: I/O error flushing output to client ???
At 10:51 PM -0400 6/27/01, Jack Sasportas wrote: > OK I have looked at past posts, and looked on the web with no answer to > this problem. > I noticed the few times I get this, there are literaly hundreds of > entries in the logfile. > > Can someone from Qualcomm please help out and really define the > importance of this message? Usually it can be ignored, but if you're seeing a ton of them, I'd suspect some network problem. What else do the logs say?
I/O error flushing output to client ???
OK I have looked at past posts, and looked on the web with no answer to this problem. I noticed the few times I get this, there are literaly hundreds of entries in the logfile. Can someone from Qualcomm please help out and really define the importance of this message? Thanks ! Jack ___ Jack Sasportas Innovative Internet Solutions Phone 305.665.2500 Fax 305.665.2551 www.innovativeinternet.com www.web56.net
