Subj : RE: Changes to message reading
To   : Al
From : apam
Date : Fri Nov 01 2019 16:06:27

 ap> Yeah, I'm checking in two places for TZUTC now, seems HPT does things a
 ap> little differently. Sadly HPT doesn't seem to import the OADDRESS field
 ap> into the JAM base, and it scrubs it out of messages it exports.
 ap> Otherwise in the from field you would see an ftn address and nodelist
 ap> entry name as well.

 Al> I've also noticed when reading messages in golded that every message
 Al> has an origin address but I don't see that in Magicka. Netmail messages
 Al> have both an origin and destination address in golded, but in Magicka I
 Al> only see the origin address.

JAM message bases have subtypes for origin address (OADDRESS) and
destination address (DADDRESS) in crashmail it fills out (at least the
OADDRESS field). Which is where magicka pulls it's origin address from.

Magicka doesn't display destination addresses, I hadn't thought of
adding that, perhaps I can place it next to the TO field for netmails.

It's not an issue really - I should probably get the address from the
origin line of the message rather than rely on the mailer to fill it
out. 

 Al> It's all a little blurry for me since I don't have much experience with
 Al> Jam message bases but I don't mind bringing up questions or issues in
 Al> the fidosoft.husky message area.

I don't know what the correct way of doing things, if it's intentional
in HPT for some reason or not, I only learn as I go along. :)

Andrew

--- MagickaBBS v0.13alpha (Linux/x86_64)
 * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)

.