• New test..

    From Nicholas Boel@1:154/10.1 to All on Wed Aug 9 18:25:37 2017
    Hello All,

    The other ones didn't work, so let's try this one.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- FMail-lnx 2.1.0.17-B20170804
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10.1)
  • From Paul Quinn@3:640/384 to Nicholas Boel on Tue Aug 15 09:31:34 2017
    Hi! Nicholas,

    This is what I see...

    On 09 Aug 17 18:25, you wrote to All:

    @TZUTC: -0500
    @CHRS: UTF-8 4
    @MSGID: 1:154/10.1 598b9a0a
    Hello All,

    The other ones didn't work, so let's try this one.

    Regards,
    Nick

    ... "øΣ ÷∞╨╫. ï ÷ôΣ╡▐ ╢Φû▐úΦ ╖╨ñΦ╢╨╫."
    --- FMail-lnx 2.1.0.17-B20170804
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10.1) SEEN-BY: 154/10 20 30 40 700 203/0 124 221/1 6 230/0 249/303 266/404 280/464
    SEEN-BY: 280/5555 320/219 340/800 423/81 640/384 2320/100 3634/12
    @PATH: 154/10 203/0

    Cheers,
    Paul.

    ... In memory of Werner Hartenstein & RMS Laconia - 15 September 1942.
    --- Paul's Win98SE VirtualBox
    * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)
  • From Nicholas Boel@1:154/10 to Paul Quinn on Mon Aug 14 18:45:26 2017
    Hello Paul,

    On Tue Aug 15 2017 09:31:34, Paul Quinn wrote to Nicholas Boel:

    This is what I see...

    Thanks!

    @PATH: 154/10 203/0

    Not adding the boss node to the PATH (fmail setting) was a good idea, I see. ;)

    Just seems I'm having an issue with echomail.jam now. Golded creates it in the right place, but running "fmail scan" seems to find it, and delete it, but doesn't actually scan out the message. "fmail scan -S" finds the message and scans it out, though. Odd.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Paul Quinn@3:640/384 to Nicholas Boel on Tue Aug 15 10:13:00 2017
    Hi! Nick,

    On Mon, 14 Aug 17, you wrote to me:

    Just seems I'm having an issue with echomail.jam now.
    Golded creates it in the right place, but running "fmail
    scan" seems to find it, and delete it, but doesn't actually
    scan out the message. "fmail scan -S" finds the message and
    scans it out, though. Odd.

    I haven't tried any sending silliness yet. I've config'd GoldEd to place those
    files in the semaphore directory but now thinking on it, maybe they should go where the messagebase directory is located. What have you come up with?

    Cheers,
    Paul.

    --- Paul's Win98SE VirtualBox
    * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)
  • From Nicholas Boel@1:154/10 to Paul Quinn on Mon Aug 14 19:18:54 2017
    Hello Paul,

    On Tue Aug 15 2017 10:13:00, Paul Quinn wrote to Nicholas Boel:

    Just seems I'm having an issue with echomail.jam now.
    Golded creates it in the right place, but running "fmail
    scan" seems to find it, and delete it, but doesn't actually
    scan out the message. "fmail scan -S" finds the message and
    scans it out, though. Odd.

    I haven't tried any sending silliness yet. I've config'd GoldEd to
    place those files in the semaphore directory but now thinking on it,
    maybe they should go where the messagebase directory is located. What have you come up with?

    It doesn't really matter where you place echomail.jam. As long as you have it configured the same in your editor as well as fmail. Although in your case, the
    semaphore directory sounds solid enough. The message base directory has it's own group of files to worry about. However, that's currently where I'm putting it only because I don't have a semaphore directory just yet. ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Tue Aug 15 08:25:22 2017
    Hi Nicholas,

    On 09 Aug 17 18:25, Nicholas Boel wrote to All:
    about: "New test..":

    @MSGID: 1:154/10.1 598b9a0a
    @TZUTC: -0500
    @CHRS: UTF-8 4
    Hello All,

    The other ones didn't work, so let's try this one.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- FMail-lnx 2.1.0.17-B20170804

    Received!

    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10.1) SEEN-BY: 103/705 154/10 20 30 40 700 203/0 221/6 240/5832 249/303 280/464 SEEN-BY: 280/5003 5555 292/624 854 310/31 340/800 423/120 712/848 770/1 SEEN-BY: 2320/100 3634/12
    @PATH: 154/10 280/464

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Tue Aug 15 08:29:27 2017
    Hi Nicholas,

    On 14 Aug 17 18:45, Nicholas Boel wrote to Paul Quinn:
    about: "New test..":

    Just seems I'm having an issue with echomail.jam now. Golded creates
    it in the right place, but running "fmail scan" seems to find it, and delete it, but doesn't actually scan out the message. "fmail scan -S" finds the message and scans it out, though. Odd.

    I never had a problem with it. But you can look inside it with any editor before you run 'fmail scan'. It's just a plain txt file.

    -S should. That option ignores echomail.jam, and scans every area for unsend messages front to back.

    Maybe I need to add some more logging? ;)

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464.112 to Paul Quinn on Tue Aug 15 08:37:32 2017
    Hi Paul,

    On 15 Aug 17 10:13, Paul Quinn wrote to Nicholas Boel:
    about: "New test..":

    I haven't tried any sending silliness yet. I've config'd GoldEd to
    place those files in the semaphore directory but now thinking on it,
    maybe they should go where the messagebase directory is located. What have you come up with?

    FMail always and only looks for it in the 'Message base' directory (where the hudson area files are located).

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Tue Aug 15 08:46:15 2017
    Hi Nicholas,

    On 14 Aug 17 19:18, Nicholas Boel wrote to Paul Quinn:
    about: "New test..":

    It doesn't really matter where you place echomail.jam. As long as you
    have it configured the same in your editor as well as fmail. Although
    in your case, the semaphore directory sounds solid enough. The message base directory has it's own group of files to worry about. However,
    that's currently where I'm putting it only because I don't have a semaphore directory just yet. ;)

    There isn't a separate configuration setting for the echomail.jam directory. FMail always uses the 'Message base' directory for it.

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Paul Quinn@3:640/1384 to Wilfred van Velzen on Tue Aug 15 18:03:50 2017
    Hi! Wilfred,

    On 08/15/2017 04:37 PM, you wrote:

    FMail always and only looks for it in the 'Message base' directory
    (where the hudson area files are located).

    Is this statement in the doc file?

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)
  • From Wilfred van Velzen@2:280/464 to Paul Quinn on Tue Aug 15 11:12:45 2017
    Hi Paul,

    On 2017-08-15 18:03:50, you wrote to me:

    FMail always and only looks for it in the 'Message base' directory
    (where the hudson area files are located).

    Is this statement in the doc file?

    If it is, I can't find it. ;)

    So point for improvement...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.17-B20170711
    * Origin: FMail development HQ (2:280/464)
  • From Paul Quinn@3:640/384 to Wilfred van Velzen on Tue Aug 15 19:42:24 2017
    Hi! Wilfred,

    On 15 Aug 17 11:12, you wrote to me:

    FMail always and only looks for it in the 'Message base'
    directory (where the hudson area files are located).

    Just BTW: I had Murphy's luck with this having a 50-50 chance of getting it right. FMail does it the same as FastEcho on -this- but Crashmail II on my -other- node takes the path parameter as an argument to the scanner command.

    Is this statement in the doc file?

    If it is, I can't find it. ;)

    Neither could I.

    So point for improvement...

    A minor one. If anything its omission is just an annoyance but not critical.

    Cheers,
    Paul.

    ... In memory of Werner Hartenstein & RMS Laconia - 15 September 1942.
    --- Paul's Win98SE VirtualBox
    * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)
  • From Wilfred van Velzen@2:280/464.112 to Paul Quinn on Tue Aug 15 13:12:23 2017
    Hi Paul,

    On 15 Aug 17 19:42, Paul Quinn wrote to Wilfred van Velzen:
    about: "New test..":

    So point for improvement...

    A minor one. If anything its omission is just an annoyance but not critical.

    Adding 1 or 2 lines to the doc, shouldn't be a problem, because it's so time consuming... ;)

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Paul Quinn@3:640/384 to Wilfred Van Velzen on Tue Aug 15 21:52:00 2017
    Hi! Wilfred,

    On Tue, 15 Aug 17, you wrote to me:

    A minor one. If anything its omission is just an
    annoyance but not critical.

    Adding 1 or 2 lines to the doc, shouldn't be a problem,
    because it's so time consuming... ;)

    The most time would be taken up by the task of finding those 2 lines that can be deleted to make space, and maintain 'balance'. ;-)

    Cheers,
    Paul.

    --- Paul's Win98SE VirtualBox
    * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)
  • From mark lewis@1:3634/12.73 to Nicholas Boel on Tue Aug 15 08:15:20 2017

    On 2017 Aug 09 18:25:36, you wrote to All:

    @TZUTC: -0500
    @CHRS: UTF-8 4
    @MSGID: 1:154/10.1 598b9a0a
    Hello All,

    The other ones didn't work, so let's try this one.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- FMail-lnx 2.1.0.17-B20170804
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10.1) SEEN-BY: 116/116 123/141 135/300 140/1 154/10 20 30 40 700 261/38 340/800 SEEN-BY: 3634/12 15 22 24 27 50
    @PATH: 154/10 3634/12



    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Keep London tidy - eat a pigeon.
    ---
    * Origin: (1:3634/12.73)
  • From mark lewis@1:3634/12.73 to Nicholas Boel on Tue Aug 15 08:16:48 2017

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

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

    is golded creating it in the proper format?

    but running "fmail scan" seems to find it, and delete it, but doesn't 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...

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

    that's actually a GoodThing<tm> :) 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.
    ---
    * Origin: (1:3634/12.73)
  • From mark lewis@1:3634/12.73 to Paul Quinn on Tue Aug 15 08:46:48 2017

    On 2017 Aug 15 10:13:00, you wrote to Nicholas Boel:

    I haven't tried any sending silliness yet. I've config'd GoldEd to
    place those files in the semaphore directory but now thinking on it,
    maybe they should go where the messagebase directory is located. What have you come up with?

    traditionally, echomail.jam and netmail.jam are placed in the message base directory where the hudson message base files are or would be created... this was developed jointly by the remoteaccess and fastecho devs when the JAM format
    was first introduced by the frontdoor and remoteaccess teams... traditional mail tossers will look for those file where the HMB is...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Most people are willing to pay more to be amused than to be educated!
    ---
    * Origin: (1:3634/12.73)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Tue Aug 15 21:37:51 2017
    Hi Nicholas,

    On 2017-08-15 08:29:27, I wrote to you:

    Just seems I'm having an issue with echomail.jam now. Golded creates
    it in the right place, but running "fmail scan" seems to find it, and
    delete it, but doesn't actually scan out the message. "fmail scan -S"
    finds the message and scans it out, though. Odd.

    I never had a problem with it. But you can look inside it with any editor before you run 'fmail scan'. It's just a plain txt file.

    -S should. That option ignores echomail.jam, and scans every area for unsend messages front to back.

    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)
  • From Paul Quinn@3:640/1384 to mark lewis on Wed Aug 16 06:24:19 2017
    Hi! mark,

    On 08/15/2017 10:46 PM, you wrote:

    traditionally, echomail.jam and netmail.jam are placed in the message
    base directory where the hudson message base files are or would be created... this was developed jointly by the remoteaccess and fastecho devs when the JAM format was first introduced by the frontdoor and remoteaccess teams... traditional mail tossers will look for those file where the HMB is...

    Yes. It is an old lesson re-learned.

    While both packages insist on having a HMB, FastEcho's unused one has been situated on a 256Kb(!) RAM drive for the last ~15 years, with semaphores and other text files in separate dirs. A body can't do that with FMail, as that is
    where the Badmail & Dupes are forced.

    Arggghhh! ;-)

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)
  • From mark lewis@1:3634/12.73 to Paul Quinn on Tue Aug 15 17:52:32 2017
    On 2017 Aug 16 06:24:18, you wrote to me:

    created... this was developed jointly by the remoteaccess and fastecho
    devs when the JAM format was first introduced by the frontdoor and
    remoteaccess teams... traditional mail tossers will look for those
    file where the HMB is...

    Yes. It is an old lesson re-learned.

    :)

    While both packages insist on having a HMB, FastEcho's unused one has
    been situated on a 256Kb(!) RAM drive for the last ~15 years, with semaphores and other text files in separate dirs. A body can't do
    that with FMail, as that is where the Badmail & Dupes are forced.

    yep... JAM badmail and dupes areas are great... my HMB has been empty since JAM
    came along back in the development days... if fastecho didn't insist on creating them even though nothing is defined as using them, it would be much better...

    Arggghhh! ;-)

    i feel yer pain, my friend :)

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... You said a mouseful!
    ---
    * Origin: (1:3634/12.73)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Tue Aug 15 19:13:26 2017
    Hello Wilfred,

    On Tue Aug 15 2017 08:29:26, Wilfred van Velzen wrote to Nicholas Boel:

    I never had a problem with it. But you can look inside it with any
    editor before you run 'fmail scan'. It's just a plain txt file.

    Sure. It just has the location and filename (minus the extension) of the JAM message base, and then the message number after it. There's nothing wrong with the output, just that FMail sees it and deletes it without any other messages as to why nothing was scanned out of it.

    -S should. That option ignores echomail.jam, and scans every area for unsend messages front to back.

    Yes. That works as expected. Unfortunately at the moment it's the only way that's working.

    Maybe I need to add some more logging? ;)

    Very possible! ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Tue Aug 15 19:22:44 2017
    Hello Wilfred,

    On Tue Aug 15 2017 21:37:50, Wilfred van Velzen wrote to Nicholas Boel:

    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...

    Excellent. Thanks for the quick response (before I even knew it was a bug)! ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10.1 to Wilfred van Velzen on Tue Aug 15 19:34:04 2017
    Hello Wilfred,

    Tue Aug 15 2017 21:37:51, you wrote to me:

    Hi Nicholas,

    -S should. That option ignores echomail.jam, and scans every
    area for unsend messages front to back.

    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...

    Testing bugfix. If I don't reply about the same matter, consider it working as expected! ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- FMail-lnx 2.1.0.17-B20170815
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10.1)
  • From Wilfred van Velzen@2:280/464.112 to Paul Quinn on Wed Aug 16 08:25:35 2017
    Hi Paul,

    On 16 Aug 17 06:24, Paul Quinn wrote to mark lewis:
    about: "New test..":

    While both packages insist on having a HMB, FastEcho's unused one has
    been situated on a 256Kb(!) RAM drive for the last ~15 years, with semaphores and other text files in separate dirs. A body can't do
    that with FMail, as that is where the Badmail & Dupes are forced.

    It's on the to-do list! ;)

    But priority is on the linux version right now...

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Wed Aug 16 08:37:42 2017
    Hi Nicholas,

    On 15 Aug 17 19:34, Nicholas Boel wrote to Wilfred van Velzen:
    about: "New test..":

    Testing bugfix. If I don't reply about the same matter, consider it working as expected! ;)

    It would be easier if you confirmed it's working, otherwise you can come back about this next year, when I completely forgot about the details... ;)

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Paul Quinn@3:640/1384 to Wilfred van Velzen on Wed Aug 16 17:56:49 2017
    Hi! Wilfred,

    On 08/16/2017 04:25 PM, you wrote:

    It's on the to-do list! ;)

    Nice.

    But priority is on the linux version right now...

    Yes, boss. I like how you talk! :)

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)
  • From Wilfred van Velzen@2:280/464 to Paul Quinn on Wed Aug 16 10:50:23 2017
    Hi Paul,

    On 2017-08-16 17:56:49, you wrote to me:

    But priority is on the linux version right now...

    Yes, boss. I like how you talk! :)

    Do I seem bossy? Should I sugar coat it somehow? ;)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Paul Quinn@3:640/1384 to Wilfred van Velzen on Wed Aug 16 19:18:17 2017
    Hi! Wilfred,

    On 08/16/2017 06:50 PM, you wrote:

    But priority is on the linux version right now...

    Yes, boss. I like how you talk! :)

    Do I seem bossy? Should I sugar coat it somehow? ;)

    Don't get too upsket(sic). It's an Aussie thing, from my generation. It's almost as good as 'mate' but recognizes that you're in charge.

    Maybe I should have referred to you as 'chief' but I wasn't sure how you take that, so I didn't. ;-)

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)
  • From Wilfred van Velzen@2:280/464 to Paul Quinn on Wed Aug 16 13:53:18 2017
    Hi Paul,

    On 2017-08-16 19:18:17, you wrote to me:

    Maybe I should have referred to you as 'chief' but I wasn't sure how
    you take that, so I didn't. ;-)

    Worse than boss... ;)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Richard Menedetter@2:310/31 to Wilfred van Velzen on Wed Aug 16 22:31:44 2017
    Hi Wilfred!

    16 Aug 2017 08:25, from Wilfred van Velzen -> Paul Quinn:

    While both packages insist on having a HMB, FastEcho's unused one
    has been situated on a 256Kb(!) RAM drive for the last ~15 years,
    with semaphores and other text files in separate dirs. A body
    can't do that with FMail, as that is where the Badmail & Dupes
    are forced.
    It's on the to-do list! ;)
    But priority is on the linux version right now...

    As soon as JAM only is possible on Linux, I will also try ;))

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: OPCODE: RA = Randomize Answer (2:310/31)
  • From Nicholas Boel@1:154/10.1 to Wilfred van Velzen on Wed Aug 16 15:31:09 2017
    Hello Wilfred,

    Wed Aug 16 2017 08:37:42, you wrote to me:

    Testing bugfix. If I don't reply about the same matter, consider
    it working as expected! ;)

    It would be easier if you confirmed it's working, otherwise you can
    come back about this next year, when I completely forgot about the details... ;)

    In that case, it's working just fine now. Thank you for the hotfix! ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- FMail-lnx 2.1.0.17-B20170815
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10.1)
  • From Nicholas Boel@1:154/10.1 to Richard Menedetter on Wed Aug 16 16:22:41 2017
    Hello Richard,

    Wed Aug 16 2017 22:31:44, you wrote to Wilfred van Velzen:

    As soon as JAM only is possible on Linux, I will also try ;))

    JAM only? As in netmail too? JAM message bases are already possible on Linux. ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- FMail-lnx 2.1.0.17-B20170815
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10.1)
  • From Richard Menedetter@2:310/31 to Nicholas Boel on Wed Aug 16 23:49:28 2017
    Hi Nicholas!

    16 Aug 2017 16:22, from Nicholas Boel -> Richard Menedetter:

    As soon as JAM only is possible on Linux, I will also try ;))
    JAM only? As in netmail too? JAM message bases are already possible on Linux. ;)

    ;))

    As soon as the native Linux version of FMail supports a pure JAM setup under Linux including setup.

    I hope it is more understandable now :-P

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Engraving is, in brief terms, the art of scratch. (2:310/31)
  • From Wilfred van Velzen@2:280/464.112 to Richard Menedetter on Thu Aug 17 08:34:09 2017
    Hi Richard,

    On 16 Aug 17 22:31, Richard Menedetter wrote to Wilfred van Velzen:
    about: "New test..":

    While both packages insist on having a HMB, FastEcho's unused one
    has been situated on a 256Kb(!) RAM drive for the last ~15 years,
    with semaphores and other text files in separate dirs. A body
    can't do that with FMail, as that is where the Badmail & Dupes
    are forced.
    It's on the to-do list! ;)
    But priority is on the linux version right now...

    As soon as JAM only is possible on Linux, I will also try ;))

    I better start working then! ;)

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Thu Aug 17 08:39:44 2017
    Hi Nicholas,

    On 16 Aug 17 15:31, Nicholas Boel wrote to Wilfred van Velzen:
    about: "New test..":

    It would be easier if you confirmed it's working, otherwise you can
    come back about this next year, when I completely forgot about the
    details... ;)

    In that case, it's working just fine now. Thank you for the hotfix! ;)

    Thanks for the confirmation...

    Btw: If Paul wants/needs a 32 bit version with this fix, I can provide one?

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Paul Quinn@3:640/1384 to Wilfred van Velzen on Thu Aug 17 17:33:59 2017
    Hi! Wilfred,

    On 08/17/2017 04:39 PM, you wrote:

    It would be easier if you confirmed it's working, otherwise you can
    come back about this next year, when I completely forgot about the
    details... ;)

    In that case, it's working just fine now. Thank you for the
    hotfix! ;)

    Thanks for the confirmation...

    Btw: If Paul wants/needs a 32 bit version with this fix, I can provide
    one?

    If it's send-related (aka fmail scan) then not at this time, thanks. I'm quietly watching just the tossing activity and monitoring the contents of the messagebase, while fine-tuning GoldEd... and, loving it. :)

    All the JAM message area paths in Linux form were successfully imported into FMail from an Areas.Bbs created by my Crashmail II tosser (on this Linux system). The netmail & HMB paths are converting correctly by 'fmail toss' using the "FMAIL_REPLACE_DRIVE" envar.

    GoldEd is set to use the same Areas.Bbs file that FConfigW32 imported, together
    with local handwritten converted paths for the netmail & HMB areas in its configuration file. GoldEd has even been config'd to use the same echo descriptions files as Fmail is supposed to use, so GoldEd looks normal again.

    OTOH, I have noticed a slight weirdness in a local area (but still of 'echomail' type). There's usually a batch of about 18-20 messages generated by
    FastEcho in the area over a period of about 5 seconds each morning. They're landing in the Fmail messagebase 'out of order'.

    I did go back to FConfigW32 and enable message sorting but the ordering still didn't seem normal compared with what I see tossed into the Crashmail messagebase... ermmm, just checking... nah, they check out with GoldEd (here) as being in the as-created order.

    I'll double-double check everything following tomorrow's activity, and advise formally if needed.

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)
  • From Wilfred van Velzen@2:280/464.112 to Paul Quinn on Thu Aug 17 10:29:58 2017
    Hi Paul,

    On 17 Aug 17 17:33, Paul Quinn wrote to Wilfred van Velzen:
    about: "New test..":

    Btw: If Paul wants/needs a 32 bit version with this fix, I can
    provide one?

    If it's send-related (aka fmail scan)

    Yes.

    then not at this time, thanks.

    Ok...

    I'm quietly watching just the tossing activity and monitoring the
    contents of the messagebase, while fine-tuning GoldEd... and, loving
    it. :)

    All the JAM message area paths in Linux form were successfully imported into FMail from an Areas.Bbs created by my Crashmail II tosser (on this Linux system). The netmail & HMB paths are converting correctly by 'fmail toss' using the "FMAIL_REPLACE_DRIVE" envar.

    GoldEd is set to use the same Areas.Bbs file that FConfigW32 imported, together with local handwritten converted paths for the netmail & HMB areas in its configuration file. GoldEd has even been config'd to use the same echo descriptions files as Fmail is supposed to use, so GoldEd looks normal again.

    OTOH, I have noticed a slight weirdness in a local area (but still of 'echomail' type). There's usually a batch of about 18-20 messages generated by FastEcho in the area over a period of about 5 seconds each morning. They're landing in the Fmail messagebase 'out of order'.

    Are they in 1 pkt file or several? You can look in the fmail log file in what order the .pkt files are processed...

    I did go back to FConfigW32 and enable message sorting

    If I'm not mistaken, the 'Sort new messages' option only works on the hudson message base, not on the JAM areas.

    but the ordering still didn't seem normal compared with what I see
    tossed into the Crashmail messagebase... ermmm, just checking... nah,
    they check out with GoldEd (here) as being in the as-created order.

    I'll double-double check everything following tomorrow's activity, and advise formally if needed.

    Ok...

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Richard Menedetter@2:310/31 to Wilfred van Velzen on Thu Aug 17 21:23:04 2017
    Hi Wilfred!

    17 Aug 2017 08:34, from Wilfred van Velzen -> Richard Menedetter:

    It's on the to-do list! ;)
    But priority is on the linux version right now...
    As soon as JAM only is possible on Linux, I will also try ;))
    I better start working then! ;)

    ;))
    I have time ...

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: I was a Wine steward at McDonald's. (2:310/31)
  • From Nicholas Boel@1:154/10.1 to Richard Menedetter on Thu Aug 17 19:40:41 2017
    Hello Richard,

    Wed Aug 16 2017 23:49:28, you wrote to me:

    As soon as the native Linux version of FMail supports a pure JAM setup under Linux including setup.

    I hope it is more understandable now :-P

    So you're waiting for fconfig to be ported..?

    Yeah, it's kind of a pain to run the config in Windows and transfer it over, but it's definitely better than nothing, and not much is being worked on these days for people that like to test new things, and since I have a windows machine, I figured what the heck. ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- FMail-lnx 2.1.0.17-B20170815
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10.1)
  • From Wilfred van Velzen@2:280/464.112 to Richard Menedetter on Fri Aug 18 09:21:40 2017
    Hi Richard,

    On 17 Aug 17 21:23, Richard Menedetter wrote to Wilfred van Velzen:
    about: "New test..":

    It's on the to-do list! ;)
    But priority is on the linux version right now...
    As soon as JAM only is possible on Linux, I will also try ;))
    I better start working then! ;)

    ;))
    I have time ...

    Good! You will need it... ;)

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)