On 10/21/2012 10:36 AM, Paul Quinn -> Nicholas Boel wrote:   
    > Hi! Nicholas,   
      
    > In a message to All you wrote:   
      
    DD>>> I have noticed that in the latest update of Thunderbird (16.01) I   
    DD>>> need to use "Followup" not "Reply" to respond in Fidonet   
    DD>>> echoes.   
      
    NB>> Doesn't seem as though I can get that to work either. Would someone   
    NB>> (multiple even) be so kind as to paste their jamnntpd.config so I can   
    NB>> compare it to mine, and see if I'm using anything I shouldn't be?   
      
    > First up, I'd suggest a re-compile, or, even a reversion to the Johan   
    > Billing original executable (is there one?... I can't even find the   
    > Windows one now!  Bugger!).   
      
    > I had some weirdnesses with a Ubuntu-compiled doover which was fixed by   
    > turfing Xubuntu 11.10 to the bit-bucket.  I then installed an old rev of   
    > Puppy linux, and reverted to a pre-compiled executable for Puppy.  The   
    > previous configs & messagebase were used again (the entire Fido   
    > directory tree was backed-up to a .tar), with a change of executable   
    > only, and, the weirdness went away.   
      
   Mind if I give your binary a shot? You can email it to accessd@pharcyde.org   
   (which should be a REPLYADDR kludge in this message). I'm using Gentoo on the   
   server side, and Sabayon Linux on the posting side (binary Gentoo fork,   
   basically).   
      
    > Anyhow, here's a copy of my jamnntpd.config file in the vBox system (I   
    > gotta change the origin sometime[smack!])...   
      
   I guess what I have in the jamnntpd.config doesn't really matter, it's just   
   options, and not anything that would really cause the errors I'm having.   
   Though I'm not sure where you got the commented version of the config file,   
   when I used "jamnntpd -create" to create my config file, there was absolutely   
   no comments in it, so I had to check the ReadMe.txt.   
      
   I believe I'm using the original 1.0 zipfile. Are you using one of the 1.0   
   betas? It looked to me nothing was really changed in the betas, except for a   
   few minor things added by Bj”rn. Though I could be wrong there.   
      
    > === begin ===   
    > # Main config of JamNNTPd   
    > #   
      
    > # -port 119   
    > -port 5000   
    > #  Set the port where JamNNTPd listens for connections. The default is   
    > 5000.   
      
      
    > #xxxx modified 10/03/2012   
    > -max 20   
    > #  The maximum allowed number of connections at one time. The default is 5.   
      
    > -groups "/opt/ftn/fido/jamnntpd/jamnntpd.groups"   
    > -allow "/opt/ftn/fido/jamnntpd/jamnntpd.allow"   
    > -users "/opt/ftn/fido/jamnntpd/jamnntpd.users"   
    > -xlat "/opt/ftn/fido/jamnntpd/jamnntpd.xlat"   
    > #  Use these to override the default locations of the config files.   
      
    > -logfile "/opt/ftn/fido/logfiles/jamnntpd.log"   
    > #  Use this to override the default location of the log file.   
      
    > #-noecholog   
    > #  Disables echoing of log messages to the console window.   
      
   Everything above is the same, except I have 'max 10'. I have noecholog enabled   
   so as to not log to my console window. Also, when I created my config file, it   
   didn't have the '-' before all the options, so mine reads:   
      
   noecholog   
   readorigin   
      
   etc..   
      
    > -readorigin   
    > #  Get address from the Origin line instead of the OADDRESS field of the   
    > JAM   
    > #  message header. This option makes JamNNTPd slower, but may be useful if   
    > #  your tosser does not set the OADDRESS field.   
      
    > -noencode   
    > #  JamNNTPd by default MIME-encodes headers with non-ascii characters.   
    > If you   
    > #  use this option, JamNNTPd will instead send the headers as plain   
    > 8-bit text.   
      
    > -strictnetmail   
    > #  Makes JamNNTPd use strict article counters for netmail messages.   
    > Normally   
    > #  JamNNTPd uses article counters that include all messages, not only those   
    > #  that the user is allowed to read. That behaviour is much faster, but may   
    > #  cause your newsreader to indicate the presence of new messages in the   
    > #  netmail area even when there are only messages for other users. Using   
    > this   
    > #  option will make JamNNTPd slower, but speed seems to be acceptable for   
    > #  small netmail areas with up to 1000 messages. Users will never be   
    > allowed   
    > #  to actually read netmail messages of other users even when this   
    > option is   
    > #  not used.   
      
    > -def_flowed on   
    > -def_showto on   
    > #  Sets the default of the flowed and showto settings (if no default is   
    > #  specified on the commandline, both will be on by default) (on/off)   
      
    > #nostripre   
    > #  JamNNTPd normally strips "Re:" from subject lines of followups. Use   
    > #  this option if you want to retain the "Re:".   
      
   I have this enabled. I'm sure it doesn't make a big difference in this matter,   
   though.   
      
    > #-notearline   
    > #  JamNNTPd normally puts the information from the X-Newsreader or   
    > User-Agent   
    > #  header field in the tearline of posted messages. This option disables   
    > this   
    > #  behaviour and leaves the tearline blank.   
      
    > -noreplyaddr   
    > #  JamNNTPd normally adds a REPLYADDR kludge with the e-mail address of the   
    > #  sender in posted messages. Use this option if you don't want REPLYADDR   
    > #  kludges. See also see section 6.4 below.   
      
   I have this commented. I assumed this was to add in your email address, so   
   someone could actually reply to you via email or netmail, or something.   
      
    > #xxxx modified 14/10/2012   
    > # -notzutc   
    > #  JamNNTPd normally writes the timezone into a TZUTC kludge when a message   
    > #  is posted. You can use this option if you don't want to create TZUTC   
    > kludges.   
      
    > #nocancel   
    > #  Disallows the cancelling (deleting) of messages by the users.   
      
    > -smartquote   
    > #  The quoting style of most newsreaders is different from traditional   
    > fidonet   
    > #  software. If you enable this option, JamNNTPd will try to change any   
    > quoted   
    > #  lines to fidonet style. This means that it will try to insert the   
    > initials   
    > #  of the person you reply to before the '>' character and also that it   
    > will try   
    > #  to compound multiple generations of quotes, i.e. "AA> BB>" will be   
    > changed   
    > #  into "BB>>".   
      
    > #xxxx modified 2/2/2012   
    > -origin "Paul's Xubuntu vBox - Maryborough, Qld, OZ"   
    > #  Normally JamNNTPd uses the text found in the Organization header line as   
    > #  the Origin line text in posted messages. You can use this switch to   
    > #  override the Organization line and set your own origin for all posted   
    > #  messages.   
      
    > guestsuffix "[guest]"   
    > #  If desired, JamNNTPd can add a suffix to posts from unauthenticated   
    > users.   
    > #  To activate that feature, specify the suffix here.   
      
    > -echomailjam /opt/ftn/fido/sema4dir/sendmail.sem   
    > #   If you specify a filename here, JamNNTPd will write a line to this file   
    > #   with the messagebase and message number for each message that is   
    > posted.   
    > #   The file follows the ECHOMAIL.JAM format supported by some tossers.   
      
   I don't use the above two options. I'm most likely not going to allow guest   
   users, and I never bothered with echomail.jam in HPT either, so why do it   
   here. :)   
      
    > #-debug   
    > #  If this option is used, JamNNTPd will print all sent and received text   
    > #  to the console window. Useful for testing.   
    > === end QUINNS~1.PRE ===   
      
   Otherwise everything is basically the same.   
      
   As for jamnntpd.allow I use one line with an asterisk.   
      
   --- jamnntpd.allow begin   
      
   # ... Just write "*" alone on a line to allow all IP numbers.   
   # If no access groups are configured, users connecting from that IP   
   # will not be able to access any newsgroups unless they log in.   
      
   *   
      
   --- jamnntpd.allow end   
      
   --- jamnntpd.groups begin   
      
      
      
   JAMNNTPD	F	1:154/10.1	/mystic/msgs/jamnntpd   
      
   --- jamnntpd.groups end   
      
   and jamnntpd.users is just myself right now, with two asterisks for read and   
   posting access.   
      
   So as of right now, Thunderbird seems to be pulling in all the messages, while   
   jumbling up some of the Subjects for one.. Second, I have to use To:  on   
   the first line of the body of the message to successfully reply to anyone..   
   and third, Thunderbird is adding it's own ">" for quoting, and even with the   
   "smartquote" option enabled, it doesn't seem to be changing anything..   
      
   --    
   Nick   
      
   --- Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120923 Thunderbird/15.0.1   
    * Origin: The Pharcyde -- Purgatory Newsreader in Wisconsin (1:154/10.1)