• [Bug] Crash netmail not working correctly

    From Martin Foster@2:280/464.27 to Tim Schattkowsky on Tue Feb 7 11:00:31 2023
    Hello Tim!

    Please note that this problem has arisen on my fresh clean install of 411.0

    Example for testing purposes:

    - I compose a crash netmail to 1:2/345

    - I "Send" the message

    - I Export the message

    - I look in the Outbound window but I don't see a mail packet destined for 1:2/345, I see a mail packet destined for 2:2/345

    I note that Outbound.001 has not been created and that the mail packet is sitting in the "Outbound" directory - Huh??

    Regards,
    Martin

    --- WinPoint 411.0
    * Origin: WinPoint Test Rig - UK - (2:280/464.27)
  • From Martin Foster@2:280/464.27 to Tim Schattkowsky on Wed Feb 8 13:23:47 2023
    Hello Tim!

    *** Tuesday 07.02.23 11:00:31, Martin Foster wrote to Tim Schattkowsky:

    [snip]
    I note that Outbound.001 has not been created and that the mail packet is sitting in the "Outbound" directory - Huh??

    Later .....
    Manually creating "Outbound.001" has fixed the problem.

    Regards,
    Martin

    --- WinPoint 411.0
    * Origin: - o(0_0)o - (2:280/464.27)
  • From Tim Schattkowsky@2:310/31.6 to Martin Foster on Tue Feb 7 15:49:40 2023
    //Hello Martin,//

    on *07.02.23* at *11:00:31* You wrote in Area *WINPOINT*
    to *Tim Schattkowsky* about *"[Bug] Crash netmail not working correctly"*.

    Hello Tim!

    Please note that this problem has arisen on my fresh clean install of 411.0

    Example for testing purposes:

    - I compose a crash netmail to 1:2/345

    - I "Send" the message

    - I Export the message

    - I look in the Outbound window but I don't see a mail packet destined
    for 1:2/345, I see a mail packet destined for 2:2/345

    I note that Outbound.001 has not been created and that the mail packet is sitting in the "Outbound" directory - Huh??

    This is probably related to a bug in outbound handling that I introduced in one of the more recent versions. The bug has already been fixed on my side, but I have not created a release. Will try to release that version during the next days. Would be great if you could check that it fixes your problem (as I think).

    Regards,
    Tim

    --- WinPoint 412.0
    * Origin: Original WinPoint Origin! (2:310/31.6)
  • From Tim Schattkowsky@2:310/31.6 to Martin Foster on Thu Feb 9 20:58:09 2023
    //Hello Martin,//

    on *08.02.23* at *13:23:47* You wrote in Area *WINPOINT*
    to *Tim Schattkowsky* about *"[Bug] Crash netmail not working correctly"*.

    Hello Tim!

    *** Tuesday 07.02.23 11:00:31, Martin Foster wrote to Tim Schattkowsky:

    [snip]
    I note that Outbound.001 has not been created and that the mail packet
    is sitting in the "Outbound" directory - Huh??

    Later .....
    Manually creating "Outbound.001" has fixed the problem.

    Makes sense. The logic for creating the outbound directories was broken and the program was doint like
    1. create outbound if it does not exist
    2. find outbound diretcory (returning the last directory checked, which IS the outbound IF it exists)

    As you can see, if step 1 fails step 2 yields the wrong directory.

    Regards,
    Tim

    --- WinPoint 412.0
    * Origin: Original WinPoint Origin! (2:310/31.6)
  • From Martin Foster@2:310/31.3 to Tim Schattkowsky on Wed Feb 15 09:10:00 2023
    Hello Tim!

    *** Tuesday 07.02.23 at 15:49, Tim Schattkowsky wrote to Martin Foster:

    Please note that this problem has arisen on my fresh clean install of
    411.0

    Example for testing purposes:

    - I compose a crash netmail to 1:2/345

    - I "Send" the message

    - I Export the message

    - I look in the Outbound window but I don't see a mail packet destined
    for 1:2/345, I see a mail packet destined for 2:2/345

    I note that Outbound.001 has not been created and that the mail packet
    is sitting in the "Outbound" directory - Huh??

    This is probably related to a bug in outbound handling that I introduced in one of the more recent versions. The bug has already been fixed on my side, but I have not created a release. Will try to release that version during the next days. Would be great if you could check that it fixes
    your problem (as I think).

    Tested and confirmed as being fixed, thanks.

    Regards,
    Martin

    --- OpenXP 5.0.57
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)