Subject: Re: 3 meg file hangs in pine

From: Pete Bellacera <[email-masked]>
Date: Thu, 16 Mar 1995 10:05:52 -0500 (EST)

Hi,

On 13 Jan 1995, Charles Lawrence wrote:

> When reading a large 2.5meg+ file into a pine message I hang and have
> to kill pine.  I am able to read in the same file fine in mail.  Is there
> a system wide pine option I need to set?

I have a similar problem in that when a message of that magnitude is 
in the INBOX pine hangs while building the index. Does anyone have any 
suggestions?

I am new to this list and hope this is not a FAQ. I did look around in the
Pine home page, the FAQ page and the pine-info archive and didn't see
anything. 

Thanks,
Pete Bellacera
The American Physical Society

---

From: Don Sugarman <[email-masked]>
Date: Thu, 16 Mar 1995 10:29:40 -0500 (EST)

On Thu, 16 Mar 1995, Pete Bellacera wrote:
> On 13 Jan 1995, Charles Lawrence wrote> 
It is my understanding that e-mail of that size is frowned upon; although 
I have successfully sent 2MB+ files before being politely warned.

What you can do is to split (UNIX split command) the file into bite-sized 
pieces (200K or so) and email each in a separate message.  I just ran
  split filename.ext
Results in 
  xaa   285k
  xab   160k
Since the orignal file was about 445k.  You can specify the output file 
names and max size, but I didn't look that up.  Check the man page for 
more info.

The recipient will have to save each file and recombine using cat:

  cat x?? > filename.ext

Be sure to minimize your problem by first zipping, gzipping, compressing, or
otherwise making the file as small as possible.  There are probably easier
ways, but this will solve your problem for now. 

Don Sugarman
[email-masked]

---

From: Pete Bellacera <[email-masked]>
Date: Thu, 16 Mar 1995 12:31:43 -0500 (EST)

On Thu, 16 Mar 1995, Don Sugarman wrote:

> What you can do is to split (UNIX split command) the file

That's a good point. However, my problem is with *receiving* such files
and the resulting hangup in displaying the index. My organization
routinely gets large, unsolicited mail messages as part of our journal
publishing operation. It wouldn't be practical to ask the senders to split
their files. 

The standard Unix mail programs (e.g. ucb/mail or its System V workalike
mailx) seem to work but we would much rather use pine. Is there anything
that can be done to improve pine's handling of large incoming messages? 

Thanks,
Pete.