TIP: Click on subject to list as thread! ANSI
echo: fmail_help
to: mark lewis
from: Michiel van der Vlist
date: 2005-01-06 22:53:00
subject: Fmail and Jam

Hello mark,

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

And the one accessing the base is the editor....

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

 > those are under Misc -> messagebase

Check...

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

Check...

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

I use HE.EXE. That came with a cross assembler package. (METAI). It is just
a hex editor and as you say any hex viewer/editor should do it.

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

1.60

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

As I said, nowhere to be found...

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

It looks like it. Although  it worries me a bit that I can't find the seen
by and path information anywhere.

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

 > mmmhummm...

IM 2.29 has the flags hard codes. IM 2.50 allows for configuring them. But
that's not all. I patched the binary of IM 2.29 and sacrificed soem
obsolete flags to make room for some new flags. An then it turned out that
IM 2.29 randomly ignored flag when compiling the nodelist. IM 2.50 has that
bug fixed.

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

 > ;(

:( indeed..

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

 > possibly...

Well, I have no problem with the mailer, but the editor is less than
satisfactory. For one it does not support initials in quoting. Something
that I get harped over from time to time. I sort of expected this to be
taken care of in 2.50. But no..

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

Win98SE.

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

;-)

Cheers, Michiel

--- InterMail 2.50
* Origin: PA0MMV, Driebergen, NL (2:280/5555)
SEEN-BY: 633/267 270
@PATH: 280/5555 123/500 106/2000 633/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™.