Subject: Re: Using Pine 3.94 with POP3

From: "Jason Englander" <[email-masked]>
Date: Wed, 1 Jan 1997 10:09:32 -0600

Jint,

> I haven't tried it yet, but in one of the Linux groups someone posted:
> 
> 	inbox-path={<insert POP3 server>/110}INBOX
> 
> Basically the same as what you posted, except I don't see a field named 
> "Remote Inbox" in pine's configuration menu. I wonder if adding that line 
> directly into the .pinerc and setting inbox-path to a local mail folder 
> would allow pine to use both POP3 and local mail successfully.
> 
> The thing I fear about setting the inbox-path to the POP3 is that pine 
> will probably scream that the inbox doesn't exist if you go into it while 
> your PPP connection is down.
> 
> Once again, I didn't try this yet, but I will when I get home.

If you leave the 'normal' inbox the way it is (reading mail from 
/usr/spool/mail/username), but you enable incoming folders (one of 
the many checkboxes in Pine's setup), then you add that part under 
the Incoming-Folders= field.

  Incoming-Folders="POP Account #1" {mailhost.interl.net/pop3}INBOX,
	"POP Account #2" {mail.otherisp.com/pop3}INBOX,
	"POP Account #3" {mail.1234.org}INBOX

This way, using incoming folders, you can still have the INBOX folder 
in Pine, _and_ a folder to read mail directly from the pop3 server.  
If you use the format that you saw in that Linux newsgroup, your 
INBOX folder (now /usr/spool/mail/username) will be replaced by 
{mail.yourisp.com/pop3}INBOX and it will bitch when you start Pine 
that it can't access that folder.

As far as using {<mailserver>/110}INBOX instead of 
{<mailserver>/pop3}INBOX - you might want to go with the 2nd one.  
Not every ISP uses port 110 for pop3.

  Jason
--
Jason Englander
InterLink L.C.
[email-masked]

---

From: Jint <[email-masked]>
Date: Wed, 1 Jan 1997 17:49:43 -0800 (PST)

> Not every ISP uses port 110 for pop3.

Thanks for the very informative reply, Jason. :)

I never did get around to try to access my POP3 with Pine since I ended
up downloading fetchmail and using that instead. Fetchmail picks up the
mail from my POP3 and then you can do whatever you want with it after
that. I'm going to be doing procmail stuff and routing mail to different
inboxes, so fetchmail seems to be the better solution for me.

I haven't configured it in daemon mode yet, so far I've just been
executing it manually as such:

	fetchmail -u <username> -p POP3 <pop3 server>

By default, it puts the mail that it fetches into
/var/spool/mail/<username of person executing fetchmail>

Then I fire-up pine and read my mail. :)

I'd recommend fetchmail for anyone accessing mail over a PPP connection
from a *NIX box. It comes with very clear docs and practically sets itself
up.

Where to get fetchmail:
ftp://ftp.ccil.org/pub/esr/fetchmail

Cheers!
_____________________________________________________________________
[email-masked]                 Jint           Systems Analyst for
[email-masked]          ~~~~            Paramount Pictures
                       |-| () |_ |_ `/ \/\/ () () |)

---

From: [email-masked] (Charles Hope)
Date: 4 Jan 1997 06:33:25 GMT

Jint ([email-masked]) wrote:
: On Wed, 1 Jan 1997, Jason Englander wrote:
: > 
: > If you leave the 'normal' inbox the way it is (reading mail from 
: > /usr/spool/mail/username), but you enable incoming folders (one of 
: > the many checkboxes in Pine's setup), then you add that part under 
: > the Incoming-Folders= field.
: > 
: >   Incoming-Folders="POP Account #1" {mailhost.interl.net/pop3}INBOX,
: > 	"POP Account #2" {mail.otherisp.com/pop3}INBOX,
: > 	"POP Account #3" {mail.1234.org}INBOX

I haven't tried this. I have pointed my entire inbox at the POP server by 
setting inbox-path={host/pop3}inbox. But then I either have to choose 
between by POP server or my local one, and not both. This method you have 
here is better (if it works for me.)

How can you send outgoing mail through the POP server using Pine 3.91? 
Even with the method I have been using, still mail gets sent from my own 
account, and not the POP server. 

Thanks!

Charles