README.md in flnews_post_proc-1.62 vs README.md in flnews_post_proc-1.70

@@ -81,11 +81,12 @@
 
 * The same conflict arises, when you have set a standard signature text and  
   would like to replace it against another, based on the newsgroup you are  
   about to post to.  
   The post-processor program sets specific signatures as configured for one  
-  or several newsgroups.  
+  or several newsgroups. You can even define a list of signatures and have
+  the program pick one from the list.
 
 * Some custom headers may serve to convey additional information to  
   interested readers of your post, like GnuPG key IDs, your language skills  
   or the like. The signature may be a better choice than custom headers.  
   You are free. I just mention face and x-face but prefer that you do not  
@@ -208,16 +209,20 @@
  
  EXAMPLE: _alt.test: "Thus spoke #\{fup_name\} on that baleful #\{fup_date\}:"_
 
 **GROUP_SIGS**  
  A signature line per Newsgroup.  
+ If a file is named instead, the program will pick randomly one signature from
+ that file. The file should contain signatures, separated by 1 empty line. 
+
  ATTN! In multi line signatures, you have to use \r\n for line breaks.
 
  CONTENT: A newsgroup or regexp per line, followed by a colon, a space and a String.  
 
  DEFAULT: As configured in flnews
 
  EXAMPLE: alt.test: _"Signature for alt.test\\\\r\\\\nsecond line"_
+ EXAMPLE: comp.*: /home/user/.my_sigs
 
 **CUSTOM_HEADERS**  
  Additional headers for the outgoing article 
 
  CONTENT: 1 line per header : a dash and space, then a String, comprising the