Article View: vmsnet.mail.mx
Article #336RE: The case problem
From: Hunter Goatley
Date: Fri, 18 Dec 1992 13:24
Date: Fri, 18 Dec 1992 13:24
47 lines
2672 bytes
2672 bytes
Per Hogstedt <hogstedt@plab.se> writes: > >Matt spoke: >>Definitely a bug in MLF. I forgot to update the FILESERV_CHECK_ACCESS routine >>(in module FILESERV.B32) to handle NOCASE-set mailing list users. Thanks >>for finding it. > >Since the case sensitivity problem has been a bit disturbing, I'd like to know >if there is any chance that this could be corrected before the next release >of MX (3.1d?). I don't know how extensive the update would be, but if there >is anyone out there planning to hack away, I am interested to know and if >possible help. > I've fixed this for the next release of MX. I'm shooting for a mid-to-late-January release of MX v3.1D. It'll feature mostly little fixes to annoying problems like this one. I'm also alpha-testing new FLQ routines that Matt wrote in BLISS (the old routines were written in PL/1). The new FLQ stuff still uses the ISAM queue file, but it now uses subdirectories of FLQ_DIR to store messages to try to alleviate problems with the QUEUE.DIR file getting larger than 128 blocks. The BLISS rewrite was necessary to get MX working on Alpha, which has been partially done. Here's my planned schedule. My wife has got my Christmas break all planned out for me 8-), so I won't be able to work on MX much, if at all, over the next three weeks. Around 1/14/93 (can you believe another year has gone by?), I hope to finish adding bug fixes, maybe a new feature or two, then build an installation kit for beta-testing. Once at least one other person successfully runs V3.1D 8-), I'll release it. Once v3.1D is released, I plan to spend time finishing the port of MX to Alpha. Matt has successfully sent a mail message from MX on an Alpha, but it has *not* been thoroughly tested yet. I hope to have MX v3.1D running (and tested) on Alpha by the end of February. After *that*, it is my intention to replace the ISAM SYSTEM_QUEUE.FLQ_CTL file with a more efficient method. Naturally, the comments above state my *plans*. I'm going to do my best to meet the deadlines I've set, but I make no warranties, guarantees, promises, oaths, etc., that it'll actually happen then. 8-) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET, 502-745-5251
Technical Details
Message-ID:
<0096542D.F9FA7280.9679@WKUVX1.BITNET>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!news.service.uci.edu!unogate!mvb.saic.com!mx-listShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!usc!news.service.uci.edu!unogate!mvb.saic.com!mx-list From: Hunter Goatley <goathunter@WKUVX1.BITNET> Newsgroups: vmsnet.mail.mx Subject: RE: The case problem Message-ID: <0096542D.F9FA7280.9679@WKUVX1.BITNET> Date: Fri, 18 Dec 1992 07:24:54 CST Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway X-Gateway-Source-Info: Mailing List Lines: 47