Hi Nicholas,

On 2017-09-08 15:47:04, you wrote to me:

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

 NB> Very clear. However, the only reason it was scanned out is because his
 NB> FMail scanned _every_ area, rather than just what was in the echomail.jam.

Nope. If I understood Paul correctly, it worked ok, scanning from echomail.jam!

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

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

 NB> Did you give Paul a compiled setup with the updated fmail.c you gave me
 NB> that fixed linux paths in echomail.jam?

Yes, it was freshly compiled. But it wasn't a debug version, so it didn't
contain the extra logging...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815