Hey all,

Looking for someone to test the A44 prealpha upgrade.

I finally got the new theme system to workable, at least enough to get a release out (which should also fix the date bug in MUTIL). Keep in mind this has a LOT of changes. The theme editor is only somewhat working.

I have versions for Windows and Linux up.

More to come!

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

On 17 Jan 2020 &4, g00r00 said the following...

Hey all,

Looking for someone to test the A44 prealpha upgrade.

I finally got the new theme system to workable, at least enough to get a release out (which should also fix the date bug in MUTIL). Keep in mind this has a LOT of changes. The theme editor is only somewhat working.

Happy to see ya back! I did have a bug request possible I posted else where but will post it here as well the acs OV and -V can not be checked on a new user even after doing the verification on their first logon; I checked this a couple times and only becomes available after the user logs out and back in then it can check and do it properly.

Cheers!
Pequito

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Welcome back!

I posted this into another echo and figured paste it here as a possible bug:

---
I had been playing with a newer feature you added within the last year and
may have found a bug in the feature for menu command -V.

When using this with OV does not seems to work after a new user signs up for
a new account; will work after the user logs out and logs back into the BBS.

I did test this with the log on after new account had been created when
testing this and also turned this off with the same results. Each time the user would need to log out and back onto the BBS to see the -V for email verification to pop up for them.

Thought would share this for possible bug in the current version 1.12 a43; I run on linux/64.
---

Cheers!
Pequito

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Happy to see ya back! I did have a bug request possible I posted else where but will post it here as well the acs OV and -V can not be checked on a new user even after doing the verification on their first logon; I

I will look into this, thank you!

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

testing this and also turned this off with the same results. Each time the user would need to log out and back onto the BBS to see the -V for email verification to pop up for them.

I think this is fixed now in the latest A44 prealpha. Thank you and let me know if you do end up trying it and you still have issues.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

On 18 Jan 2020 &4, g00r00 said the following...

testing this and also turned this off with the same results. Each ti the user would need to log out and back onto the BBS to see the -V fo email verification to pop up for them.

I think this is fixed now in the latest A44 prealpha. Thank you and let me know if you do end up trying it and you still have issues.

Thank you g00r00 will test this tonight and or tomorrow :) Nice to see you back around =D

Cheers!
Pequito

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

On 17 Jan 2020 &4, g00r00 said the following...

Hey all,

Looking for someone to test the A44 prealpha upgrade.

I will be doing this in the next 12 hours I see some pretty big changes with themes; also since we are breaking down this stuff can we move the data file stuff for file bases etc out of the data folder to like an fbase mbase folder under data so can keep the data folder clear for the other items we edit/change? Just an idea :P

Cheers!
Pequito

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

On 17 Jan 2020 at 09:52a, g00r00 pondered and said...

Hey all,

Looking for someone to test the A44 prealpha upgrade.

Hi and welcome back :)

Yep have migrated the 1/100 HUB to the pre-alpha that popped up the other day and posted a couple of comments to this echo earlier about that. But happy to repost etc. if that helps. I have also spun up a fresh install to poke at
which I can report stuff as I find it. You'll see there are others here that have done some upgrades and spotted stuff too :)

release out (which should also fix the date bug in MUTIL). Keep in mind this has a LOT of changes. The theme editor is only somewhat working.

Thanks! Could you please take a look at a few other issues (SEEN-BY lines and wrapping of text) that I have been in touch about by email? It would be great if the next version could address those.

..oh and thanks for the updates level 3 logging in the way tossing and
packing is being reported. Very helpful.

Could you also enable the logging menu functionality in this build?

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hey g00r00,

Please have a look in your Gmail for a mail coming from me.

Reach out to me if any questions.

Cheers!

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

Looking for someone to test the A44 prealpha upgrade.

Hey g00r00, testing on Ubuntu 18.04.3 x64. Upgraded from A43 today. No big deal, the prompts.dat/prompts.txt thing you've likely heard about, but aside from that things worked out.

