Date: Sun, 3 Dec 1995 00:47:40 -0600 (CST) From: Rob Snow <rsnow@txdirect.net> To: dwhite@resnet.uoregon.edu Cc: Donald Burr <d_burr@ix.netcom.com>, "Jonathan M. Bresler" <jmb@FreeBSD.org>, questions@FreeBSD.org, "Jonathan M. Bresler" <jmb@kryten.Atinc.COM> Subject: Re: pop client Message-ID: <Pine.BSF.3.91.951203004534.19139A-100000@oasis.txdirect.net> In-Reply-To: <Pine.BSF.3.91.951202215740.857F-100000@riley-net170-164.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2 Dec 1995, Doug White wrote:
> Sorry jmb if you get this multiple times.
>
> > > >Pine's remote folder support uses "imap" which may not be supported on
> > > >all systems. imap also doesn't work very well on very busy systems.
> >
> > Actually, pine (at least, 3.91) does support reading remote mail using
> > pop3. Add this in your .pinerc
>
> I did not know that. Thanks a bunch for the info!
>
> >
> > incoming-folders=INBOX_netcom {popd.ix.netcom.com/pop3}
> > ^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^
> > | |
> > (1) (2)
> >
> > (1) = set this to be the name that you want this "mailbox" to appear as
> > (2) = set this to the hostname/IP address of your pop3 server
>
> Appears to work great calling Qualcomm's pop3d server located on a Sparc.
>
> > It'll ask you for your username and password, when you read mail. Your
> > UNIX login name on your FreeBSD box must be the same as the account you
> > have on the POP server.
>
> Well, it can be different (note you can edit the username, like with
> imap), but it's not recommended since you get to backspace out and retype
> your username every time.
>
> > It seems to me, though, that the POP3 may not be working right (?) -- I
> > get a lot of erorr messages when ever I try to use it, but maybe it's due
> > to Netcom's stupid POP server(?)
>
> I'd tend to believe this one. :)
>
> Doug White | University of Oregon
> Internet: dwhite@gladstone.uoregon.edu | Residence Networking Assistant
> http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Actually I believe that the pop implementation in pine is broken. I
followed some threads earlier this year about Pine's pop implement
before I ported popclient. I don't remember what the errors were but
I believe it'll fail in use.
______________________________________________________________________
Rob Snow Powered by FreeBSD
rsnow@txdirect.net http://www.freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.951203004534.19139A-100000>