It would be good to find a way to alert the sysop and display in MIS2 the output of any lines added to the errors.txt file. I think there's a risk things can get noted there and easily overlooked.
That is actually the reason the log exists. I think it was discussed in the WHATSNEW when I started created the errors.log but maybe not. The
idea is the same as from Mystic2demo also where those are sent
optionally as e-mail or text message notifications. I just have to tie
it all together once I get MIS2 stable.
I was planning to have an "ERRORS" tab in MIS that lights up when a new one comes through, but I am thinking now that I may just have an entire
So, I uploaded a file that was a zip file that contained a nodelist inside. The nodelist text file was named nodelist.305
The mutil merge nodelist utiltiy wouldnt extract the nodelist zip file anmed nodelist.zip. If I renamed it to nodelist.z00 it extracted fine.
Can you make the mutil utility also extract zip files, for people who
just create a standard zip file with no numerics in the ending?
So, I uploaded a file that was a zip file that contained a nodelist inside. The nodelist text file was named nodelist.305
The mutil merge nodelist utiltiy wouldnt extract the nodelist zip file anmed nodelist.zip. If I renamed it to nodelist.z00 it extracted fine.
Can you make the mutil utility also extract zip files, for people who
just create a standard zip file with no numerics in the ending?
So, I uploaded a file that was a zip file that contained a nodelist inside. The nodelist text file was named nodelist.305
The mutil merge nodelist utiltiy wouldnt extract the nodelist zip file anmed nodelist.zip. If I renamed it to nodelist.z00 it extracted fine.
Can you make the mutil utility also extract zip files, for people who just create a standard zip file with no numerics in the ending?
There is a standard filename format and instructions for how these lists are >supposed to be distributed through FTN networks, and Mystic simply follows the >standard.
For example, if FSX distributes "FSX-NET.ZIP" as its Information pack and its >nodelist as "FSX-NET.Z65" following the standard, you can see how this could >become an issue because the merger would be trying to merge FSX-NET.ZIP too.
If the information pack somehow contained a file that had a numeric extension, >it could end up merged into a Nodelist, potentially corrupting the nodelist >which in turn could break sending Netmail (if you force nodelist compliance), >and breaks sending mail to nodes that aren't configured in Echomail Nodes.
--- Mystic BBS v1.12 A37 2017/12/08 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
In Echomail Node editor, page 4 (BinkP) can you please make the hostname field display a bit bigger. Adding in digitalwurmhole.ddns.net:24556 I only see digitalwurmhole.ddns displayed. I think there enough screen
real estate to be able to widen that field some more to the right :) Thanks!
When adding passwords in on page 2 (security) how about setting the TAB key to move between all three fields and auto populate each with the same password as entered in the above field?
only see digitalwurmhole.ddns displayed. I think there enough screen real estate to be able to widen that field some more to the right :) Thanks!
Fixed.
When adding passwords in on page 2 (security) how about setting the T key to move between all three fields and auto populate each with the password as entered in the above field?
I'll see what I can figure out.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 200:33:05 |
| Calls: | 2,083 |
| Calls today: | 1 |
| Files: | 11,139 |
| Messages: | 947,927 |