I noticed my <bbs>/scripts/ directory was moved but its subdirectories were not. Same with <bbs>/text/.

Otherwise, all good! I'm glad to see more mpy work taking place :)

--- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
* Origin: monterey bbs (21:1/168)

20 Jan 20 16:11, you wrote to g00r00:

Thanks! Could you please take a look at a few other issues
(SEEN-BY lines and wrapping of text) that I have been in touch
about by email? It would be great if the next version could
address those.

and maybe all the other FTN bugs:

wrong file timestamps in binkp (offsetted by the timezone)

wrong format in the binkp time field (but that is only informational, afaik)

wrong month in the pkt header

i think the utf-8 problems are related to the line btmreaking bug and should disapear if line breaking is disabled

did i forget something?





* Origin: 🌈 (21:1/151)

On 17 Jan 2020, g00r00 said the following...

Looking for someone to test the A44 prealpha upgrade.

Sounds like several of us have upgraded so far.

Win32 version. Backed everything up first after which I ran through and ran "install replace c:\mystic" then "install extract prompts.dat", "upgrade.exe" and finally "mplc -all" (mplc -all was left out of the upgrade.txt by the
way"

Created the new directories, copied my prompts over properly. Only issue I've seen is that if you have subdirectories in the script dir it does not create those in the new script directory. Had to manually copy that stuff over.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A44 2020/01/16 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)

Thanks! Could you please take a look at a few other issues (SEEN-BY
lines and wrapping of text) that I have been in touch about by email? It would be great if the next version could address those.

Yep I will have to check my e-mail unless you want to retype here. I've been neglecting e-mail a lot lately (ie I haven't been reading it since maybe November sometime)

At the current moment I don't know of the SEEN-BY issue but I will of course get it cleared up ASAP once I do!

..oh and thanks for the updates level 3 logging in the way tossing and packing is being reported. Very helpful.

No problem, I am pretty sure it was by your request :)

Could you also enable the logging menu functionality in this build?

I had it working for a few things (MIS and the node logging I think?) but for some reason I commented it out.

When the date thing appeared after the new year I had to scramble to get the theme system usable, so I could release those prealphas. The upgrade.exe hadn't even been started for the theme conversion for example. Things were really rushed in these first prealpha due to the date issue, and a lot of things are half-done.

I'll try to get back to the logging and review why I commented the menu out, BUT the good news is that I did have the new logging system working
at least partially.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Hey g00r00, testing on Ubuntu 18.04.3 x64. Upgraded from A43 today. No
big deal, the prompts.dat/prompts.txt thing you've likely heard about,
but aside from that things worked out.

I noticed my <bbs>/scripts/ directory was moved but its subdirectories were not. Same with <bbs>/text/.

Sounds like I have a lot of touching up to do. To be perfectly honest I
never even did a Linux run-through before I built the prealphas. I tested my local Windows setup and when it worked I uploaded (because of the date issue).

The directories should have been moved/removed so something went wrong there.
I have heard about some weirdness with prompts.dat/prompts.txt but I will
need to look into it further.

The prompts.txt file isn't intended to have all of the prompts in it now though, just the "delta" between the prompts.dat and whatever your theme's prompts were at the time of conversion.

But yeah I really rushed things after I saw the 2020 date issue and a lot of
it is poorly tested/sloppy. Thank you to all of you brave souls taking the plunge :)

I have been slowly rewriting all of the theme system, some editors (new msg/file base editors, new theme editor, new prompts editor), logging, python stuff, etc over the past sevral months so this date bug completely caught me off-guard. I've even been experimenting with things like automated upgrades and online theme archives too.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

On 20 Jan 2020 at 07:08a, g00r00 pondered and said...

