1 - Aliases |
|
2 - avoid looping aliases |
|
3 |
|
4 - Domain |
|
5 - optional limits for number of: |
|
6 + accounts |
|
7 + aliases |
|
8 + destinations/alias |
|
9 + alias domains |
|
10 |
|
11 Database: |
|
12 public.users.digestmd5: add "character varying(48)" |
|
13 Outlook will love it. (`doveadm pw -s DIGEST-MD5.hex -p 1 -u 0`) |
|
14 |
|
15 - Non-root usage [madduck@madduck.net]: |
|
16 - Provide /usr/share/vmm/vmm-{mkdirs,rmdirs,du} setuid wrappers that do |
|
17 precisely what they have to and no more. The should probably even call |
|
18 /usr/share/vmm/vmm-wrapper-helper as unprivileged user to parse the |
|
19 arguments, match them with the database and obtain the actual data to |
|
20 process, e.g. email@add.ress → home directory mapping from the DB, or |
|
21 obtaining the set of precreatable maildirs from the config. |
|
22 |
|
23 - configset and configure need root, it is questionable whether these |
|
24 can/should be wrapped, as they will be disabled anyway for Debian, and |
|
25 they are root-like activities (unlike day-to-day postmaster work). |
|
26 |
|
27 - Pascal suggested to use hooks: |
|
28 07 23:36 <Faxe> zwei config settings handle_dir in domain und account |
|
29 07 23:37 <Faxe> und dann post-{domain,user}add scripte, die den wrapper aufrufen |
|
30 |
|
31 - relay_domains management [madduck@madduck.net]: |
|
32 - should be in a separate table |
|
33 |
|
34 - default aliases [madduck@madduck.net] |
|
35 - it should be possible to define a set of default aliases and their |
|
36 destinations for a domain, e.g. postmaster@ and abuse@. For most |
|
37 flexibility, there ought to be a m:n table connecting domains to sets of |
|
38 default aliases. These aliases then get treated like normal aliases |
|
39 unless they are overridden by a real alias. |
|