pop3 problems

[Derek Ragona]

At 12:06 PM 4/4/2007, David Southwell wrote:
>On Wednesday 04 April 2007 09:29:13 Derek Ragona wrote:
> > At 11:20 AM 4/4/2007, David Southwell wrote:
> > >On Wednesday 04 April 2007 08:57:51 David Southwell wrote:
> > > > I am trying to get pop3 working on freebsd 6.1 but am having no
> > > > success.
> > > >
> > > > mail ports installed:
> > > > [root at dns1 /usr/ports/mail/imap-uw]# pkg_info |grep mail
> > > > cclient-2004g,1     Mark Crispin's C-client mail access routines
> > > > imap-uw-2004g_1,1   University of Washington IMAP4rev1/POP2/POP3 mail
> > > > servers maildrop-2.0.2      Mail delivery agent (MDA) with filtering
> > > > abilities postfix-2.3.8,1     A secure alternative to widely-used
> > > > Sendmail [root at dns1 /usr/ports/mail/imap-uw]#
> > > >
> > > >
> > > > In inetd I have:
> > > > pop2    stream  tcp     nowait  root    /usr/local/libexec/ipop2d
> > > > ipop2d pop3    stream  tcp     nowait  root
> > > > /usr/local/libexec/ipop3d   ipop3d imap4   stream  tcp     nowait  root
> > > >    /usr/local/libexec/imapd    imapd When connections are attempted
> > > > there is no response from the server.
> > >
> > >correction the above line should read:
> > >When connections are attempted there is response from the server!!
> > >
> > > > When an attempt is made to connect to pop3 the server is found,
> > > > connection is made but there is a problem with password verification.
> > > >
> > > > Can anyone help me identify the problem. I have not been able to find a
> > > > check list to help.
> > > >
> > > > How do I get logging information for pop3?
> > > >
> > > > Thanks david
> > > >
> > > >
>
> >
> > Try telneting to that port while logged into that server.
> >
> >          -Derek\
>
>Here is my response:
>
># telnet 127.0.0.1 110
>Trying 127.0.0.1...
>Connected to localhost.
>Escape character is '^]'.
>+OK POP3 localhost 2004.89 server ready


Looks like you are getting a connection.  I don't use that imap for pop so 
I can't help much beyond this.  You could try using a different pop daemon. 
I would check the man page and see if you can run your daemon in the 
forground, not through inet and get debugging messages.

         -Derek

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.