39 destinations for a domain, e.g. postmaster@ and abuse@. For most |
39 destinations for a domain, e.g. postmaster@ and abuse@. For most |
40 flexibility, there ought to be a m:n table connecting domains to sets of |
40 flexibility, there ought to be a m:n table connecting domains to sets of |
41 default aliases. These aliases then get treated like normal aliases |
41 default aliases. These aliases then get treated like normal aliases |
42 unless they are overridden by a real alias. |
42 unless they are overridden by a real alias. |
43 |
43 |
|
44 - list{aliases,accounts,relocated,addresses} subcommands [madduck@madduck.net] |
|
45 - I would find it useful if I could query the database for all defined |
|
46 users, aliases, relocated, and addresses (the union of all three). |
|
47 Ideally, the commands would also take % wildcards, so that I can limit |
|
48 the output |
|
49 |
44 - domain and account notes [madduck@madduck.net]: |
50 - domain and account notes [madduck@madduck.net]: |
45 - I found it useful to keep a free-text "notes" field for accounts and |
51 - I found it useful to keep a free-text "notes" field for accounts and |
46 domains, where the admin can store anything s/he wants. This would |
52 domains, where the admin can store anything s/he wants. This would |
47 simply be a new field in the two tables and the appropriate UI changes. |
53 simply be a new field in the two tables and the appropriate UI changes. |