Subj : Re: Trialing FMail/lnx status check-in
To   : Nicholas Boel
From : Wilfred van Velzen
Date : Fri Sep 08 2017 12:22:41

Hi Nicholas,

On 2017-09-07 16:36:44, you wrote to Paul Quinn:

 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>>> /opt/ftn/fido/outbound/02800180.hlo 07 Sep 17 12:15:15 FMAIL
 WvV>>> Mail bundle already going from 3:640/1384 to 3:640/384 07 Sep 17
 WvV>>> 12:15:15 FMAIL  Netmail: 0,  Personal: 0,  Hudson: 0, JAMbase: 1
 WvV>>> 07 Sep 17 12:15:15 FMAIL  Msgbase net: 0, echo: 1, dup: 0, bad:
 WvV>>> 0 07 Sep 17 12:15:15 FMAIL  Scan Active: 1.376 sec.

 NB> This log snippet doesn't mention anything about area "fec1e5dd". But
 NB> it does mention "WIN95". Something seems odd there,

The jam file area name that is used on Pauls system is odd, but all is working 
fine...

 NB> ..instead, and that is what FMail is looking for, but since it doesn't
 NB> see it, and nothing else was read from echomail.jam it deleted the
 NB> file.

It did see it and exported the message to Pauls outbound (if that isn't clear 
yet?)...

 PQ>> The terminal screen says things about checking netmail & HMB, and
 PQ>> then JAM areas.  Nothing about the echomail.jam file at all.

 NB> I believe I had asked about some better logging when echomail.jam fails
 NB> too. ;)

It's there... In the debug version. Just have to clean that up a bit for the 
production version. ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)

.