Subject: Why is searching for subject keywords in pine 3.91 so SLOW??

From: MagNET Supervisor <[email-masked]>
Date: Sat, 18 Feb 1995 13:24:35 -0700

Hello...

Is there a way to improve the performance of Pine's keyword subject 
string seach? It seems like it goes through ALL messages in a specific 
newsgroup, not just the unread ones...

Leave e-mail to [email-masked]

Thanks

--Guy

---

From: Deborah Leah Blackner <[email-masked]>
Date: Sat, 18 Feb 1995 22:39:08 -0600

Hi!

Sorry if I am posting this to the wrong place. but ....

Could someone please tell me the steps to uuencode a binary file (it's a 
.gif to be specific) and then attach it to a pine mail message. I have 
read the cryptic man page on uuencode and tried to follow the directions 
given, but have been unsuccessful.

What I need is a step by step, hold my virtual hand, type of direction.

UNIX and I are grudgingly becoming acquainted, but we are not quite on 
speaking terms yet.

THANKS!

---

From: "Brian E. Sherman" <[email-masked]>
Date: Sat, 18 Feb 1995 21:56:11 -0800 (PST)

On Sat, 18 Feb 1995, Deborah Leah Blackner wrote:

> .gif to be specific) and then attach it to a pine mail message. 

I use the following commands on SCO & Sun Unix systems.
	1. cd to your home directory 
  		cd 
	2. copy the .gif file to your home directory
		cp /usr/tmp/your.gif .
	3. compress the file 
		compress your.gif   
		(Note: File name has .Z appended to it)
	4. check permissions on the file & change as necessary
		ls -l your.gif.Z      (to check)
		chmod 666 your.gif.Z  (to change)
	5. uuencode the file
		uuencode your.gif.Z your.gif.Z > encoded.fil 
		(this command creates a file called "encoded.fil"
		 when the file is uudencoded it will be called your.gif.Z)
	6. Start pine
		select c (compose message)
		after entering the To: e-mail address  go to the
		attachment: field and key in the name of the file you 
		wish to send  ie: encoded.fil
		pine responds with  
		1. "1. /home/username/encoded.fil  (63 KB)"
	7. Finish composing message and send.

	I usually include the following in the message:
	"The attached file is an uuencoded compressed file"
	
	The person getting the message & file should know how to detach, 
	and uncompress the file before using the uudencode command.
	Hope this helps.  If you have trouble send me an E-mail.
 *-------------------------------------------------------------------------*
 |        _///_  "You can make a program fool-proof but then someone comes |
 |        (o o)        along and makes a better fool"  Murphy's Law        |
 *-----ooO--~--Ooo-------------------------------------*-------------------* 
 | Newport/Layton Home Fashions,Inc. - MIS/EDI Manager |
 |    E-Mail: Brian E. Sherman <[email-masked]> |
 | snailMail: 1420 NW Lovejoy St.      *---------------*
 |            Portland, OR  USA  97209 |  Opinions Expressed Here Are All Mine.
 |     Voice: 503-222-3847  Ext. 234   |  
 |       Fax: 503-222-7465             |  
 *-------------------------------------* 
       (oo)   (oo)

---

From: Don Sugarman <[email-masked]>
Date: Sun, 19 Feb 1995 11:21:45 -0500 (EST)