been neglecting e-mail a lot lately (ie I haven't been reading it since maybe November sometime)

At the current moment I don't know of the SEEN-BY issue but I will of course get it cleared up ASAP once I do!

Thank you, Yeah probably best if you just look for the 3-4 emails I sent and that should hopefully sum up quite a bit of what's been picked up.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 20 Jan 2020 at 09:33a, Oli pondered and said...

and maybe all the other FTN bugs:

Thanks for the list. I'm sure as time/energy permit g00r00 will look into
them. Feel free to expand on any you want here as the more specific you can
be into what you are reporting on the better.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I ran the update, but the /scripts folder was missing for me.

Tim N
admin@f4fbbs.com

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Files 4 Fun BBS (21:2/120)

I ran the update, but the /scripts folder was missing for me.

It should now end up in <bbs>/themes/default/scripts

--- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
* Origin: monterey bbs (21:1/168)

On 17 Jan 2020 &4, g00r00 said the following...

Hey all,

Looking for someone to test the A44 prealpha upgrade.

I finally got the new theme system to workable, at least enough to get a release out (which should also fix the date bug in MUTIL). Keep in mind this has a LOT of changes. The theme editor is only somewhat working.

Found one item seems to be limited on the path for the theme location, an example say I wanted to do:

/mystic/data/theme/ansi/menu instead of menus, this could be me or is there
a short way to do that from the fallbacks provided?

Cheers!
Pequito

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

At the current moment I don't know of the SEEN-BY issue but I will of course get it cleared up ASAP once I do!

Thank you, Yeah probably best if you just look for the 3-4 emails I sent and that should hopefully sum up quite a bit of what's been picked up.

The SEENBY should hopefully be fixed now!

If you get a chance to try it let me know, and if it works then I will spring on some more changes (the start of the stat tracking) that could totally break everything lol.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

wrong file timestamps in binkp (offsetted by the timezone)

Just double checked and the standard I am looking at says to give the Unix
time of the file. It does not say it should be UTC. But if you can find something official that clarifies that let me know.

wrong format in the binkp time field (but that is only informational, afaik)

Can you elaborate? Are you looking at an old version or something? Here is what it says:

_NUL "TIME remote_date_time"
remote_date_time format is described in [RFC822].

The format given fits that described in RFC822.

wrong month in the pkt header

Can you show this? There were some older versions where something like this would happen, but it was because of another BBS software that is no longer in development creating improper fields.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

I ran the update, but the /scripts folder was missing for me.

It should now end up in <bbs>/themes/default/scripts

well color me purple :)

Thank you!

Tim N
admin@f4fbbs.com

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Files 4 Fun BBS (21:2/120)

Found one item seems to be limited on the path for the theme location, an example say I wanted to do:

/mystic/data/theme/ansi/menu instead of menus, this could be me or is there a short way to do that from the fallbacks provided?

You don't have separate paths for those anymore. You have a root theme directory and all themes go in there. So there is only one path now that is configurable and thats where your themes go (in system paths).

Then the theme directory (say c:\bbsthemes\) has a directory one per theme. Under that is "text" "scripts" and "menus" directories. You cannot change those names.

The reason for this is because if you wanted to share your theme you just
zip your theme directory up and give it to someone and they drop it in their theme directory and it just works, without any configuration.

The reason for the prompt changes are so themes don't need to be upgraded
when new prompts are being added.

Its all moving towards automation, online theme archives and all that sort of stuff :)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Can you show this? There were some older versions where something
like this would happen, but it was because of another BBS software
that is no longer in development creating improper fields.

Mystic creates packets with the month off by one in the packet header,
for example in January, mystic sets the month as 1, whereas it should be
0.

Great to see you back by the way :)

Andrew


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

On 20 Jan 2020 &4, g00r00 said the following...

Found one item seems to be limited on the path for the theme location example say I wanted to do:

/mystic/data/theme/ansi/menu instead of menus, this could be me or i there a short way to do that from the fallbacks provided?

You don't have separate paths for those anymore. You have a root theme directory and all themes go in there. So there is only one path now
that is configurable and thats where your themes go (in system paths).

Then the theme directory (say c:\bbsthemes\) has a directory one per theme. Under that is "text" "scripts" and "menus" directories. You
cannot change those names.

Ah was hopeful to be able to despite sharing :P Thank you for confirming!

