Hi Paul,   
      
   On 2017-09-09 21:49:00, you wrote to me:   
      
    PQ> ... Anyway, I have a tall tale to tell...   
      
    PQ> This morning I modified GoldEd's config over to reading the FMail config   
    PQ> rather than an Areas.Bbs file exported from it, after I found & re-enabled   
    PQ> the GoldEd config switch to convert DOS paths to a Linux one in tosser   
   area   
    PQ> config files.  (It took a little fine-tuning but in the end it worked.)   
    PQ> So, after doing the right thing with the scan always FMail switch, I went   
    PQ> through the motions of another post test.  GoldEd created the echomail.jam   
    PQ> file like this...   
      
    PQ> --- 8< ---   
    PQ> C:\opt\ftn\fido\msgbase\fmail_help 867   
    PQ> --- 8< ---   
      
    PQ> Which is fine since the FMail envar translation will convert it back to a   
    PQ> Linux path.  (I say back because FMail initially sucked in the Areas.Bbs   
    PQ> file from CM II, _with_ Linux paths.  And they stuck!  FMail's area   
   manager   
    PQ> has Linux paths!)  So, running the sendmail.sh produced...   
      
    PQ> --- 8< ---   
    >> 09 Sep 17 20:56:14 FMAIL  FMail-lnx32-2.1.0.18-Beta20170905 - Scan   
    >> 09 Sep 17 20:56:14 FMAIL  Echomail message, area FMAIL_HELP   
    >> 09 Sep 17 20:56:14 FMAIL  Update /opt/ftn/fido/outbound/02800180.hlo   
    >> 09 Sep 17 20:56:14 FMAIL  Mail bundle already going from 3:640/1384 to   
    >> 3:640/384 09 Sep 17 20:56:14 FMAIL  Netmail: 0,  Personal: 0,  Hudson: 0,   
    >> JAMbase: 1 09 Sep 17 20:56:14 FMAIL  Msgbase net: 0, echo: 1, dup: 0,   
    >> bad: 0 09 Sep 17 20:56:14 FMAIL  Scan Active: 0.162 sec.   
    PQ> --- 8< ---   
      
    PQ> Neat, huh?   
      
   Yes, looks all good!   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)