Well, I honestly don't think anybody wants SWA to be as functional as Outlook as this would probably bring with it an equally cluttered user interface; it usually takes me about 10 minutes to find one of the more obscure options in one of the many preferences dialogs.
However, some of what's requested here can be done.
For setting up Server Based Rules over the web, we offer the web-based Scalix Rules Wizard. This can be used to setup Out of Office notifications and Auto-Forwards and many other types of rules.
After a default Install of Scalix, this is normally available via the
http://my.server.name/Scalix/rw
URL.
It can be integrated into the SWA menu bar by editing the /etc/opt/scalix/webmail/partner.xml config file. You need to change the "rulesWizard" and "rulesWizardURL" properties and restart tomcat.
The next release of Scalix will do that automatically for you by default during the install.
Now to the other questions:
1. Flexible use of From Address
This is currently not possible. Also, it is not typically a wanted feature for an enterprise Email system, as it would allow me to send email on behalf of my CEO or anybody else, therefore it is a security problem. The proper way to do this is to use delegation (which controls who you may send as by ACL permissions), which is currently available through Outlook. A future release of SWA will also allow for delegate access. Currently, IMAP clients are the only supported client type where the end user has full control over his sender address. If that's not wanted as a security enhancement, it can be disabled on the SMTP Relay level (smtpd.conf) with the AUTH_SUCCESS and AUTH_MISMATCH config options.
2. Delegation of Administration by Domains
This is currently not possible in a single Scalix instance with SAC. However, there are two ways to do it anyway. One is to use multiple independent Scalix Instances that run on a single server; each with it's own user management, message store, address book, etc. The other would be to use an LDAP directory for User Management (which will give you fine-grained access permissions to the objects) and then user our omldapsync integration tool and pam-based authentication against the LDAP server to integrate with an Enterprise directory.
Hope this helps,
Florian.