Hello mark,

 >  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...

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

 >  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...

Does Fmail do true reply linking?

 >  MvdV> seen by and path are missing,

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

Nope. not to be found.

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

No, not there either...

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

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

 >  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...

Nope. Nowhere to be found.

 >  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?

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

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

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

Maybe it is time to dump InterMail alltogether...

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

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

Cheers, Michiel

--- InterMail 2.50