Subj : Follow-up on "Some A48 issues (summed up)" (as per 07/09/2022) To : g00r00 From : Bj”rn Wiberg Date : Sat Jul 09 2022 01:57 pm Hello g00r00! I hope all is well with you! On 03 Jul 2022, Bj”rn Wiberg said the following... BW> The following are the things that I'm currently experiencing BW> with the 2022/04/03 A48 prerelease, and some minor things I'd wish for Thanks a lot for fixing so many of these in the 07/07/2022 prerelease! I know that you're probably still working on things, but I still thought I would give an update regarding the new prerelease. The things that I'm still having problems with (and some new) would be the following: BW> * FTP uploads appear to corrupt the file base. If I scroll down the This is still a problem; as soon as I FTP upload a file to a file base that already has a file, it appears to corrupt the file base. This time I got parts of the login screen showing up when listing the base from within the BBS. But when editing the file, the Description is empty (although with a corrupted file base that might not be indicative of anything particular). BW> * There appears to be a "leftover" in the SysOp menu; the "(V) Voting BW> Booth Editor" option which attempts to call command "(*V) Unknown BW> Command", which doesn't exist any longer. Probably the (V) option BW> should be removed from the SysOp menu? (That one is still there.) BW> * For a normal account (not a QWK account), when selecting the message BW> bases to scan from the message menu, i.e. (MZ) Toggle new scan bases BW> with an empty Data field, Mystic appears to be selecting the wrong BW> message base when I enter a number: That one is still there. Now it appears to be selecting a message base in some other message group? Not sure, because I can't see any changes in the scanned list after entering some number. I do not get any error message of any kind. Also, related to this (and new, I think): * For a normal account (not a QWK account), when selecting the message bases to scan from the offline mail menu, i.e. (OS) Set QWK scanned bases with Data: /allgroups, the number one enters does not correspond to the base being toggled there either. For example: ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ ± QWK Message Area Scan Settings Local ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Area Scan Name ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1 Yes Private Messages (PMs) 2 Yes Private Messages (PMs) (SysOp Access) 3 No Duplicate Messages 4 Yes fsxNet Netmail 5 No fsxNet Netmail (SysOp Access) 6 No FSX_ADS: BBS and NETwork Ads 7 No FSX_ARTS: Arts + Artistic Chat 8 Yes FSX_BBS: BBS Support/Dev 9 No FSX_BOT: Automated Robot Posts 10 No FSX_CRY: Cryptographics (cut cut) ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Toggle: [#,#-#], [A]dd/[R]emove All, [?/List, Enter/Quit]: 10 2010: DOVE-Net Sysops Only will be scanned in QWK packets. ....so it appears to select the wrong message base. When checking the DOVE-Net message group, I find that #10 corresponds to the base that Mystic selected. But I wasn't even "standing" in the DOVE-Net message group (and it should be irrelevant).... (I'm using list compression, as earlier.) BW> * In the multinode teleconference, if one uses ASCII, the cursor is BW> positioned at the end of the line so that the text one writes always BW> gets wrapped. BW> I believe this is because the cursor gets positioned at the end of the BW> input field (whose background is not actually written when using BW> ASCII). Would it be possible for Mystic to position the cursor at the BW> beginning of the "invisible" input field if using ASCII? (Using BW> backspaces?) (That one is still there.) BW> * The str8 variable in archive_view.ini would need an extra space to BW> clear out the "Enter/View" text when searching. (I think that one is still there?) BW> * Read ACS checking for the POP3 server -- i.e. that it would return BW> Access denied if a user does not fulfil the Read ACS -- would be much BW> appreciated. It would make things consistent between the BBS interface BW> and the POP3 access method. (I think that one is still there?) Also, a few more things (I do not know if all have been present earlier) and suggestions: * 5mooth-mist25.ans is present in the text directory of the default theme. Should it be there? Perhaps for some gallery function or similar? * When editing user flags in the user editor, ANSI escape codes (e.g. arrow up yields a "P") toggle the corresponding flags. Would it be possible for Mystic to "filter out" anything with an escape before it? * When selecting a function/command in the menu editor, -R is listed after -S. * After uploading a file via FTP, the FTP command processor will become unresponsive until upload testing has finished (if one has enabled upload testing). Could Mystic send e.g. a "452 Requested action not taken. Still testing uploaded file. Please wait a little and try again." response to most commands during testing? Perhaps that would prevent batch uploads (mput), but maybe some commands (ls, cd etc.) where the user is waiting for a response would benefit from a 452 feedback response? * I still cannot get file download over the web to work. When clicking on the download link for a file, I get the "File not in queue" error message. The MIS log shows: + 2022.07.09 13:46:13 HTTP > Connect on slot 1/10 (192.168.1.1) + 2022.07.09 13:46:13 HTTP 1-HostName router.asus.com + 2022.07.09 13:46:13 HTTP 1-Country Unknown (-) + 2022.07.09 13:46:13 HTTP 1-DLREQ: GET /dlreq?12cfe918 HTTP/1.1 + 2022.07.09 13:46:13 HTTP 1-Authenticated user: Zip + 2022.07.09 13:46:13 HTTP 1-List Batch + 2022.07.09 13:46:13 HTTP 1-Request done + 2022.07.09 13:46:14 HTTP > Connect on slot 1/10 (192.168.1.1) + 2022.07.09 13:46:14 HTTP 1-HostName router.asus.com + 2022.07.09 13:46:14 HTTP 1-Country Unknown (-) + 2022.07.09 13:46:15 HTTP > Connect on slot 1/10 (192.168.1.1) + 2022.07.09 13:46:15 HTTP 1-HostName router.asus.com + 2022.07.09 13:46:15 HTTP 1-Country Unknown (-) + 2022.07.09 13:46:15 HTTP 1-DLREQ: GET /dlreq?12cfe918&test.tar HTTP/1.1 + 2022.07.09 13:46:15 HTTP 1-Authenticated user: Zip + 2022.07.09 13:46:15 HTTP 1-Refused: File not in queue The dlreq data file contains: bbs@glimmer:~/mystic/data$ cat 12cfe918.dlreq 1657377963 192.168.1.1 1 1,10240,0,/mnt/bbs/mystic/files/local/L_UPLOADS/test.tar 1,181,0,/mnt/bbs/mystic/files/local/L_UPLOADS/test.tgz bbs@glimmer:~/mystic/data$ It looks OK I think. Could it possibly be some kind of mismatch between the directory separators (/ on Linux instead of \ on Windows) or some path length limitation that causes this? I'll let you know if I would stumble across anything additional, but I think the new version is a big step forward. Thanks, and, as always, many thanks in advance! Best regards Bj”rn --- Mystic BBS v1.12 A48 2022/07/07 (Linux/64) * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137) .