Hi Paul,   
      
   On 2017-09-07 19:48:25, you wrote to me:   
      
    WvV>> What does the log say?   
      
    PQ> --- 8< ---   
    WvV>> 07 Sep 17 12:15:14 FMAIL  FMail-lnx32-2.1.0.18-Beta20170905 - Scan   
    WvV>> 07 Sep 17 12:15:14 FMAIL  Scanning JAM area 0: ABLED   
    PQ> [ ...trimmed... ]   
    WvV>> 07 Sep 17 12:15:15 FMAIL  Scanning JAM area 172: WIN95   
    WvV>> 07 Sep 17 12:15:15 FMAIL  Echomail message, area WIN95   
    WvV>> 07 Sep 17 12:15:15 FMAIL  Scanning JAM area 173: WINDOWS   
    WvV>> 07 Sep 17 12:15:15 FMAIL  Scanning JAM area 174: WWIV   
    WvV>> 07 Sep 17 12:15:15 FMAIL  Scanning JAM area 175: ZEC   
    WvV>> 07 Sep 17 12:15:15 FMAIL  Scanning JAM area 176: ZONE3_SYSOP   
    WvV>> 07 Sep 17 12:15:15 FMAIL  Scanning JAM area 177: ZONE3_TECH   
    WvV>> 07 Sep 17 12:15:15 FMAIL  Update /opt/ftn/fido/outbound/02800180.hlo   
    WvV>> 07 Sep 17 12:15:15 FMAIL  Mail bundle already going from 3:640/1384   
    WvV>> to 3:640/384 07 Sep 17 12:15:15 FMAIL  Netmail: 0,  Personal: 0,   
    WvV>> Hudson: 0, JAMbase: 1 07 Sep 17 12:15:15 FMAIL  Msgbase net: 0, echo:   
    WvV>> 1, dup: 0, bad: 0 07 Sep 17 12:15:15 FMAIL  Scan Active: 1.376 sec.   
    PQ> --- 8< ---   
      
    PQ> The terminal screen says things about checking netmail & HMB, and then JAM   
    PQ> areas.  Nothing about the echomail.jam file at all.   
      
   Maybe the loging/printing isn't perfect, but this all seems fine. Have you   
   checked if the mail arrived at it's destination (3:640/384) ?   
      
   If you are not certain you can have FMail make backups of outgoing .pkt files   
   by specifying a "Outgoing backup" directory in FConfig. So you have a way of   
   checking what's produced without it disappearing because of your mailer (or   
   other processes) doing their jobs...   
      
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)