I'll gladly implement any suggestions that I receive... as long as people are actually using the program, I'm willing to keep improving it. Among the features I want to include in the program/s are the following:

Feature	Priority
Properly rendered file gadgets in the preferences program.
An ARexx action type, which would just run the chosen ARexx script with Sys:RexxC/Rx.
Storage of MailWatch filesize in a variable in ENVARC:/ENV:, so the program can determine what change has happened between activations.
An Installer script.
A 'window.mwdf' GUI definition module, which will display gadgets or graphical fields in a window instead of AppIcons.
Some way of organizing separate preferences for each new loadable module; maybe just a library call to the module itself, to indicate that the user wanted to set the preferences. This could either run code inside the module itself, or possibly an external program.
At some point soon I'll make the API for the external modules publically available. This will enable anyone (if they so desire) to quickly and easily write a GUI definition module for MailWatch.
A help field in the preferences program (optional) - give a short explanation of each gadget as the pointer moves over it.
I may include support for playing alert sounds via Datatypes (for OS 3.x users only). The program would still work on OS 2.x systems, just without the sounds.