| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: JAM area limits |
Hi mark, On 15 May 14 16:11, mark lewis wrote to Manuel Adorni: about: "Error": ml> the limits of JAM message bases are exceedingly large but some ml> programs may not properly support the maximum limits... I know one limit in FMail. When a JAM area grows bigger then 0x3FF0 = 16368 messages, it messes up the last read pointer on import of new messages. I have one such area on this point system. When it happens it shows >5000 new messages. I just have to scroll to the end of the list, and find out what the new messages are for myself. But that's it, the JAM area doesn't get unreadable or otherwise broken... So nothing like what Manual experienced. I already looked at this problem in the code, and there is no easy fix without a rewrite of that part of the code. I might have another look when it becomes too annoying, untill then I regard it as a cosmetic problem. ;) Wilfred. --- FMail-W32-1.68.3.69-B20140513* Origin: point{at}work (2:280/464.112) SEEN-BY: 3/0 633/0 267 280 281 402 640/384 712/0 848 770/1 @PATH: 280/464 712/848 633/280 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.