Cheers!
Pequito

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Mystic creates packets with the month off by one in the packet header,
for example in January, mystic sets the month as 1, whereas it should be 0.

Thanks, this has been fixed. Its amazing it went like a decade unnoticed!

Great to see you back by the way :)

Thanks! And thanks for the help getting that right!

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Mystic creates packets with the month off by one in the packet
header, for example in January, mystic sets the month as 1,
whereas it should be 0.

Thanks, this has been fixed. Its amazing it went like a decade
unnoticed!

I only noticed because I've been hex editing packets to / from mystic.
Trying to figure out why mystic won't route my netmails, yet both HPT
and crashmail do. Mystic routes other netmails fine, but I can't for the
life of me figure out what I am doing wrong.

This was my setup:

637:1/102 (Titan) <-> 637:1/100 (Mystic) <-> 637:1/101 (Magicka)

Netmail from 637:1/101 gets routed by 637:1/100 to 637:1/102 fine, but
when I go the other way, Mystic imports the netmail thinking it is
destined for it rather that 637:1/101.

I have studied packets going both ways and compared them a lot and they
both seem to be right. I was wondering if Mystic has some other logic to determine the destination besides the packed message headers.

I also noticed Mystic added the INTL kludge even if the zones wasn't
different, in fact I think mystic wouldn't route if the INTL kludge
wasn't there (I set FORCEINTL in crashmail to get it working).

I wasn't going to post this here as I am sure you have plenty to do and
I'm not sure if there is a bug in mystic or not (I want to say not, as
usually it's me with the bugs, I just am not sure)

Andrew



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

On 20 Jan 2020 at 04:59p, g00r00 pondered and said...

Thank you, Yeah probably best if you just look for the 3-4 emails I s and that should hopefully sum up quite a bit of what's been picked up

The SEENBY should hopefully be fixed now!

If you get a chance to try it let me know, and if it works then I will spring on some more changes (the start of the stat tracking) that could totally break everything lol.

Thank you. I'll test this tonight (my time) which is now... :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 20 Jan 2020 at 04:59p, g00r00 pondered and said...

The SEENBY should hopefully be fixed now!

I ran some tests tonight and updated the NET 1 HUB at 21:1/100

Posted from it and sent the tossed packet to Agency at 21:1/101

Here's how it looked at 1/101

[snip]

From: Paul Hayton
To: All
Subj: NET 1 HUB
Date: 01/21/20 20:51
Base: General Chat

@TID: Mystic BBS 1.12 A44
@MSGID: 21:1/100 6af6e043
@TZUTC: 1300
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 1//116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 13 @SEEN-BY: 1//134 136 137 138 139 140 141 143 144 145 146 147 148 149 150 152 15 @SEEN-BY: 1//154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 17 @SEEN-BY: 1//172 173 174 175 176 177 178 180 181 182 183 184 185 186 187 188 18 @SEEN-BY: 1//190 191 192 193 194 195 197 199 200 201 202 203 204 205 995 999 @SEEN-BY: 2//2/100 3/100 4/100 5/100
@PATH: 1/100
Has been updated to v1.12 A44 Windows/32 Compiled 2020/01/20 23:57:33

--- Mystic BBS v1.12 A44 2020/01/20 (Windows/32)
* Origin: fsxNet HUB (21:1/100)

[snip]

So as you can see there's some additional forward slashes showing at the
start of the second (and subsequent) SEEN-BY lines which don't look right to me. But I do think you're heading in the right direction with this one.
Thanks :)

I rolled back and reverted 1/100 to v1.12 A44 Windows/32 Compiled 2020/01/16 13:12:26 after this test.

If you get a chance to try it let me know, and if it works then I will spring on some more changes (the start of the stat tracking) that could totally break everything lol.

I took a quick look at the stats tracking and I like the UI display from the echomail node menu. Kinda hoping when you get time to work on this some more MUTIL can be configured to generate some reports based on templates that we have discussed in the past.

Thanks for starting on this stuff. Having stats to ascertain when a node last polled in/out is very helpful for a HUB setup.

