Hi! Nick,   
      
   On Sun, 21 Oct 12, you wrote to me:   
      
    NB>>> I can compare it to mine, and see if I'm using anything I shouldn't   
    NB>>> be?   
      
    >> 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.   
      
    AD> Mind if I give your binary a shot?   
      
   Wilco.  I'll send both if I still have the Ubuntu one.  I'm upstairs on my   
   wife's PC for the moment.   
      
    AD> I guess what I have in the jamnntpd.config doesn't really matter,   
    AD> it's just options, and not anything that would really cause the   
    AD> errors I'm having. Though I'm not sure where you got the commented   
    AD> version of the config file, when I used "jamnntpd -create" to create   
    AD> my config file, there was absolutely no comments in it, so I had to   
    AD> check the ReadMe.txt.   
      
   Wow.  Yeah, I see what you mean.  I configured most of this (for Windows)   
   about six & a half years ago.  I probably constructed the config file from the   
   ReadMe.txt file.  You know, "from the horse's mouth" sort of thing.   
      
    AD> I believe I'm using the original 1.0 zipfile. Are you using one of   
    AD> the 1.0 betas?   
      
   Nope.  I've left them be, where they are.   
      
    >> === begin === # Main config of JamNNTPd   
    >> #xxxx modified 10/03/2012 -max 20   
    >> #  The maximum allowed number of connections at one time. The   
    >> default is 5.   
      
    AD> Everything above is the same, except I have 'max 10'.   
      
   That was changed on recommendation by Björn as I was having some 'max users'   
   problems with the Windows server.   
      
    >> -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.   
      
    AD> I have this commented. I assumed this was to add in your email   
    AD> address, so someone could actually reply to you via email or netmail,   
    AD> or something.   
      
   Yep, that's the intent.  Conversely, I just have a philosophical POV about   
   protecting users from spammers, and therefore I prefer to exclude that info   
   from my server's news posts.   
      
    >> guestsuffix "[guest]"   
    >> -echomailjam /opt/ftn/fido/sema4dir/sendmail.sem   
      
    AD> I don't use the above two options. I'm most likely not going to allow   
    AD> guest users, and I never bothered with echomail.jam in HPT either, so   
    AD> why do it here. :)   
      
   Well, 'echomail.jam' setting is basically used as a semaphore file for the   
   linux system(s).  A cron job runs every 30 minutes, looking for such things.    
   On my Windows server, my mailer Radius sees them immediately and runs-up a   
   sendmail type BATch (it happens pretty much straight after the user hits   
   [Send] in their news reader).   
      
   The guest setup worked recently for a new user.  It surprised the geebies out   
   of me!  :)   
      
    AD> As for jamnntpd.allow I use one line with an asterisk.   
      
   Here's mine:   
      
   === begin JAMNNT~1.ALL ================================   
   # Allowed IP numbers for JamNNTPd   
   #   
   # Syntax:   
   #   
   #      
   #   
   # "*" can be used as a wildcard. Everything after "*" is ignored, i. e.   
   # 127.0.*.1 is equivalent to 127.0.*. Just write "*" alone on a line to   
   # allow all IP numbbers.   
   #   
   # If no access groups are configured, users connecting from that IP will   
   # not be able to access any newsgroups unless they log in.   
   #   
   # "*" means "all groups" and "-" means "no groups".   
   #   
      
   ##  Message Group Name   
   #   ------------------------------   
   #   A   TREK/DR WHO/BLAKE7/RED DWARF/BABYLON5/STARGATE   
   #   B   VIRUS/ANTI-VIRUS STUFF   
   #   C   Moderators echo < ------------------------ look!   
   #   D   Adult/General chat stuff   
   #   E   Sound stuff   
   #   F   COMMS/TERMINAL/Modem stuff   
   #   G   DOS stuff   
   #   H   Windows stuff   
   #   I   Netmail & Syslogs group!! < -------------- look!   
   #   J   Visiting sysops echoes < ----------------- look!   
   #   K   IBM/CLONE/General computer TECH   
   #   L   RELIGIOUS STUFF   
   #   M   OFFLINE MAIL STUFF   
   #   N   ALTERNATE OPERATING SYSTEMS   
   #   O   Mystic BBS local message areas   
   #   P   COOKING/HOMEMAKER/LAND USERS/GARDENING   
   #   Q   LANs/NETWORKING/PACKET RADIO/ELECTRONICS   
   #   R   Australian sysops echoes < --------------- look!   
   #   S   FOR SALE/TRADING   
   #   T   GENEALOGY   
   #   U   BUSINESS RELATED   
   #   V   COMPUTER PROGRAMMING   
   #   W   MEDICAL & DISABLED RELATED   
   #   X   SPORTS/RECREATIONAL/HUMOROUS STUFF   
   #   Y   SCIENCE/SPACE TECHNICAL/NASA STUFF   
   #   Z   Sysop's only echoes < -------------------- look!   
      
   #      
   # My computer   
   127.0.0.1   *      *   
      
   # Local Network   
   10.1.1.*    *      *   
      
   # Internet   
   *.*.*.*     DKOPX  O   
      
      
   === end JAMNNT~1.ALL ==============================   
      
    AD> -+- jamnntpd.groups begin   
    >   
    AD> JAMNNTPD	F	1:154/10.1	/mystic/msgs/jamnntpd   
    AD> -+- jamnntpd.groups end   
      
   Similar here, except JAMNNTPD is classified as a sysop echo.  :)   
      
    AD> and jamnntpd.users is just myself right now, with two asterisks for   
    AD> read and posting access.   
      
   Depending on the server (I run three but only one is public), I've got a few   
   sysops, a couple of user entries for me & my wife, and, a couple of test user   
   entries.   
      
    AD> So as of right now, Thunderbird seems to be pulling in all the   
    AD> messages, while jumbling up some of the Subjects for one.. Second, I   
    AD> have to use To:  on the first line of the body of the message   
    AD> to successfully reply to anyone.. and third, Thunderbird is adding   
    AD> it's own ">" for quoting, and even with the "smartquote" option   
    AD> enabled, it doesn't seem to be changing anything..   
      
   Some of those symptoms could be from a bad compile.  The smartquote facility   
   has always worked for me and is something of a 'black box' to me; I know it   
   works, so I haven't tried to pull it apart (as it were) to see why/how.   
      
   I'll send those binaries when I get to my own PC...   
      
   Cheers,   
   Paul.   
      
   ... If it jams, force it.  If it breaks, it needed replacing anyway...   
   --- Paul's Win98SE VirtualBox   
    * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)