Yes. Most (all?) tossers allow you to specify the full
path and filename for each area.
I keep mine in lettered subdirectories (\fido\a\a*,
There are probably old DOS based repair tools. I haven't
had a corrupt message base since I stopped using DOS so it
hasn't been an issue. I still keep full archives of
everything though (all incoming mail files are backed up as
they are, the message bases are backed up before and after
nightly maintenance and I have the mail tosser send a copy
of everything passing through to a local point address).
However.. Squish is probably the better of the two, should
it become damaged. Since it only has one real data file,
the rest can be regenerated from that. JAM keeps the
message text and metadata in two separate files so if they
get out of sync, you're hosed.
In Maximus the Squish areas have a maximum message limit of
65535. But I'm not sure if this is a limitation of Squish,
Maximus or editor. Would be handy to know.
Looks to be a Maximus limit. The Squish library used in
EleBBS (MkMsg) uses a signed 32bit integer for message
numbers (ie. 2^31-1, over 2 billion).
I'm also unsure what the maximum number of areas is for
In the Squish tosser documentation it says the maximum
number of areas is limited to memory. So this could be
virtually unlimited areas, if using disk swapping.
Pretty much. Since each area is its own set of files, any
area limits are in the software not the format.
|Location:||Riverside County, California|
|Nodes:||15 (0 / 15)|