20 Jan 20 17:03, you wrote to me:

wrong file timestamps in binkp (offsetted by the timezone)

Just double checked and the standard I am looking at says to give the
Unix time of the file. It does not say it should be UTC. But if you
can find something official that clarifies that let me know.

unix time is by definition UTC.

wrong format in the binkp time field (but that is only
informational, afaik)

Can you elaborate? Are you looking at an old version or something?
Here is what it says:

_NUL "TIME remote_date_time"
remote_date_time format is described in [RFC822].

The format given fits that described in RFC822.

Mystics BBS interpretation isn't accepted by the linux date command. I think it
was a missing + or space character. Some tiny detail was wrong.

wrong month in the pkt header

Can you show this? There were some older versions where something
like this would happen, but it was because of another BBS software
that is no longer in development creating improper fields.

I know that I've got from Avon's 1/100 Hub had a invalid month in December. AFAIK the packets were created by Mystic BBS A43. Fidonet mail packets weirdly use 0 to 11 (0: Jan, 11: Dec). I have no idea why, but that's the way it's specified. Mystic is one month off (1 to 12).

* Origin: 🌈 (21:1/151)

20 Jan 20 18:55, you wrote to apam:

Mystic creates packets with the month off by one in the packet
header, for example in January, mystic sets the month as 1,
whereas it should be 0.

Thanks, this has been fixed. Its amazing it went like a decade
unnoticed!

I only noticed it because crashmail complained in December (but tossed the packets anyway).

* Origin: 🌈 (21:1/151)

On 20 Jan 2020 at 04:59p, g00r00 pondered and said...

The SEENBY should hopefully be fixed now!

If you get a chance to try it let me know, and if it works then I will spring on some more changes (the start of the stat tracking) that could totally break everything lol.

Hi ho... OK day two so I tested the next build but sadly can only report the same issue observed as last night

[snip]

From: Paul Hayton
To: All
Subj: NET 1 HUB
Date: 01/22/20 20:03
Base: General Chat

@TID: Mystic BBS 1.12 A44
@MSGID: 21:1/100 925d3f75
@TZUTC: 1300
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 1//116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 13 @SEEN-BY: 1//134 136 137 138 139 140 141 143 144 145 146 147 148 149 150 152 15 @SEEN-BY: 1//154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 17 @SEEN-BY: 1//172 173 174 175 176 177 178 180 181 182 183 184 185 186 187 188 18 @SEEN-BY: 1//190 191 192 193 194 195 197 199 200 201 202 203 204 205 995 999 @SEEN-BY: 2//2/100 3/100 4/100 5/100
@PATH: 1/100
Has been updated to v1.12 A44 Windows/32 Compiled 2020/01/21 11:40:22

--- Mystic BBS v1.12 A44 2020/01/21 (Windows/32)
* Origin: fsxNet HUB (21:1/100)

[snip]

I have restored NET 1 HUB back to v1.12 A44 Windows/32 Compiled 2020/01/16 13:12:26

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

So as you can see there's some additional forward slashes showing at the start of the second (and subsequent) SEEN-BY lines which don't look
right to me. But I do think you're heading in the right direction with

I just noticed that the FSX mail doesn't seem to be getting to the BBS I was using (not sure if my replies have gone out either) so I am a bit behind.

I just fixed up the SEEN-BY again and I will make another build shortly, once
I get through all the of the messages here to get any other feedback I might have missed.

So there should be a build dated Jan 24th shortly that has the fix.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

Mystics BBS interpretation isn't accepted by the linux date command. I think it was a missing + or space character. Some tiny detail was wrong.

You'll need to be more specific than that. There are discrepancies about the date format all over from what I remember. For example, the standard reference a RFC that calls for 2 digit years, yet right after that they give an example date that uses 4 digit years. All of the implementations from my memory use 4 digit years and what Mystic sends (should) match what is sent by other
mailers like binkd

I'll gladly fix it up if we can determine what/if something is wrong.

