From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I send a message to lots people without showing all the names?
Status: RO
X-Status: 

Put addresses and/or list from your address book in the Bcc: (blind carbon
copy) header field. You will see all the names and addresses as you
compose the message, but they are erased before arriving in other people's
INBOXes. The Bcc: header is not displayed automatically in the default
Pine configuration, so you may need to use the rich headers command
(Ctrl-R) while the cursor is in the header to expose it. 

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I have a signature automatically appended to my mail messages?
Status: RO
X-Status: 


Using your favorite text editor (e.g. Pico), create a file in your home
directory called .signature containing the text you want appended to each
message.
   
PC-Pine users should put their signatures in the file \PINE\PINE.SIG. 
   
For more details see Nancy McGough's Signature and Finger FAQ.  The 
hypertext version is at:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

The plain text version is at:

ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How can I filter messages into different incoming folders?
Status: RO
X-Status: 

                                       

Pine does not do delivery filtering. That function is done by other
programs, such as "procmail" or "filter" or "deliver" or "mailagent." 
   
Once you have set-up your delivery filtering, e.g. via the "procmail"
program, then you will have new mail arriving in several different
mailboxes/folders, in addition to your INBOX. 
   
So then the question becomes, how do you access those new "incoming
message" folders that your favorite delivery filter program has created?

One solution is to just access them the same way you access your other
mail folders.  If they are in your default folder directory (usually
$HOME/mail) then just type L to list your folders and select the folder
you'd like to view.  If they are in a different directory, for example
$HOME/mail/IN, add that directory to your folder-collections by putting
this into your .pinerc: 

folder-collections=mail/[],
        mail/IN/[],

And then when you list your folders by typing L the mail/IN directory will
be in your list. 

Another solution is to use Pine's incoming-folders variable.  With this
method you can use the Tab key to tab through new messages in all your
incoming folders.  When you are at the last new message in one incoming
folder pressing the Tab key will move you to the next incoming folder with
a new message. 

Here is part of a sample .pinerc for setting up incoming folders: 
 
incoming-folders=Art151           {warhol.art.nowhere.edu}IN/art151,
                 Art-L            {warhol.art.nowhere.edu}IN/Art-L,
                 Old-Student-Acct {fozzie.elsewhere.edu}INBOX

In this case, the pinerc entries presume that your delivery filtering
program has been configured to put mail relating to the Art151 class into
the folder "IN/art151" and mail relating to the Art-L mailing list into
"IN/Art-L". 
   
From the Folders List screen, you can then easily access those folders.
Eventually we will have a way to indicate which of these may have new mail
waiting for you, so that you don't forget that you have more than one
place to look for new mail. 
   
For a more detailed treatment of filtering, see the Filtering Mail FAQ and
the Procmail FAQ.  The hypertext version of these are available at: 

http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.html

The plain text versions are available at:

ftp://ftp.halcyon.com/pub/ii/internet/filtering_mail_faq
ftp://ftp.halcyon.com/pub/ii/internet/procmail_faq

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: Nancy McGough <nancym@ii.com>
Subject: How do I define my own headers like Reply-To and Organization?
Status: RO
X-Status: 

                                       

In Pine 3.90, and later versions, you can set Reply-To, Organization,
and other headers using the customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) To use the Where command type: w
   b) At the prompt type: customized-hdrs
   c) To Add a value type: a
   d) At the prompt type: Organization: Your Organization Name
   e) Repeat steps c and d for other headers such ast Reply-To

   Note that Pine understands environment variables so you
   can use lines like the following (if the variables are set):
      Organization: $ORGANIZATION
      Reply-To: $REPLYTO

While reading a message that you've received you can view all headers by 
typing h.  If h does not work you need to go to your configuration menu and 
set the enable-full-header-cmd variable.

While composing a message you can view all the headers by placing the cursor
in the header region and typing ^R (view rich headers).

Customized headers are not available in Pine 3.89 and earlier.

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I use Pine non-interactively, e.g., in a shell script?
Status: RO
X-Status: 

This is not currently possible.  If it were possible you could use Pine,
and your Pine addressbook, to mail people from within a shell script, at 
the end of a pipeline, etc.


From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.
Status: RO
X-Status: 

                                       

