X-Git-Url: http://gitweb.michael.orlitzky.com/?p=mailshears.git;a=blobdiff_plain;f=doc%2FTODO;h=d2d762cc3fd9e650c4f569ffea532e996221cdf9;hp=8d773983a2cb247cdcb328638538a53fc9a23de5;hb=08e0795d01329de098fb23d85d459d32e54f3e36;hpb=e7fa62fc599b7583102fe48fbaad3db4f911a6da;ds=sidebyside

diff --git a/doc/TODO b/doc/TODO
index 8d77398..d2d762c 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,21 +1,22 @@
-* When we delete a domain, do we delete all of the accounts, too? Or
-  just the domain? We can do this in either the runner or the plugin.
+* There is essentially no error handling. We report errors, but we
+  don't fail when we see one. The main reason for this is that we
+  don't know when each plugin will be run. If the first plugin
+  encounters an error, we could quit right there. But what if the
+  third one fails after the first two succeed? We would need some kind
+  of rollback mechanism.
 
-  At the moment, it's mixed. The RmRunner does it manually, but e.g.
-  the PostfixadminDbRm plugin also deletes the mailboxes when the
-  domain is deleted.
+  For "mv", a rollback is conceivable. But with "rm", there's no going
+  back. Maybe relying on the user to interpret the output and go
+  fix stuff himself is the best we can do?
 
-  One doesn't seem any better than the other, but maybe if you
-  consider that some of the plugins have no-ops for
-  delete_domain(). Those could be made to actually do something
-  (i.e. delete all matching account names). Then we could get rid of
-  the get_domain_accounts() or-whatever-it's-called methods.
+* Add OpenDKIM support.
 
-* PostfixadminDb can be made a plugin -- prune just won't work without
-  it.
+* Rename the "dovecot" plugin to "filesystem".
 
-* Error reporting sucks, and when a domain or account doesn't exist we
-  should be able to say so. The describe_domain/account functions
-  should also work better. Depending on what we do in the first bullet
-  point, they could either return a list of names, or
-  NotImplementedError.
+* Implement moving of domains.
+
+* The AgenDAV "user exists" test is wonky, because there's no real
+  users in AgenDAV. Right now we check the "username" column in the
+  "prefs" table, but all of the shares (and principals?) have URLs
+  instead of usernames. We don't parse the URLs, and instead rely
+  on doing find/replace of substrings in e.g. AgendavMv.