I know that I've got from Avon's 1/100 Hub had a invalid month in December. AFAIK the packets were created by Mystic BBS A43. Fidonet mail packets weirdly use 0 to 11 (0: Jan, 11: Dec). I have no idea why, but that's the way it's specified. Mystic is one month off (1 to 12).

Gotcha. This was fixed!

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

Hi ho... OK day two so I tested the next build but sadly can only report the same issue observed as last night

Yep sorry, I wasn't getting messages here so I missed it.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

24 Jan 20 11:24, you wrote to me:

Mystics BBS interpretation isn't accepted by the linux date
command. I think it was a missing + or space character. Some
tiny detail was wrong.

You'll need to be more specific than that.

just compare it with the date format that binkd is using. the difference is at the end of the string. i don't think it's important. i only looked into this, because i thought that was the reason for the wrong file timestamps (but it's not).

the line breaking at 80 chars is much more problematic ...

* Origin: 🌈 (21:1/151)

On 24 Jan 2020 at 11:13a, g00r00 pondered and said...

I just noticed that the FSX mail doesn't seem to be getting to the BBS I was using (not sure if my replies have gone out either) so I am a bit behind.

My hunch is that MIS on Gryphon's system has auto IP blocked the 1/100 HUB :( Dan aka Black Panther had (at my request) logged in to leave him a message about this to see if that was the case. I can't telnet in as I use the same
IP. (219.89.83.33 and 2001:470:d:123::50)

The reason will be because for a while I have been using BinkD as the mailer for the HUB.. and for about a month also HPT do do the tossing to try and negate SEEN-BY issues (and some others I have posted about to you) but when
you resurfaced I switched 1/100 back to Mystic but help BinkD.

I have a hunch there may be some issues with the inbuilt BinkP server or
MUTIL or a combo of both leading to some packets not being sent to nodes. I have seen occasions whereby nodes report missing packets. Some checks at
1/100 seem to suggest that .HLO files and others sometimes seem to be missing links to compressed packets waiting for a node. This leads to compressed
files sitting in echomail\out not being sent even when a node polls in.

I has switched to BinkD initially to try and see if missing packets sent to a NET 1 node (Oli was very good at reporting these to me - thanks Oli :)) were resolved by just switching out the mailer... and it seemed to be the case.
Oli was reporting all packets coming in to him (he was comparing them to a
feed he was getting from 3/100 HUB also) but there were the other soft CR and wrapping issues also being seen as well.. that I think are more related to MUTIL and not the issue I'm waffling on about now :)

Anywhoo... thanks for the reply. I thought this may be the case with your
pause in responses. Unless you post at Cyberia my hunch is no outbound
polling of 1/100 would take place and with inbound polling of 1/100 being blocked it's a PITA

FIDOPOLL Version 1.12 A44 2020/01/16

Looking up address "21:1/120" in nodelist
Scanning 21:1/120
Queued 9 files (818243 bytes) to 21:1/120
Polling BINKP node 21:1/120 (Darryl Perry) by IPV4
Connecting to cyberiabbs.zapto.org
Connected IPV4 to 54.193.66.229
Error receiving data (Msg= Size=0/6336)
Connection lost
Authorization failed

Sigh...

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 24 Jan 2020 at 11:13a, g00r00 pondered and said...

I just fixed up the SEEN-BY again and I will make another build shortly, So there should be a build dated Jan 24th shortly that has the fix.

I tested the following and we're getting there but there is still an issue I think with the logic being applied.

Most lines were fine now in this test but the last line where the first NET 2 address happened to fall was messed up with an additional 2/

Take a look

[snip]

From: Paul Hayton
To: All
Subj: NET 1 HUB
Date: 01/25/20 12:22
Base: General Chat

