>>  MvdV> No last read pointers,

 >> they are in the JLR files... each user has a CRC32 of their
 >> name and then there are two pointers... one is last read
 >> and the other is last seen or some such... this gives one
 >> the ability to hop through the base and then have a set
 >> starting point...

 MvdV> There is a .JLR file for each of the three JAM areas that I
 MvdV> set up. But they are zero length files.....

ewww... if the base has been accessed, there should be a 16byte record for
each user that has accessed the base... if you have 2 users and one
accesses every base and the other accesses only one base, then all JLRs
will be 16bytes except for the one that both access which will be
32bytes...

 >>  MvdV> no reply linking,

 >> depends on the tosser, to an extent... JAM was designed for
 >> MSGID/REPLY linking for true(r) threading than the old
 >> subject line linking...

 MvdV> Does Fmail do true reply linking?

can't remember at the moment... i'm running FMail 1.48 and have the
following settings...

Update reply chains  Yes
Sort new messages    No
ΘΝ Use subject       No


those are under Misc -> messagebase

 >>  MvdV> seen by and path are missing,

 >> those are within the JHR files... or should be, anyway...

 MvdV> Nope. not to be found.

hummm... i see them in my stuff here but they are pretty short as the setup
is for one of my points and it pulls only the local areas...

oh! make sure that each area has the setting "Imp. Seenby" set to
yes... that should at least get the seenbys into the bases...

in one JAM code package i have, seenbys, flags and tzutc were left as ID
2000 (unknown kludge)... i modified that code to put them with their proper
ids and some software does see them while other doesn't... i did that back
in july 2004 but can't lay my hands on the notes i had from the testing of
the different packages... there weren't many that i tested, though...
fastecho, fmail, remoteaccess, timed and the frontdoor stuffs are likely
the only ones i really looked at...

 >> if not there, then possibly hidden behind ^a in the JDT files...

 MvdV> No, not there either...

hummm... that's wierd... what are you using to look with? i use LIST.COM
but most any hex viewer should work...

 >>  MvdV> mail entered locally is not exported.
 >>
 >> at all or does it require a complete message base scan to
 >> get them out?

 MvdV> Not at all. Not even with a complete massage base scan.

ewww... what version of FMail?

 >>  MvdV> The fmail doc mentiones a file ECHOMAIL.JAM but I
 >>  MvdV> can't locate that anywhere.

 >> it should be located in the same place as the possibly
 >> empty HMB files...

 MvdV> Nope. Nowhere to be found.

hummm... it should contain the base name and the message number needing exporting...

 >>  MvdV> Well, I guess, it is this buggy editor that comes with
 >>  MvdV> InterMail 2.50 that must be the problem then... :-(

 >> it may very well be... have you tried another JAM capable
 >> editor on those same bases to see?

 MvdV> No, I wanted to eliminate Fmail as the source of the problems
 MvdV> first. That is why I asked here if anyone had similar problems
 MvdV> with Fmail and Jam.

ahhh... well, from what i see over here, fmail shouldn't be part of the problems...

 MvdV> I recently upgraded from InterMail 2.29 to 2.50. I had a
 MvdV> problem making the old mailer recognize IP flags. That problem
 MvdV> is solved with the upgrade.

mmmhummm...

 MvdV> But now I seem to be stuck with a buggy editor. At first I was
 MvdV> pleasantly surprised to see that the IM 2.50 editor was
 MvdV> upgraded to support JAM (And a few more). But now it has
 MvdV> turned into disappointment. Not only does in not properly
 MvdV> support JAM, but it got a few bugs in the Hudson section as
 MvdV> well now. Every once in a while it just crashes with a file
 MvdV> access error or something. Didn't have these problems with
 MvdV> 2.29. And I can't just go back to the old editor as Peter
 MvdV> changed something in the index files for the nodelist. :-(

;(

 MvdV> Maybe it is time to dump InterMail alltogether...

possibly...

 MvdV> Problem is that I don't want pay again for a mailer that I am
 MvdV> not really using anyway. The POTS mailer just sits there
 MvdV> watching the semaphore flags and exits on mail received. Once
 MvdV> every three month there is this oddball sysop who crashes me a
 MvdV> pointlist segment. That is all it is doing these days. I
 MvdV> upgraded so that I had a version that I could train NOT to
 MvdV> call nodes flagged as IBN.

i hear that... there are some free mailers out there... what OS are you
running? radius does a nice job and is what i use on the point system with
fmail and timed... the main bbs is all FD, RA and FE with TimED on the side
and all are beta products except TimED...

 MvdV> I am also not enthousiastic about having to go through the
 MvdV> learning curve again. I like what I'v got because I am used to
 MvdV> it.

i know that feeling... its why i haven't left the family i've been running
all these years...

)\/(ark