On Thu, Jan 03, 2002 at 07:15:42PM -0500, Bernd Prager wrote: > > > I just recently imstalled version 4.0.3 on RedHat 7.0, kernel > 2.4.16., > > > openssh-3.0.2p1-1. > .. > > > popper[22175]: (null) at 192.168.2.113 (192.168.2.113): -ERR POP EOF > > > or I/O Error > ... > > This is weird enough that I think we need a few more facts. > > > > You are logging into what port number with ssh - port 110, or the > > standard port number (22)? > > > > And the syslog message is going where - to the console, or to the ssh > > window you're trying to log in with, or into one of your usual system > > logs? > > > > It sort of sounds like you *might* have set qpopper up in inetd or > > xinetd on port 22 instead of the usual port 110 for POP or 995 for > > POP-SSl. > > I get the local messages in Outlook Express (Win2K): > Unable to logon to the server using Secure Password Authentication. Account: > 'Home', Server: 'mail.prager.ws', Protocol: POP3, Server Response: '.', > Port: 110, Secure(SSL): No, Error Number: 0x800CCC18 > The other error message above appears in /var/log/maillog on my Linux box.
Could you please post your inetd or xinetd command line configuration for qpopper (and your config file if any)? It sounds like you have port 110 set up for SSL only, and Express is trying to use it for clear-text POP (or maybe vice versa.) If you want to support unconditional SSL for POP, the more conventional port to run that on is 995. So ssh doesn't really enter into the picture? -- Clifton -- Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED] WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