There are currently two ways to force a new mail check. 
     * Press `Ctrl-L' (Refresh Display). 
     * At the last message in a folder, press 'N' 4-5 times. 
       
   

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I read a ROT13 encoded message?
Status: RO
X-Status: 

                                       

When viewing the message, use the '|' (Pipe) command and give it the
following: 

        tr '[A-Za-z]' '[N-ZA-Mn-za-m]'

You could also write a script, maybe called unrot, that does this and then
pipe the message to the script. 

In order for the pipe command to work you need to be using Pine 3.90 or 
higher and have the enable-unix-pipe-cmd variable set.

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I eliminate the @host.domain from local addresses?
Status: RO
X-Status: 

This is not a new idea.  It's a very old idea, in fact, and just about
everyone who has ever dealt with email has had it at one time or another. 
Regretably, it has come to be recognized as a bad idea.  Here's why: 

An email address without a host name is not syntactically valid according
to RFC822.  Now, it is true that RFC822 only specifies what must be done
in messages which are transmitted over the network, and that strictly
local messages are not under RFC822's dictates. 

This means that there are two formats of email, one that conforms to
RFC822 and one that does not.  Careful efforts must be made to ensure that
the non-conforming mail format never escapes the local system onto the
network. Twenty years' of experience has shown that it is impossible to
guarantee that the non-conforming format does not escape into the network,
even in the face of traps to catch such messages on their way out and
convert them to RFC822 conforming format.  Indeed, such traps have often
contributed additional problems on their own. 

The non-conforming format is ambiguous as to what host is intended.
Although the off-the-cuff solution (and the one that everyone implements)
is ``use the local host'', numerous examples have occurred in which this
leads to wrong behavior.  For example, it may be the ``local mail center''
instead of the ``local machine which is a single-user workstation''.  Or,
if a one of the non-conforming messages escaped on to the network, it's
some remote system and we have no idea at all what system that may be! 
There's no way for the mail reader to tell; a human may infer from context
but often does so by using information that is not available to the
program. 

The Pine team has spent long (and at times heated) meetings reviewing this
issue, before coming to the conclusion (as other email groups have
independently done) that it's a no-win situation.  The policy of the email
development community for 15 years (since the RFC733 discussions) has been
to exterminate the non-conforming format by not implementing it in modern
mail tools. 

It may be feasible to implement a feature in a future version of Pine that
would suppress the display of the local host name in email addresses. That
is, the host name would still be in the file on disk, but would not show
up on the screen.  We'll consider it, but we have a large list of very
high priority tasks which must be done first. 
 

From dlm@shivafs.cac.washington.edu Thu Aug 17 17:44:08 1995
Date: Thu, 17 Aug 1995 17:44:05 -0700 (PDT)
From: Michael Ramey <mramey@u.washington.edu>
Subject: How can I use the 'ispell' spell-check program in pine and pico?
Status: RO
X-Status: 


Why use Ispell with Pine (and Pico)?
------------------------------------

 - it allows you to add words to a private dictionary so that your name
   (technical words, etc.) will not be reported as errors;

 - it offers correct spellings for misspelled words, and you can 
   select one of the offered alternatives by pressing a single key;

 - it spell checks the document from top to bottom (rather than jumping
   around in alphabetical order) so you can anticipate the next words to 
   be checked;

 - because it checks from top to bottom, you can stop the program after
   checking your reply (at the top) without checking the message you are
   replying to.


How do I use Ispell with Pine (after it is installed) ?
-------------------------------------------------------

After you have installed Ispell in pine, when you are entering a message
into the pine composer and the cursor is in the "Message Text" area of the
screen, you can press ^_ (Control-underscore), to check the spelling of
your message.  The message header cannot be spell-checked.  

Inside the ispell program, you can press the following keys: 
   ?      Help for ispell
   space  Accept the word - this time only
   A      Accept the word - for the rest of the file (message)
   I      Accept the word - and Insert it in your private dictionary
   0-9    Replace the word with one of the suggested alternatives
   R      Replace the word completely (then you enter the replacement)
   Q      Quit checking this file - corrections will be saved
   X      Exit immediately - corrections will be lost

If the spell check halts and you see "(INTERRUPT)" in the upper-left
corner of the screen, just press the <SpaceBar> to continue.  Generally
when this happens, the spell check is complete.  See 'man ispell' for 
more information on the ispell program. 


How do I install Ispell in Pine ?
---------------------------------

There are a couple ways to use Ispell within Pine; method #1 is usually
all you need to do.  It's very easy; just follow the instructions below. 


PINE -- METHOD #1:
Set your alternate-editor to ispell, then you can press ^_ 
(Control-underscore) in the composer to invoke ispell. 
To do this, follow these steps (press the "key" in each step):

 - Check to be sure that the ispell program is installed on your system,
   and use the correct directory path; at the unix prompt, enter the 
   command: 'which ispell'.  The following instructions assume output 
   from this command was '/usr/local/bin/ispell'.
 - start the 'pine' program
 - from the "M"ain-Menu of pine
 - press "S"etup
 - then "C"onfig
 - then "W"hereIs and enter 'editor' (without the ' marks) 
   and press <ENTER>
 - press "W"hereIs and <ENTER> until you find the line:
      editor = <No Value Set>
 - press "A"dd-Value, and enter '/usr/local/bin/ispell' (without 's)
   and press <ENTER>
 - you should now see:
      editor = /usr/local/bin/ispell
 - if so, press "E"xit-Config, and you are done!

You can still press ^T to use the standard pine spell-checking program
(which will -not- use your personal dictionary, and will not offer 
suggestions for correct spelling).


PINE -- METHOD #2:
Pine already checks the SPELL environment variable to locate the spell 
checking program, so you can create the following script and name it 
'spell': 

        #!/bin/sh
        ispell -l

To make ^T in pine use 'ispell' and your private dictionary: 
  - make the above script file 'spell' in your home directory 
  - make it executable: 'chmod u+x spell' 
  - set the environment variable SPELL: 'setenv SPELL $HOME/spell' 
    (include this command in your .profile, .cshrc or .login file) 

Now, when you press ^T in pine, you will execute the ispell program, and
it will recognize words stored in your private dictionary.  The screen
display will look like pine is using the standard spell-checking program,
except words will be checked from top to bottom in the message, rather
than in alphabetical sequence.  This method does not allow you to Insert
words into your private dictionary.  However, this might be useful with a
central script file (setenv SPELL ...) and a central private dictionary
(ispell -p ...) to provide a common private dictionary for an entire
workgroup.  The manager could add items to the private dictionary; other
people could use the private dictionary (^T), but they could not change
it. 


PICO:
To use ispell with pico (the stand-alone editor):
 - implement the 'ispell' program via ^T (CTRL-T) (using the script file) 
   in addition to implementing it via ^_ (CTRL-_) (using pine "S"etup, 
   "C"onfiguration as described above).

Use ^T in pico to use the ispell program and your private dictionary 
(but without the ability to add words to the dictionary).  You cannot 
use ^_ in pico; it is an "Unknown Command".  You can use ^T-ispell in 
pine also, but why bother when ^_ works better. 


[MRamey] 

