W...W
     W.W.W
     .W.W.

     WaterGate
     Message processor for FidoNet & Internet/Usenet
     Future plans

     Copyright (c) 1993-1997 Waterline Software Development
                             All Rights Reserved

6 July 1997,

This document contains some of the future plans for WaterGate.
I have compiled it for few reasons: to show people the potential
of WaterGate in the near future, to start discussions, to allow
people to tell me what they want fixed first and to stop people
from asking me for the todo/wish list, which contains over 600
items and happens to be in Dutch anyway ;)

Future plans for WaterGate development, in no specific order.


Mailing List
------------

Allow custom headers added to distributed messages
Make list of connected users publicly available (option)
Forward subscribe requests to administrator (private lists)
Rewrite the message as if it was sent by the server (option)
Put multiple recipient addresses on rmail line (system option)
Use REPLY kludge in reply


AreaFix/Newsfix
---------------

Send log to admin
Build in %rescan
Build in %unlinked
Use REPLY kludge in reply
Archive processed request
Pre-check requests by admin


Dupe checking
-------------

Redo the whole thing
Separate Fido and Usenet databases
Track dupes on a per-area basis
Proper logging, especially Usenet dupes


WtrConf
-------

Quick setup
Improve keys lines
Update / extend import formats
TXT editor
Rename/move msgbase when changing path/basename
Config check for common errors


WtrStat
-------

Forms with tokens instead of limited command line options
Command line args to filter users, days, etc.
Binary history database


Other items
-----------

Multi-part MIME messages
Internal handling of multiple recipients.
To, Cc and Bcc handling.
File routing
Add zone gating
Report newly created newsgroups to admin
More customized requests through .txt files
Allow file tokens in .txt files
Check / fix statistics reporting
Accounting
Copy headers per user / group / areas
Carbon copy / Blind copy
Protect the gateway from the e-mail side
Adding posting ability to WtrUtil to post in any area
Separate netmail area for file attaches
Move sent netmail to history area (wtrutil)
signature@system domain to send new sig to
Limit known users using route.tdb and bounce for the rest
Improved percentage-hack support ramon%wsd@wline.se
Support control messages
Allow packets from system AKA without having to create a user
Extended file server robot (multi-part reply, auto encoding, etc.)
Scan Bad
Max archive length
Post newly created areas in an echo
Auto-connect some users to newly created areas
Decode files for users
Properly calculate split parts when extracting file


Notice, this list is far from complete. It is a comprehensive list
of most that needs to be done. My personal todo/wish list is a lot
more clear, contains loads of details on each item, dates, etc.
So don't worry if your item(s) are not in this list.

Ramon

ramon@wsd.wline.se
ramon.winkel@ex1.ecs.ericsson.se