Hello mark,

WvV> Btw: I'm still looking for good documentation for the hudson message
WvV>      base format, if anyone's got it?

ml> i'm not aware of any documentation on the HMB at all... the only thing i
ml> have that even comes close is source code... some would say that that is
ml> documentation enough 

It is ;-)
For my RISC OS !WimpLink Point system I have figured out how the message base
was configured at low level, by simply looking at it with a hex editer
and thwe flag list in the manual.
I did the same to my RISC OS e-mail program !Marcel.
The main reason for this examination was to correct broken messages,
and after that reindex the msg-base to use them again, in stead of deleting.
Sometimes I got tears from broken msg-bases ;-(.
The indexing system is more complex to figure out, but I am not a C
programmer.
What one can do is make a test system with an emty msg-base,
write some messages with every possible flag and kludge,
and receive some to it, and then examine the low level contents.
With the source code besides it, it must be possible to get the structure clear
for at least 90 % I think.
May be the FTSC documents can help to get it all clear?

It could be something like this:

From AKA
To AKA
msg date in unix time
received or sent / polling date in unix time
From:
To:
Subject
EchoMail Area Tag
8 bytes msg flags
Kludges with ctrl A
unformatted msg text (mostly the biggest part ;-)
tagline
tearline and product name
Origin
SEEN-Bye's
Kludges with Ctrl A
Path aka's
Closing byte Hex 0 (zero)

That last one is important as msg separator.
This list has to be finetuned to create the right msg format.
Hm, Hudson, wasn't that a river near New York found by some Dutchman?
Good luck with it.

Henri.

---
 * Origin: Connectivity is the Future; UniCorn BBS 31 26 4425506 (2:280/1208)