W...W W.W.W .W.W. WaterGate Message processor for FidoNet & Internet/Usenet Known Problems Copyright (c) 1993-1997 Waterline Software Development All Rights Reserved 6 July 1997, During testing we found a number of bugs that could not be fixed before the release date and have to wait until another version. This document lists those problems for you, the features affected and the extent of the problem. This will allow you to either work around it or avoid a certain feature. Some things are not possible with WaterGate and explicitly mentioned in the manual. Those are not in this listing. -------------------------------------------------------------------- 1 Problem: SEEN-BY and PATH lines in echomail are considered text when there is no tear-line present. A new PATH and SEEN-BY kludge will be added below the Origin line. Info: An echomail message without a tear-line is not valid but does occur. Affected: All echomail without tear-line Solution: None. -------------------------------------------------------------------- 2 Problem: Path lines without backslash can give problems and directory might not be created. Info: Original check for backslash was lost when the File Manager was added. Affected: All fields where you can enter a path. Solution: Use the File Manager to pick a path or make sure you type the backslash at the end of a path. -------------------------------------------------------------------- 3 Problem: AreaFix commands %MOVENEW and %DELNEW are not updated to work with the new groups. Info: They try to manipulate group Z (now F) instead of Z1. Affected: %MOVENEW and %DELNEW, only available for users with "AreaFix Special" or "Newsfix Special" set to YES. Solution: None. -------------------------------------------------------------------- 4 Problem: The combination of an e-mail area and the local list server can give problems with subscriptions on the RFC side and the gateway being closed during distribution. Info: When using an e-mail area you have to write an e-mail address or the message will not be scanned out, so you can only address listserv@your.domain. Your own e-mail adres is then a link to the FTN side (either via a MAP-UUCP statement). If you subscribe that way, then the distributions from that list never make it to you because RFC to FTN gating is not possible during distribution. Affected: Subscribing to a local list server from within an e-mail area. Solution: SysOp must change subscription manually. Make the RFC address post-only and add a FTN user with receive-only (of full) access to receive the distributions, but those won't end up in the e-mail area unless you use a BBS-AREA that points to the e-mail area. -------------------------------------------------------------------- 5 Problem: AreaFix tries to disconnect last subscriber from locally originated area. This is a subscriber, not the uplink! Info: It thinks the last subscriber is the uplink. It then can't find this user in the AreaFix Forwarding definitions when it tries to write the forwarding netmails. Affected: Locally originated areas. Solution: Set "Allow Passive" for this Area Definition to NO. -------------------------------------------------------------------- 6 Problem: JAM purge doesn't update the last read information. Affected: JAM bases. Last-read pointers of your users on the BBS or local editor can point wrong. Solution: Do not purge JAM areas. -------------------------------------------------------------------- 7 Problem: BlueWave shows lots of empty lines in messages downloaded from RA. Info: BlueWave or RA cannot handle kludge lines longer then 80 characters. This can happen when you use the Copy Headers feature to copy RFC header lines into FTN messages. Affected: BlueWave. Solution: Disable Copy Headers to Kludges. Copy to Text instead or not at all. -------------------------------------------------------------------- 8 Problem: Selecting ".." in the File Manager in the OS/2 version causes an endless loop. Info: The ".." directory shows up in the root in the File Manager of the OS/2 version. Affected: OS/2 version, File Manager, selecting ".." directory in the root. Solution: Do not select ".." in the root. -------------------------------------------------------------------- 9 Problem: Lots of error 4, "out of file handles" in the OS/2 version. Info: WaterGate tries to open more files as there are handles available. The DOS versions can reports this error as well with the same reason. Affected: OS/2 version. Solution: Set "Max open handles" to 1. WtrConf, System Configuration, Global settings, Advance settings, "Max. files open" = 1. If the problem remains, then please report. Increases FILES= in CONFIG.SYS is not the solution. -------------------------------------------------------------------- 10 Problem: Exceptions are not handled in the OS/2 version. Info: Ctrl+Break or Ctrl+C aborts the program in a hard way. Affected: OS/2 version. Solution: Do not press Ctrl+Break or Ctrl+C. -------------------------------------------------------------------- 11 Problem: Headers containing 8 bit data are not quoted-printable encoded. Info: This was not added yet. The old 8-bit to 7-bit mapping table from 0.92 is still used internally to remove the 8-bit data. Affects: Header lines containing 8 bit data. Solution: None. -------------------------------------------------------------------- 12 Problem: The OS/2 version cannot handle long paths too well. Affects: OS/2 version. Solution: Use 8.3 paths for the moment. -------------------------------------------------------------------- Team WaterGate