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)"?
The big messages were tossed and exported to all links without issues
when they arrived. I only found this problem with rescans.
The big messages were tossed and exported to all links withoutI think I know the answer, but I ask anyway: What msgbase format
issues when they arrived. I only found this problem with rescans.
are you using?
??>> 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.
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?
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.
>> 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...
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! ;-)
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. :)
You can thank Dan Richter also, his messages are getting bigger and
bigger every day. 260k today. ;)
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.
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
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 105 |
Nodes: | 16 (0 / 16) |
Uptime: | 06:14:04 |
Calls: | 5,878 |
Calls today: | 9 |
Files: | 8,496 |
D/L today: |
846 files (323M bytes) |
Messages: | 344,667 |
Posted today: | 3 |