@TID: Mystic BBS 1.12 A44
@MSGID: 21:1/100 f9576c79
@TZUTC: 1300
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 1/116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 133 @SEEN-BY: 1/134 136 137 138 139 140 141 143 144 145 146 147 148 149 150 152 153 @SEEN-BY: 1/154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 171 @SEEN-BY: 1/172 173 174 175 176 177 178 180 181 182 183 184 185 186 187 188 189 @SEEN-BY: 1/190 191 192 193 194 195 197 199 200 201 202 203 204 205 995 999 @SEEN-BY: 2/2/100 3/100 4/100 5/100
@PATH: 1/100
Has been updated to v1.12 A44 Windows/32 Compiled 2020/01/24 15:22:51

--- Mystic BBS v1.12 A44 2020/01/24 (Windows/32)
* Origin: fsxNet HUB (21:1/100)

[snip]

Hope that helps :)

Thanks for working on this one.

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

just compare it with the date format that binkd is using. the difference is at the end of the string. i don't think it's important. i only looked into this, because i thought that was the reason for the wrong file timestamps (but it's not).

The string for my timezone is identical to that of binkd, which is I thought what I had already said but maybe I didn't. I literally looked at the binkd code back in the day because the standard wasn't always clear.

I am willing to bet you saw a + on non-biased time zones (which I wouldn't see where I live because I am not in Asia/Austrialia).

BinkP references that RFC like I already mentioned, but then the example they give directly after that doesn't even follow the RFC format (lol). The Fidonet standard for TZ specifically says NOT to include a + but that software should be prepared to handle it if it does.

So which one do I follow? Mystic can follow the shoddy BinkP specification tha contradicts itself, or the FidoNet standard for supplying the TZ bias? Right now it follows the TZ FidoNet standard and doesn't include the + but I can change it to show the + just for BinkP TIME frame if that is what BINKD does.

the line breaking at 80 chars is much more problematic ...

Its not breaking, its word wrapping text. It was a requested feature both at the echomail and NNTP levels because of content getting lost.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

I tested the following and we're getting there but there is still an
issue I think with the logic being applied.

Thanks for the update. This is challenging to test because I don't have any system capable of reproducing the situation at the moment.

Along the echomail lines, I saw your message about potential issues with FLO files so I have introduced FLO.TXT! We got rid of the BUSYLOG and now we get another one ;)

I made a special build for you (anyone really) who wants to help locate any issues with FLO logs. The builds below will create a "flo.txt" in the same directory anytime one of the flow files are modified in any way. If there is some sort of error or issue with FLO it should be captured in that .txt file.

www.mysticbbs.com/downloads/prealpha/FLO

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

On 24 Jan 2020 at 03:59p, g00r00 pondered and said...

Thanks for the update. This is challenging to test because I don't have any system capable of reproducing the situation at the moment.

It's all good, just keep tweaking and I'll keep testing :)

Along the echomail lines, I saw your message about potential issues with FLO files so I have introduced FLO.TXT! We got rid of the BUSYLOG and
now we get another one ;)

I made a special build for you (anyone really) who wants to help locate any issues with FLO logs. The builds below will create a "flo.txt" in
the same directory anytime one of the flow files are modified in any
way. If there is some sort of error or issue with FLO it should be captured in that .txt file.

OK ta... so to clarify this build looks at files created by MUTIL for a BSO mailer weather it be Mystic's inbuilt BinkP server or the one I am currently using to send traffic around (BinkD)? Am I understanding that right?

I need to ensure SEEN-BY's are sorted before I drop it into NET 1 HUB
though.. else I create more issues for nodes while trying to test for this
next thing. Make sense?

Gotta say the one thing that I really like that BinkD offers over the inbuilt combo of Mystic BinkP server and Fidopoll is that when calling out to nodes BinkD can poll many at once and the delivery of CRASH packets to nodes is lightning fast vs the sequential one node polled at a time manner of Fidopoll...

All of which is a roundabout way of asking do you think Fidopoll will ever be enabled to allow for multiple outgoing concurrent sessions like BinkD offers?
I think also the plan was to move the fidopoll code into the BinkP server at some stage?? Does that sound right or am I way off?

Anywhoo I'll sit tight for now but will pull down the software and wait to
read your replies :)

Thanks James..

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)