-* Error reporting sucks, and when a domain or user doesn't exist we
- should be able to say so. The describe_domain/user functions
- should also work better. For plugins that don't implement domains,
- we can return a (count of?) list of users, or fall back to the
- user deletion descriptions.
+* 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.
-* Implement "mv".
+ 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?
- Design:
+* Add OpenDKIM support.
- This should only work from a domain that exists in postfixadmin to a
- domain that already exists in postfixadmin. If the target domain
- does not exist, we should error out as soon as possible.
+* Write a man page.
- Once we're sure that the target domain does exist, we can hand off
- the "mv" operation to the plugins. Some of them might have nothing
- to do -- that's fine.
+* Update the README.
-* Add convenience methods (e.g. user_exists, domain_exists) that we
- can use in the tests to check results.
+* Make a release.
-* Potentially add OpenDKIM support.
+* Should we wrap all of the connection.close() calls in "ensure"?
+
+* Test deletion of a user "bar" who lies in the middle of a
+ goto="foo,bar,baz" alias.
+
+* Make sure removing a domain updates the aliases table correctly.
+
+* Factor out all of the msg-building in e.g. MvRunner.
+
+* Implement moving of domains.