List of Known Bugs in WaterGate 0.93.p7
---------------------------------------

The following bugs are known to exist in WaterGate 0.93.p7.
Work-arounds are given where possible.

* The "From AKA" used in Areafix forward messages to the uplink can
  contain the wrong AKA. WaterGate tries to find the system AKA
  closest to the destination AKA and uses that one, instead of the
  default AKA from the Group Definition for the group selected in the
  Areafix Forward definition.

  Work around:
  If WaterGate takes the wrong AKA, try putting the AKA you want to
  use high up in the list of system AKAs so WaterGate will use that
  one.
  Alternative is it add a domain to both the uplink address and the
  system AKA that are the same. WaterGate will value the 5D match
  over the 4D match.

* WtrGate cannot handle a Squish message base with an index file over
  64Kbytes in size. You will get an error report in the log when the
  size of the Squish index is too large. The message that otherwise
  would be imported will be lost.

  Work around:
  Try to keep the size of the message base down so it never reaches
  this size. Use automatic purging by limit and/or days.

* If a NUL is present in the body of a mail or news article and gated
  to netmail or echomail then the NUL is not replaced in all
  situations and can show in the body of for example a PKT or *.MSG,
  which is fatal for that format since it terminates the body there.

* The last character on each line is not translated according to the
  character set translation. The problem only affects lines with a
  'special' character at the last position of a line.
