blob: 2d57048dec4d90ba0d998720145b959eb4529d78 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
* Email::Valid does not accept UTF-8 emails adresses (e.g., test@ƛ.net).
LDAP doesn't allow UTF-8 in the DNs anyway, so maybe convert the
domains/emails to Punycode internally?
* What to do when a user wants to add a domain? Is it worth it to send a confirmation e-mail?
* Better check for existing lists (commands).
- When adding a new alias/mailbox 'test', check for existing alias/mailbox 'test', and list 'test'.
- When adding a new alias/mailbox 'test-request', check for existing alias/mailbox 'test-request', list 'test-request' *and* list 'test'. (The same for other list commands.)
- When adding a new list 'test', check for existing alias/mailbox/list 'test', 'test-request',...
- When adding a new list 'test-request', check for existing alias/mailbox/list 'test-request', 'test-request-request',... *and* list 'test'. (The same for other list commands.)
* Check for cycles when creating new aliases?
(It is impossible since the authenticated user may not have full read access on the graph)
Hopefully Postfix checks it and warns the postmaster.
* Write a script to check every runmode against the W3 validator.
* Use FastCGI. References
- http://search.cpan.org/~naoya/CGI-Application-FastCGI-0.02/lib/CGI/Application/FastCGI.pm
- http://stackoverflow.com/questions/11771564/nginx-fastcgi-configuration-for-cgiapplication-app
* Use HTML::Template::Pro. Not sure it's really worth it, though.
|
