• rescanning and long messages

    From Carlos Navarro@2:341/234 to Wilfred van Velzen on Monday, November 28, 2022 20:40:34
    It seems that FMail (at least the Win32 version) has issues when rescanning echos that have long messages.

    I've done some test and checked the PKTs -- long messages seem to be cut at around 40K.

    Carlos

    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: cyberiada (2:341/234)
  • From Wilfred van Velzen@2:280/464 to Carlos Navarro on Monday, November 28, 2022 21:16:09
    Hi Carlos,

    On 2022-11-28 20:40:34, you wrote to me:

    It seems that FMail (at least the Win32 version) has issues when rescanning echos that have long messages.

    I've done some test and checked the PKTs -- long messages seem to be cut at
    around 40K.

    I would have to test that. What are your settings for "Max message size (kb)" and "Max PKT size (kb)"?

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Carlos Navarro@2:341/234.1 to Wilfred van Velzen on Monday, November 28, 2022 21:37:31
    I would have to test that. What are your settings for "Max message
    size (kb)" and "Max PKT size (kb)"?

    0 (no maximum) and 9999.

    The big messages were tossed and exported to all links without issues when they arrived. I only found this problem with rescans.

    Carlos

    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: cyberiada point (2:341/234.1)
  • From Tommi Koivula@2:221/1 to Carlos Navarro on Tuesday, November 29, 2022 08:25:38
    On 28.11.2022 22.37, Carlos Navarro wrote:

    The big messages were tossed and exported to all links without issues
    when they arrived. I only found this problem with rescans.

    I think I know the answer, but I ask anyway: What msgbase format are you using?

    'Tommi

    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)
  • From Carlos Navarro@2:341/234.12 to Tommi Koivula on Tuesday, November 29, 2022 07:41:45
    The big messages were tossed and exported to all links without
    issues when they arrived. I only found this problem with rescans.
    I think I know the answer, but I ask anyway: What msgbase format
    are you using?

    JAM.

    --
    Carlos
    --- Hotdoged/2.13.5/Android
    * Origin: cyberiada mobile point (2:341/234.12)
  • From Tommi Koivula@2:221/1 to Carlos Navarro on Tuesday, November 29, 2022 09:28:11
    On 29.11.2022 8.41, Carlos Navarro wrote:

    ??>> The big messages were tossed and exported to all links without
    ??>> issues when they arrived. I only found this problem with rescans.
    TK> I think I know the answer, but I ask anyway: What msgbase format
    TK> are you using?

    JAM.

    Yes, so that is not the problem.

    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)
  • From Wilfred van Velzen@2:280/464.112 to Tommi Koivula on Tuesday, November 29, 2022 08:28:40
    Hi Tommi,

    On 29 Nov 22 08:25, Tommi Koivula wrote to Carlos Navarro:
    about: "rescanning and long messages":

    The big messages were tossed and exported to all links without issues
    when they arrived. I only found this problem with rescans.

    I think I know the answer, but I ask anyway: What msgbase format are you using?

    That shouldn't matter for a rescan. The full message is already stored in there...

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464 to Carlos Navarro on Tuesday, November 29, 2022 09:16:45
    Hi Carlos,

    On 2022-11-28 21:37:31, you wrote to me:

    I would have to test that. What are your settings for "Max message
    size (kb)" and "Max PKT size (kb)"?

    0 (no maximum) and 9999.

    The big messages were tossed and exported to all links without issues when they arrived. I only found this problem with rescans.

    I did the test, talking to my linux version of FMail and can reproduce this. So thanks for the bug report! ;-)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/1 to Wilfred van Velzen on Wednesday, November 30, 2022 12:55:07

    >> The big messages were tossed and exported to all links without issues
    >> when they arrived. I only found this problem with rescans.

    TK> I think I know the answer, but I ask anyway: What msgbase format are you
    TK> using?

    That shouldn't matter for a rescan. The full message is already stored in there...

    In case of hudson also? Can it store that big messages? Cannot remember the limits of HMB anymore but it has some. :)

    'Tommi

    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)
  • From Tommi Koivula@2:221/1 to Wilfred van Velzen on Wednesday, November 30, 2022 12:59:11
    WV>> I would have to test that. What are your settings for "Max message
    WV>> size (kb)" and "Max PKT size (kb)"?

    CN> 0 (no maximum) and 9999.

    CN> The big messages were tossed and exported to all links without issues when
    CN> they arrived. I only found this problem with rescans.

    I did the test, talking to my linux version of FMail and can reproduce this. So thanks for the bug report! ;-)

    You can thank Dan Richter also, his messages are getting bigger and bigger every day. 260k today. ;)

    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Wednesday, November 30, 2022 12:02:02
    Hi Tommi,

    On 2022-11-30 12:55:07, you wrote to me:

    That shouldn't matter for a rescan. The full message is already stored
    in there...

    In case of hudson also?

    My DUPE area is in hudson. There were no problems importing the big messages in there.

    Can it store that big messages?

    Apparently...

    Cannot remember the limits of HMB anymore but it has some. :)

    The "biggest" limit is, the maximum 16MB size of the total message base.


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Wednesday, November 30, 2022 12:06:29
    Hi Tommi,

    On 2022-11-30 12:59:11, you wrote to me:

    You can thank Dan Richter also, his messages are getting bigger and
    bigger every day. 260k today. ;)

    It doesn't bother me, I'm not connected to the file announce areas in FidoNet. ;-)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/360 to Wilfred van Velzen on Wednesday, November 30, 2022 13:47:38
    Hello, Wilfred van Velzen.
    On 30/11/2022 13.02 you wrote:

    Hi Tommi,
    On 2022-11-30 12:55:07, you wrote to me:
    That shouldn't matter for a rescan. The full message is already stored
    in there...
    In case of hudson also?
    My DUPE area is in hudson. There were no problems importing the big messages in there.

    Good to know.

    Can it store that big messages?
    Apparently...
    Cannot remember the limits of HMB anymore but it has some. :)
    The "biggest" limit is, the maximum 16MB size of the total message base.

    And max 200 areas. Well it was good enough for SuperBBS. :)


    Tommi

    --- HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1666961899000 HotdogEd/2.13.5
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Carol Shenkenberger@1:275/100 to Carlos Navarro on Sunday, December 11, 2022 12:02:16
    Re: rescanning and long messages
    By: Carlos Navarro to Wilfred van Velzen on Mon Nov 28 2022 08:40 pm

    It seems that FMail (at least the Win32 version) has issues when rescanning echos that have long messages.

    I've done some test and checked the PKTs -- long messages seem to be cut at around 40K.

    Carlos


    Probably a snippit from code back when some BBSes would crash the message base on ones longer than that.

    xxcarol
    --- SBBSecho 2.11-Win32
    * Origin: Shenk's Express telnet://shenks.dyndns.org (1:275/100)