Subject: POP client???

From: kevin@PROBLEM_WITH_INEWS_DOMAIN_FILE (Kevin Flanagan)
Date: 14 Feb 1995 12:36:12 GMT

I hear that PINE can be configured to be a POP client, does anyone here have 
a pointer to the document that I need to set this up?

Thanks,

	Kevin M. Flanagan

---

From: chris@PROBLEM_WITH_INEWS_GATEWAY_FILE ()
Date: 14 Feb 1995 13:48:11 GMT

Kevin Flanagan (kevin@PROBLEM_WITH_INEWS_DOMAIN_FILE) wrote:
:  I hear that PINE can be configured to be a POP client, does anyone here have 
: a pointer to the document that I need to set this up?

I've done it by inserting/changing one line in my .pinerc file:
incoming-folders=POPMail {mailbox.cc.binghamton.edu/pop3}

however, i've had some serious problems when using pine as a popmail client
over a short time period (one week).  I've one user who always get's the
following message right after connecting to the popserver (this print's after
it lists some of the headers):
Bug in Pine detected: "Received abort signal".

I'm leaning towards a pine bug because eudora under windows has no problem
fetching the articles (nor does Windows 95 mail client have any problem
with them)...

Since it's an undocumented (and probably unsupported feature) I will report
this bug (but, I don't expect an answer)....
-chris peck
 binghamton university

---

From: Selcuk Ozturk <[email-masked]>
Date: Tue, 14 Feb 1995 13:12:15 EST

# I've done it by inserting/changing one line in my .pinerc file:
# incoming-folders=POPMail {mailbox.cc.binghamton.edu/pop3}
# 
# however, i've had some serious problems when using pine as a popmail client
# over a short time period (one week).  I've one user who always get's the
# following message right after connecting to the popserver (this print's after
# it lists some of the headers):
# Bug in Pine detected: "Received abort signal".
# 
I see the same problem. Especially, if there are a lot mail
to be fetched.

Selcuk

---

From: Ed Greshko <[email-masked]>
Date: Wed, 15 Feb 1995 08:06:54 -0800 (GMT)

> I see the same problem. Especially, if there are a lot mail

	I've also seen people with a size 7 foot trying to wedge it into
a size 5 shoe.  They were subsequently upset when they lost all feeling
in their feet and complained to the shoe manufacturer about their poorly
desiged shoes.

	Pine was designed as an IMAP client.  It was done so with good
reason.  Why would anyone want to shoehorn pine into a POP client when
the easiest and most benificial action to take would be to install the
imapd?  Would you attempt to force Eudora into imap mode?

						Ed
Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C

---

From: Selcuk Ozturk <[email-masked]>
Date: Wed, 15 Feb 1995 09:29:01 EST

# 	I've also seen people with a size 7 foot trying to wedge it into
# a size 5 shoe.  They were subsequently upset when they lost all feeling
# in their feet and complained to the shoe manufacturer about their poorly
# desiged shoes.
# 
# 	Pine was designed as an IMAP client.  It was done so with good
# reason.  Why would anyone want to shoehorn pine into a POP client when
# the easiest and most benificial action to take would be to install the
# imapd?  Would you attempt to force Eudora into imap mode?
# 
# 						Ed

I think that installing imapd is not the "easiest and most beneficial"
thing always. It is not the easiest thing if you don't have the root
privileges or if you have to write the program yourself to implement
it in KA9Q Nos. It is not the "most beneficial" thing either on every
platform. The most important assumption behind the imap is that the
server machine is more powerful and resourceful than the client. What
about if the reverse is true as in my case. 

I don't want to say that Pine has to be a POP client. The decision is
developement team's and I would respect it. But, the functionality
seems to be there and doesn't work correctly. Either, it should be
fixed or taken out completely. There is no sense in leaving a buggy
portion of the code in the already huge Pine executable.

Selcuk

---

From: Ed Greshko <[email-masked]>
Date: Thu, 16 Feb 1995 10:31:45 -0800 (GMT)

> about if the reverse is true as in my case. 

	I don't believe that IMAP puts much more, if any, strain on your
system resources than POP.  I don't know where you got the impression
that "server machine is more powerful" in the case of IMAP and not also
in the case of POP.

	IMHO, it would be more worth your while to implement IMAP even
if you have to port the IMAP daemon to your machine.  The time would be
well spent to acquire the added funtions of IMAP.  At least it is time not 
spent in trying to get an unsupported and undocumented feature working.  

> portion of the code in the already huge Pine executable.

	I could find no information in the documentation that stated this
this feature is available or supported.  

	I believe that the Pine Team has stated in the past *not* to expect
this undocumented feature to remain.  BTW, you'd be surprise how many
undocumented features to be found in "payware".

---

From: kevin@PROBLEM_WITH_INEWS_DOMAIN_FILE (Kevin Flanagan)
Date: 16 Feb 1995 02:36:42 GMT

chris@PROBLEM_WITH_INEWS_GATEWAY_FILE wrote:

: I've done it by inserting/changing one line in my .pinerc file:
: incoming-folders=POPMail {mailbox.cc.binghamton.edu/pop3}

: however, i've had some serious problems when using pine as a popmail client
: over a short time period (one week).  I've one user who always get's the
: following message right after connecting to the popserver (this print's after
: it lists some of the headers):
: Bug in Pine detected: "Received abort signal".

I set this up too, and get the same error..... ;'(
I'm using the Linux version and would like to get mail there too.

Thanks,

	Kevin

---

From: Selcuk Ozturk <[email-masked]>
Date: Thu, 16 Feb 1995 15:44:59 -0500

> Bug in Pine detected: "Received abort signal".

I guess I found at least one of the bugs in pop3 client code. I didn't
do comprehensive testing but at least I don't get the above message
anymore. 

Following is a diff of the necessary change to the pop3.c file
in c-client directory of pine distribution. pop3.oc is is the
original pop3.c in the distribution. This one is for the non-ANSI
pop3.c. The line numbers might be different for the ANSI one.

If you find anything else I would apreciate if let me now.

Selcuk

*** pop3.oc	Thu Feb 16 12:43:55 1995
--- pop3.c	Thu Feb 16 12:45:37 1995
***************
*** 363,370 ****
        LOCAL->buf = (char *) fs_get ((LOCAL->buflen = MAXMESSAGESIZE) + 1);
        nmsgs = strtol (LOCAL->reply,NIL,10);
  				/* create caches */
!       LOCAL->header = (char **) fs_get (i * sizeof (char *));
!       LOCAL->body = (char **) fs_get (i * sizeof (char *));
        for (i = 0; i < nmsgs;) {	/* initialize caches */
  	LOCAL->header[i] = LOCAL->body[i] = NIL;
  				/* instantiate elt */
--- 363,370 ----
        LOCAL->buf = (char *) fs_get ((LOCAL->buflen = MAXMESSAGESIZE) + 1);
        nmsgs = strtol (LOCAL->reply,NIL,10);
  				/* create caches */
!       LOCAL->header = (char **) fs_get (nmsgs * sizeof (char *));
!       LOCAL->body = (char **) fs_get (nmsgs * sizeof (char *));
        for (i = 0; i < nmsgs;) {	/* initialize caches */
  	LOCAL->header[i] = LOCAL->body[i] = NIL;
  				/* instantiate elt */

---

From: Mark Crispin <[email-masked]>
Date: Thu, 16 Feb 1995 18:51:08 -0800

This bug fix is correct.

I discovered it independently when re-reading the code in the light of 
the recent flames.

-- Mark --