Subject: Problem with PC-Pine 3.91 Configuration

From: [email-masked] (James Thomsen Wong)
Date: 22 Oct 1994 05:10:35 GMT

Dear netters,

I'm trying to set up my PC Pine 3.91 from my home SLIP acct.
I was trying to connect to uclink.berkeley.edu, in which this is 
where all my mails go to, but then it says something like:
 "Can't connect to uclink.berkeley.edu, 143 : Refused 10061"
 "No folders opened."

Part of my Config is:
user-domain = uclink
smtp server = uclink
inbox path = {uclink}INBOX
folders-collection:*{uclink}mail/[]

>From talking to the root of uclink, they don't have IMAP server 
and I think they recommend me connecting to POP server first
then map that to Pine...I don't know how though.

Can someone tell me what I did wrong in the config? All my
mail folders, including inbox is in the mail directory in my home
directory.

Thanx and I appreciate your help!

PS: Please e-mail me for suggestion.
James

*****************************************************************************
"When God created water, he used everything from H to O.
                                        --- Dollyism October 1994
*****************************************************************************
                                                 James Thomsen Wong
                                            Univ. of California, Berkeley
                                                      o-<--<

---

From: "M. J. O'Neill" <[email-masked]>
Date: 22 Oct 1994 16:53:32 GMT

> folders-collection:*{uclink}mail/[]

Hi!

Try using your complete domain name and complete paths.

My config works fine as follows:

user-domain        = clark.net
smtp-server        = clark.net
nntp-server        = news.clark.net
inbox-path         = {clark.net}/opt2/mail/mjoneill
folder-collections = Saved Mail c:\trumpet\pine\savemail\[]
                     ClarkNet {clark.net}/opt2/usr/mjoneill/mail/[]

I also ran into problems because of a line I added to the 'hosts' file
in my trumpet directory (I had my host's name in place of my own PC's
name).  Until I corrected this, I got the EXACT same error message.

Mike