Hi mark,
On 2016-10-23 19:21:44, you wrote to me:
AP>>> I need to be able to purge the message bases (as they do get quite
AP>>> large and slow things down) and retain more than 9999 messages.
WV>> I've changed that to a maximum of 65535, for the next release. ;)
ml> that's crazy... especially when JAM can have 2M messages and at least MSG
ml> can store up to 99999999...
Well it's better than the current 9999. And as the config file stores it as a
16 bits value, that's all I can do without making things complicated... ;)
AP>>> I also need to be able to pack the jambases without renumbering
AP>>> them.
WV>> Why do you need that?
ml> some software doesn't take kindly to renumbering the messages underneath
ml> it... JAMNNTPD comes to mind...
So it stores last read pointers in it's own config? And doesn't use the .jlr
file for that, as it is supposed to?
ml> so why pack, you ask? to remove deleted and dead message bodies...
ml> every time you edit a JAM message, the header is updated to the new message
ml> body location and the old one is left floating as trash...
ml> packing the message bases removes the dead wood from deletions and edits...
I know that. ;)
Bye, Wilfred.
--- FMail-W32 1.73.0.16-B20161023
* Origin: FMail development HQ (2:280/464)
|
