-----BEGIN PGP SIGNED MESSAGE----- On Tue, 10 Nov 1998, Kent West wrote:
> Is there a[n easy] way to set up your signature file in Pine so that a > different fortune is sent with each signature? (I've come to realize that > with Linux, yes, it's possible, because you can do just about anything, > but is it _easily_ done?) Yes, it can be done, and it's not hard at all. I do something similar, except instead of using fortune, I have a directory with a bunch of different text files. Each text file contains 1 sig. I wrote a pine filter to automatically append a random file from this directory to my outgoing messages. This gives me a bit more control over what goes out, as opposed to using fortune, where you never know what you'll get. Here is a one line script that might work for your purpose: #!/bin/sh fortune >> $1 $1 is the name of a temp file that contains the body of your outgoing message. So you can see how the script will simply append the output of fortune to your message. Now you need to tell Pine to use that script as an outgoing filter. In Pine's config, find the "sending-filter" option, and specify the filename of your script followed by _TMPFILE_, which is the $1 option that your script expects. You'll also want to check compose-send-offers-first-filter if you'd like your script to be the default filter, offered whenever you send a message. note that you won't see one of my sigs attached to this message. I have sent it through a different filter to PGP sign it. noah PGP public key available at http://lynx.dac.neu.edu/home/httpd/n/nmeyerha/mail.html or by 'finger -l [EMAIL PROTECTED]' -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNkjxO4dCcpBjGWoFAQELiwP+JwSy3ddzu6k1Pj+6KTgaZWlmtXvQ4TDh 3V7KGULAWMghj4nb+sCfpLnF4lKdcvGT6Tgk+gXhw/+3WoSJO6HVahfQ+QG3Zv7A V1Kb6faiR5r14riQ5B+cp1BNzsGg40He6sf0bC7+z1T44/CsSp4u0Au+b44i0hKI W+9PkpQ7A0c= =uStf -----END PGP SIGNATURE-----
