• Changes to message reading

    From apam@21:1/126 to All on Fri Nov 1 14:46:17 2019
    I've made some changes to the message reading interface....

    More strings changes (sorry Tiny)

    Let me know what you think ... especially about the conference -> area
    bit down the bottom...

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Al@21:4/106 to apam on Thu Oct 31 22:05:36 2019
    Let me know what you think ... especially about the conference -> area
    bit down the bottom...

    I like it. I see the TZ in the date as well.. I'm seeing the TZUTC kludge
    as well.. :)

    Ttyl :-)
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From apam@21:1/126 to Al on Fri Nov 1 15:35:32 2019
    Let me know what you think ... especially about the conference -> area
    bit down the bottom...

    I like it. I see the TZ in the date as well.. I'm seeing the TZUTC
    kludge as well.. :)

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

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Al@21:4/106 to apam on Thu Oct 31 22:45:18 2019
    Yeah, I'm checking in two places for TZUTC now, seems HPT does things a little differently. Sadly HPT doesn't seem to import the OADDRESS field into the JAM base, and it scrubs it out of messages it exports.
    Otherwise in the from field you would see an ftn address and nodelist entry name as well.

    What is the OADDRESS field?

    I do see my own address in the from field when I post a message but once
    hpt scan runs it disappears, I don't know why. Is that the origin
    address?

    I know hpt quite well but I have always used it with Squish bases, so I
    am not as familiar with how it works with Jam.

    Ttyl :-)
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Al@21:4/106 to apam on Thu Oct 31 22:53:22 2019
    Yeah, I'm checking in two places for TZUTC now, seems HPT does things a little differently. Sadly HPT doesn't seem to import the OADDRESS field into the JAM base, and it scrubs it out of messages it exports.
    Otherwise in the from field you would see an ftn address and nodelist entry name as well.

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

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

    Ttyl :-)
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From apam@21:1/126 to Al on Fri Nov 1 16:06:27 2019
    Yeah, I'm checking in two places for TZUTC now, seems HPT does things a little differently. Sadly HPT doesn't seem to import the OADDRESS field into the JAM base, and it scrubs it out of messages it exports.
    Otherwise in the from field you would see an ftn address and nodelist entry name as well.

    I've also noticed when reading messages in golded that every message
    has an origin address but I don't see that in Magicka. Netmail messages have both an origin and destination address in golded, but in Magicka I 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.

    It's all a little blurry for me since I don't have much experience with Jam message bases but I don't mind bringing up questions or issues in
    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)
  • From Al@21:4/106 to apam on Thu Oct 31 23:23:30 2019
    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.

    That would be nice, but it all works as is anyway.

    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.

    I don't think tear and origin lines are needed in netmail. Netmail that I
    write in golded doesn't have either so that method may fail at times.

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

    I have gotten many answers in that area (fidosoft.husky) so it might come
    in handy. Quite a technical bunch in there.. when they are talking.. :)

    Ttyl :-)
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From apam@21:1/126 to Al on Fri Nov 1 16:34:35 2019
    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.

    That would be nice, but it all works as is anyway.

    Just added :)

    I don't think tear and origin lines are needed in netmail. Netmail that
    I write in golded doesn't have either so that method may fail at times.

    Yeah, I guess if it fails it fails and will fall back to what you have
    now. It's only a graphical thing so it's not the end of the world :)

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Al@21:4/106 to apam on Thu Oct 31 23:47:32 2019
    That would be nice, but it all works as is anyway.

    Just added :)

    Yep, that does look good.. :)

    I don't think tear and origin lines are needed in netmail. Netmail that
    I write in golded doesn't have either so that method may fail at times.

    Yeah, I guess if it fails it fails and will fall back to what you have now. It's only a graphical thing so it's not the end of the world :)

    I have 2 netmails in my fsx netmail area, one has tear and origin lines
    and one doesn't but they both correctly display the correct origin and destination addresses.. :)

    Ttyl :-)
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Oli@21:1/151 to apam on Fri Nov 1 12:07:37 2019
    On Fri, 1 Nov 2019 15:35:32 +1000
    "apam -> Al" <0@126.1.21> wrote:

    Sadly HPT doesn't seem to import the OADDRESS field
    into the JAM base, and it scrubs it out of messages it exports.

    This is weird. Is it a bug in HPT? I don't see any reason to not put the originating address into the OADDRESS field.

    ---
    * Origin: (21:1/151)
  • From Tiny@21:1/130 to apam on Fri Nov 1 13:09:58 2019
    Quoting apam to All <=-

    More strings changes (sorry Tiny)

    It's all good. Still using the stock strings file. I won't modify
    it again until you release a non alpha I think.

    Let me know what you think ... especially about the conference -> area
    bit down the bottom...

    Updating now.

    Shawn

    ... The trouble with facts is that there are so many of them.

    --- EzyBlueWave V3.00 01FB001F
    * Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)
  • From apam@21:1/126 to Oli on Sat Nov 2 10:49:09 2019
    On Fri, 1 Nov 2019 15:35:32 +1000
    "apam -> Al" <0@126.1.21> wrote:

    Sadly HPT doesn't seem to import the OADDRESS field
    into the JAM base, and it scrubs it out of messages it exports.

    This is weird. Is it a bug in HPT? I don't see any reason to not put
    the originating address into the OADDRESS field.

    I don't know if it's intentional by the HPT guys or not, you'd have to
    ask them.

    Andrew

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