I think the Deborah's original request implies that the recipient cannot 
read the MIMEd message, hence the need to uuencode.
I've annotated Brian's message (everyone's an editor, right? <g>)

> 	2. copy the .gif file to your home directory
Not sure why he thinks the gif file in in /usr/tmp.  To generalize:
                cp <source_path>/your.gif .

> 		1. "1. /home/username/encoded.fil  (63 KB)"

At this step, I would ctrl-r the file into the message body, rather than
attaching it.  MIMEing a uuencoded file buys you nothing, since it is
already ASCIIfied.  (Note that the first line of the uuencoded file is
"begin 666 your.gif.Z", so uudecode will know how to name the file, as
Brian mentioned above. 

> 	Hope this helps.  If you have trouble send me an E-mail.
I think Brian meant uudecode first, then uncompress the file.

But in this case, the recipient should 
Option 1 -
 save the message to a file, e.g., message.uu, then execute uudecode: 
     uudecode message.uu
 which will produce a reconstituted your.gif.Z, which is uncopressed
     uncompress your.gif
Option 2 -
 pipe the message to uudecode from the mail program 
     | uudecode
 if your recipient's mail progam supports that.

Don Sugarman
[email-masked]

---

From: "Michael C. Newell" <[email-masked]>
Date: Thu, 23 Feb 1995 15:54:10 -0500 (EST)

> given, but have been unsuccessful.

Assume the file is called "picture.gif" and it is in your home 
directory.  Do the following:

  1. UUEncode the file via the command

	uuencode picture.gif picture.gif > picture.uue

  2. Start up Pine.

  3. Compose your message.

  4. Move to the end of the message (include the signature if any -
     go all the way to the end.)

  5. Press the CONTROL-R key sequence.

  6. Supply the name "picture.uue" to the prompt asking for the file
     name to include.

  7. Press CONTROL-X to send the message.

  8. Exit Pine.

  9. Delete the uuencoded file via the command

	rm picture.uue

The command in Step 1 encodes the file so that it may later be re-incarnated
under the same name.  The first parameter is the name of the input file.  The
second parameter is the name that uudecode will use when the file is
re-created (generally they are the same).  The "> picture.uue"  re-directs
the output of the uuencode command to the file "picture.uue"  (you can use
any name that makes you happy - it's just a temporary file anyway.) As with
most Unix things there are alternate ways of doing the same thing, but I find
this is the simplest. 

You don't even need to invoke Pine to send it - if all you want to do is 
send the file without including a message, try the command

  uuencode picture.gif picture.gif | mail -s "Subject text" user@host

This will encode the file and mail it in one step to the target user 
("user@host") with the subject "Subject text" and the body containing 
only the encoded file.

To extract and decode the file, do

  1. Launch Pine.

  2. Highlight the message at the index or read it.

  3. Enter the CONTROL-E combination to extract the message to a file.

  4. Supply any file name at the prompt; generally I use "mcn" because
     they are my initials and easy to type... :{)

  5. Exit Pine.

  6. Enter the command

	uudecode your-file-name

     where "your-file-name" is the name of the file you supplied in
     Step 4.

UUDECODE will create a file with the same name as the second argument 
supplied on the uuencode command line.  This can be annoying at times, 
because sometimes you don't know what the encoded file name was.  The 
easiest way to find that out is to do the command

	grep begin your-file-name

where again "your-file-name" is the name you saved the file as.  You'll 
see a line something like

	begin 666 new-file-name

where "new-file-name" is the name uudecode will use when it rebuilds the 
file.  In some Unix systems (Sunos for example) if there are spaces in 
the file name only the first part is used; for example if you see

	begin 666 My file

the new file will be called "My".  The number is the protection mode the file
will be created with; generally it's 666 [anyone can read and write the
file], 755 [the owner can read write and execute the file, others can read
and execute it], or some other combination.

You need to be a bit careful using uudecode on files sent by other 
people; for example, if the begin line looks like

	begin 755 .login

the decoded file will replace your .login file (with possibly un-amusing 
results the next time you log in...)  Remember - on the Net, ALWAYS look 
a gift file in the mouth! :{)  [Note my forebearance in working ".gif" 
into this...]

Hope this helps,

Mike

+--------------------------------------+------------------------------------+
|Mike Newell                           | The opinions expressed herein are  |
|NASA Science Internet Network Systems | my own, and do not necessarily     |
|Sterling Software, Inc.               | reflect those of the NSI program,  |
[email-masked]                | Sterling Software, NASA, or anyone |
|+1-202-434-8954                       | else.                              |
+--------------------------------------+------------------------------------+