Hi Nicholas,
On 2017-08-15 08:29:27, I wrote to you:
NB>> Just seems I'm having an issue with echomail.jam now. Golded creates
NB>> it in the right place, but running "fmail scan" seems to find it, and
NB>> delete it, but doesn't actually scan out the message. "fmail scan -S"
NB>> finds the message and scans it out, though. Odd.
WvV> I never had a problem with it. But you can look inside it with any editor
WvV> before you run 'fmail scan'. It's just a plain txt file.
WvV> -S should. That option ignores echomail.jam, and scans every area for
WvV> unsend messages front to back.
WvV> Maybe I need to add some more logging? ;)
While I was adding some debug logging to the echomail.jam processing code, I
found a bug. The paths in the echomail.jam file and those for the jam areas in
the config weren't converted to linux paths before comparing them. On my system
this wasn't a problem because of some script code that runs after I leave
golded-lnx to fix the paths to their dos versions in echomail.jam, because of
my previous hibrid system. A fixed version of fmail.c is in your inbound...
Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)
|
