On 2017 Aug 14 18:45:26, you wrote to Paul Quinn:

 NB> Just seems I'm having an issue with echomail.jam now. Golded creates it in
 NB> the right place,

is golded creating it in the proper format?

 NB> but running "fmail scan" seems to find it, and delete it,
but doesn't
 NB> actually scan out the message.

this seems to indicate another bug or invalid format that isn't being
complained about...

----->8 snip 8<-----

the format of echomail.jam is:

  one line per message.
  each line contains two parts.
    the 1st part is the full path to the message base plus the base name.
    the 2nd part is the message number to be exported.

  eg:
    G:\JAM\FIDO\H\HAM 145346
    G:\JAM\FIDO\H\HAM 145352
    G:\JAM\FIDO\C\COOKING 576683
    G:\JAM\FIDO\H\HAM 145357

    the above says to export messages #145346 and #145352 from the message
    base named HAM in the G:\JAM\FIDO\H directory. and to also export
    message #576683 from the COOKING message base located in the
    G:\JAM\FIDO\C directory. then back to the HAM message base to export
    message #145357.

----->8 snip 8<-----

at least one program, the last version of allfix by the original author,
has a problem with echomail.jam... it is using the wrong variable type
(word vs longint) for the message number so they are wrapped (actually
modulo math or clock math) at 65535... so when message numbers in a base
that allfix posts to get larger than 65535, it writes the wrong (smaller)
number to the echomail.jam file...

 NB> "fmail scan -S" finds the message and scans it out, though. Odd.

that's actually a GoodThing :)  i have to use it to scan out
allfix's posts on my main system... since it takes a while on a large
message base setup, i only have it run at midnight which is why one sees
batches of the new file arrival posts from my main system after midnight
each night...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin'
it wrong...
... As handy as an indulgent husband.
---