• New messages

    From Al@21:3/107.1 to Apam on Wed Oct 9 00:35:12 2019
    Hello Apam,

    One thing I noticed here with HPT. I just connected a bunch of areas and
    some new messages arrived so I added the area to magicka and then restart magicka and log in. When I go to the new area where new mail had arrived
    there are no messages.

    And when I look at the message bases they are empty. The files exist but
    are all 0 bytes except the .jhr file is 1024 bytes. It looks like magicka didn't like the existing files and blanked them out.



    Ttyl :-),
    Al



    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: Equinox BBS - Penticton, BC Canada (21:3/107.1)
  • From Al@21:3/107.1 to Apam on Wed Oct 9 01:52:08 2019
    Hello Apam,

    And when I look at the message bases they are empty. The files exist but are all 0 bytes except the .jhr file is 1024 bytes. It looks like magicka didn't like the existing files and blanked them out.

    I've been seeing this tonight. One thing I notice is that the message
    base files hpt creates, basename.jdt, .jdx and .jhr. It doesn't create basename.jlr but I notice when magicka creates bases it creates the .jdt,
    .jdx, .jhr and .jlr files.

    Message base files with those three extentions do exist but for some
    reason magicka blanks them out and creates new (empty) message base
    files.

    Once magicka has created message bases hpt tosses to them happily.

    Something to do with hpt maybe?


    Ttyl :-),
    Al



    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: Equinox BBS - Penticton, BC Canada (21:3/107.1)
  • From Oli@21:1/151 to Al on Wed Oct 9 11:09:57 2019
    Message base files with those three extentions do exist but for some reason magicka blanks them out and creates new (empty) message base
    files.

    Once magicka has created message bases hpt tosses to them happily.

    Something to do with hpt maybe?

    Magicka should not wipe a message base without permission from the sysop ;). I think it's unlikely that it is a problem with hpt. Tossers usally don't create *.jlr files, *.jlr only stores the user's lastread info. Maybe Magicka tries to
    open that files, gets an error and thinks it's best to recreate the message base?



    * Origin: 🌈 (21:1/151)
  • From apam@21:1/125.99 to Al on Wed Oct 9 19:28:00 2019
    I've been seeing this tonight. One thing I notice is that the message
    base files hpt creates, basename.jdt, .jdx and .jhr. It doesn't
    create basename.jlr but I notice when magicka creates bases it
    creates the .jdt, .jdx, .jhr and .jlr files.

    Message base files with those three extentions do exist but for some
    reason magicka blanks them out and creates new (empty) message base
    files.

    Once magicka has created message bases hpt tosses to them happily.

    Something to do with hpt maybe?

    More likely something to do with jamlib (which magicka uses). I think I actually remember this from previously.

    I'll have a look into it.

    Andrew

    --- MagickaBBS v0.12alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From apam@21:1/125.99 to Oli on Wed Oct 9 19:31:02 2019
    Tossers usally don't create *.jlr files, *.jlr only stores the user's lastread info. Maybe Magicka tries to
    open that files, gets an error and thinks it's best to recreate the message base?

    Looks like that might be exactly what is happening. JamLib seems to give
    an error if the last read file isn't existing.

    Andrew

    --- MagickaBBS v0.12alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From apam@21:1/125.99 to Al on Wed Oct 9 19:46:42 2019
    Message base files with those three extentions do exist but for some
    reason magicka blanks them out and creates new (empty) message base
    files.

    I've just pushed a fix to jamlib that should hopefully not fail to opem a
    jam base with out a jlr file. (and instead create an empty one).

    You will have to make clean again so jamlib is recompiled.

    Andrew

    --- MagickaBBS v0.12alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From Al@21:3/107.1 to Oli on Wed Oct 9 02:54:36 2019
    Magicka should not wipe a message base without permission from the sysop ;).

    That would be better, yes. :)

    I think it's unlikely that it is a problem with hpt. Tossers usally
    don't create *.jlr files, *.jlr only stores the user's lastread info. Maybe Magicka tries to open that files, gets an error and thinks
    it's best to recreate the message base?

    Hpt is a pretty study tosser as is all the husky stuff. I haven't used it
    with JAM message bases much so I'm a little in the dark here.

    I notice that msged uses a .sql instead of the .jlr to track a persons
    last read messages. It works but if you carry on with another editor it
    won't know where you left off.

    Ttyl :-),
    Al

    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: Equinox BBS - Penticton, BC Canada (21:3/107.1)
  • From Al@21:3/107.1 to apam on Wed Oct 9 02:56:58 2019
    More likely something to do with jamlib (which magicka uses). I think I actually remember this from previously.

    I'll have a look into it.

    I have a few new areas so I'm going to add them to magicka and touch the
    .jlr file before restarting magicka. That might do the trick.

    Ttyl :-),
    Al

    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: Equinox BBS - Penticton, BC Canada (21:3/107.1)
  • From Al@21:3/107.1 to apam on Wed Oct 9 03:16:22 2019
    I've just pushed a fix to jamlib that should hopefully not fail to opem a jam base with out a jlr file. (and instead create an empty one).

    Yep, that seems to have fixed it. I just added a few areas and was able
    to read them without issue. :)

    Ttyl :-),
    Al

    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: Equinox BBS - Penticton, BC Canada (21:3/107.1)
  • From Oli@21:1/151 to Al on Wed Oct 9 12:35:13 2019
    I notice that msged uses a .sql instead of the .jlr to track a persons last read messages. It works but if you carry on with another editor
    it won't know where you left off.

    .sql is for squish message bases. Is this a bug in smapi, in msged or intentional? I wonder if the file has just the wrong name or if it's using a real Squish .sql file (I don't know if .sql and .jlr are different or the same structure)

    * Origin: 🌈 (21:1/151)
  • From Al@21:3/107.1 to Oli on Wed Oct 9 03:59:02 2019
    .sql is for squish message bases.

    Yep, but if you read jam message bases with msged it will create and use
    .sql files as last read pointers instead of .jlr.

    Is this a bug in smapi, in msged or intentional?

    I suspect it's an old bug that was not know for a long time. Now the
    developes of msged are long gone..

    I wonder if the file has just the wrong name or if it's using a real
    Squish .sql file (I don't know if .sql and .jlr are different or the
    same structure)

    That's possible. I don't know what the contents of the .sql is, it may
    just be a wrong extention being used. I'm not really sure.

    Sure does look funny though.. :)

    Ttyl :-),
    Al

    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: Equinox BBS - Penticton, BC Canada (21:3/107.1)
  • From apam@21:1/125.99 to Al on Thu Oct 10 11:57:38 2019
    That's possible. I don't know what the contents of the .sql is, it
    may just be a wrong extention being used. I'm not really sure.

    It could be using sqlite or some other mechanism for last read pointers.
    For a mail reader with only one user, it could be more practical to use individual message read/unread flags rather than a "last read" pointer.
    In which case sqlite might be a good way of doing it.

    Andrew

    --- MagickaBBS v0.12alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From Al@21:3/107.1 to apam on Wed Oct 9 19:53:48 2019
    It could be using sqlite or some other mechanism for last read pointers. For a mail reader with only one user, it could be more practical to use individual message read/unread flags rather than a "last read" pointer.
    In which case sqlite might be a good way of doing it.

    I think msged only supports *.MSG, Squish and Jam. It works with the .sql lastread file when reading Jam or Squish message areas. I think it should
    use the .jlr when Jam areas are used.

    Ttyl :-),
    Al

    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: Equinox BBS - Penticton, BC Canada (21:3/107.1)