05 Jul 16 23:38, you wrote to Ross Cassell:   
      
    RC>> In the message list, in the FROM -> TO field, the names get mangled   
    RC>> until the message is selected, I am running the server under UBUNTU   
    RC>> 16.04 and have seen this issue under 1.0, 1.1 and 1.2.. Should I try   
    RC>> ..05?   
      
    MB> It is not a jamnntpd problem but a client problem.  The client looks   
    MB> for e-mail in the <> portion of the from field so the -> confuses   
    MB> some.  I changed the -> to a - and it works much better.   
      
   i did the same over here (but changed to --) and it didn't do any good at   
   all... that was with the version i was running before i grabbed 1.2 and   
   compiled it... with 1.2 and the RFC 5322 email address format fix, they're   
   fine on my OS/2 system (jamnntpd compiled with emx) when reading with my linux   
   thunderbird and other linux news software...   
      
   in the past, when i've seen the headers ""correct themselves"" when clicking   
   on the message to read it, it has been because the local header database is   
   out of sync with the messages on the news server... the only way to fix that   
   is to download the headers again... when doing that, jamnntpd will send them   
   via the RFC 5322 code with something that looks like a proper email address   
   but isn't...   
      
   eg:   
     point@node.net.zone   
      
   which really should be in another format with a proper domain that can be   
   specified in the jamnntpd conf files by the operator... a proper domain with   
   netmail<->email conversion capabilities...   
      
   eg:   
     user.name@example.com                      (my bbs)   
     user.name@node.example.com                 (nodes in my net)   
     user.name@net-node.example.com             (nodes in my zone)   
     user.name@net-node-point.example.com       (all points)   
     user.name@zone-net-node-point.example.com  (all outside my zone)   
      
   if there's no domain for private replies to flow through, then something like   
      
     user.name@somedomain.invalid   
      
   i'm actually considering having my registered users use   
      
     me@privacy.net   
      
   instead of using their real email address when they post messages via my   
   server... i retain their applications so have that for their real email   
   addresses or at leat the ones they used when they registered for my service...   
      
   )\/(ark   
      
   Always Mount a Scratch Monkey   
      
   ... It's not about amusement, it's about dinner.   
   ---   
    * Origin:  (1:3634/12.73)