Hi Randall,
thank you for answering.
Ihe problem is that I don't get any messages back by qpopper. So I have
to do something.
My old Qpopper 2.5.? did not do this error.
Is there a way to suppress this error message?
Bye
Marcus
> It sounds like that one client does not issue QUIT before closing the
> connection. That's a violation of RFC 1939, and Qpopper reports it
> as an error (unexpected EOF). If so, you can ignore it or try and
> get the client fixed.
Randall Gellens wrote:
>
> At 2:47 AM +0200 8/23/01, Marcus Schopen wrote:
>
> > Hi there,
> >
> > checking my POP Account with Horde IMP Client (www.horde.org) produces
> > the following error in /var/log/mail:
> >
> > Aug 23 02:03:54 julia popper[6652]: (null) at localhost (127.0.0.1):
> > -ERR POP EOF or I/O Error
> > Aug 23 02:03:54 julia popper[6652]: I/O error flushing output to client
> > at localhost [127.0.0.1]: Operation not permitted (1)
> >
> > Setting "chunky-writes = tls" in all configuration files as discribed in
> > the FAQ does not help.
> >
> > Changin "localhost" to the Server Domain does not help either.
> >
> > I'm using:
> > Qpopper 4.0.3 on Linux
> > IMP, Version 2.2.6 and Horde, Version 1.2.6 as Client.
> >
> > Checking POP with Netscape or fetchmail (also ssl) works fine.
> > Checking other POP3 Servers with the same Horde IMP client works also
> > fine too.
> >
> > So I think it's a problem of my Qpopper.
> >
> > Any help would be great!!!
> >
> > THANK YOU
> > Marcus
> >
--
_____________________________________
(0> Marcus Schopen
//\ P.O. Box 10 25 25
V_/_ 33525 Bielefeld, Germany
ICQ#120991527
_____________________________________
Live as variously as possible
