* Convert Alias/Forward code to use valias functions
* Sort Aliases/Forwards


Heather L Sherman <heather@idealab.com>

1) tracking between email accounts and forwards is broken:

- create an email account "timothy.chin"
- create an alias "tim"
- wait an imaginary year until Tim quits the company :-)
- create a forward "timothy.chin" to point to "t_chin@yahoo.com"

Problem -- .qmail-tim still points to the explicit maildir timothy.chin
(and mail is delivered accordingly) but displaying all aliases/forwards
blithely shows:

tim -> timothy.chin
timothy.chin -> t_chin@yahoo.com

Misleading and resulting in a major violation of user expectations!

This problem occurs even you if you use the "delete account/set forward for
deleted account option" instead of just ignoring the existing account and
creating a conflicting foward.    Note that using the delete option to
create a forward causes a .qmail-user file to be created which is missing a
final \n.

This could all be avoided if .qmail-user files for aliases were created
Just Like .qmail-user files for forwards

Now for the potential confusing areas:

2) issues with mailing list management

Question I got from one tester:
    "is the 'owner' of a list the moderator?"

(my postmasters don't know what owner means on the "create mailing list
page.  Is there a formal "owner" concept in ezmlm?  a little more text here
to clarify would be good).

The interface to modifying the mailing list is better than the old version,
but still a bit clunky.  "show subscribers"  and "show moderators" pages
would be more useful with "add subscribers" and "add moderators" boxes or
buttons on the pages -- in fact, it would less cluttered if the "delete/add
subscriber" and "delete/add moderator" choices _only_ appeared when you did
a "show moderator".  I don't know how useful others find these short cuts
to these functions, however.

3) The difference between an alias and a forward is not clear -- I'm not
even sure that this distinction needs to be made.  The behaviour really
should be the same:   a .qmail file forwarding to "user@domain" should get
created (see bug report 1 above).

4) It's not clear what a "catchall" account is -- and the interface for
creating it is misleading.   The "button" is used here as a radio button,
while all the delete and add buttons actually take you to a new page.  This
is disconcerting to the novice postmaster.

5) For pages which have tables which could conceivably grow large,
navigation should be at the top as well as the bottom (e.g. "add new
forward", "Main menu", etc. along the bottom of the forward/alias accounts
page should also appear along the top).

6) This is probably outside the scope of this tool, but there is no way
I've found to list all possible domains on the server (perhaps even
including the domainname as a pulldown menu on the login page would solve
my craving for context.  If you have any suggestions, I'd appreciate
hearing them.