----------------------------------------
 randomsig v1.9.10 KNOWN BUGS AND ISSUES
----------------------------------------

-  With the MAIL_QUOTING feature turned on and if you are quoting the
  same mail that you are recieving, it is possible to get stuck in a
  situation where you keep adding the same username or different usernames
  to the end of the same signature.  This will be fixed in the future when
  randomsig will be written to ignore anything after a '-- ' sequence in
  an e-mail message.

-  It might seem like randomsig in named pipe mode doesn't work with Pine
  but the real problem is that Pine does not do the proper thing with
  signature files that are named pipes.  Pine ends up stat'ing the file,
  not caring that it is a named pipe and is zero bytes long it attempts
  to read 0 bytes from the named pipe, which ends up sending a SIGPIPE,
  which would normally kill the program but I wrote a signal handler that
  catches it and sleeps for a fraction of a second.  You have to try
  composing a message a few times to get it to work the first time around.
   This problem has been discussed for several years on some Pine mailing
  lists and newsgroups without getting fixed.  Sigh.

-  Right now if you change the configuration so that you remove a file from
  the config to be read for potential random lines, the lines will stay around
  within the program after sending a HUP signal to the program.  You will
  have to restart the program if you want to get rid of the old lines.  This
  will probably be fixed in the 2.0 release.

**  Please let me know if you find any bugs by sending email to suso@suso.org **