I'd suggest trying to telnet to port 12340 on the external interface on the ClearOS box itself. That will tell you whether Apache is listening on the external interface on that port. If you can connect, start looking more closely at your port forwards etc...but if it fails, start looking at your appache config.
Name of the game is narrowing down the problem to the smallest possible set of circumstances.
are different users who should not have access to each other's mail.
This isn't the case for you.
As for sending as aliases, when logged into Zarafa Webmail as a user, click on "Settings" at the bottom right and click on the "Compose Email" Tab. From that page, you'll see a section 'From Email Addresses' where a user can add their alternate domains, so that when sending, they can change their "From" profile.
I still would like to know how to disable or block root account for security reasons.. if thats possible.
That might be a good feature to add someday. In the mean time, if you look at/hack the file /usr/clearos/apps/base/libraries/Authorization.php, you'll see a line:
if ($username === 'root')
Change it to...you guessed it:
if ($username === 'root')
I've never seen an update on this class for a while, so your hack should be safe for a while...however, know that any update that comes down from an update that changes this file would wipe out your edits. Might be worth chattr the file to make it ReadOnly.
Welcome back...fairly modest list there..here are the caveats:
RE: 2 - Virtual Domains. Depends on your definition. Have a read here.
RE: 4 - Full Outlook Support. Only the Professional Edition's Zarafa Small Business Version provides support for MAPI so Outlook can talk natively to the server. The Zarafa Community Edition that Tim Burgess provides does not have this functionality...although you can manually hack it in for up to 3 users.
RE: 6 - AD Folder Like Security. On our roadmap for version 7 to implement file ACL. For now, Flexshare file shares are limited to owner/group RW (eg. Unix file permissions only).
I just PM'd you...let's take this out of the public and try and resolve quickly, then post our finding back here for everyone. Of course, we're very interested in making sure there's no roadblocks to any part of the wizard. Maybe you've encountered something I haven't seen before...
And XXXX is your system's unique hostkey, obtained by running:
cat /etc/suvad.conf |grep hostkey
If that works, your system will be registered on the ClearCenter side...to make your box aware of it, run:
But really, this is just to find out if the curl command works from CLI and it points to something in the ClearOS framework, of it's something to do with the webservice call which might show up better using curl directly.
Those rules will work for non-transparent mode too.
As for flipping the mode around (eg. force 4 IP's through proxy and allow all others to go through)...you're on your own...that would take a bit of hacking and you're basically not using Webconfig anymore.
I suppose you could just put the 4 PC's in a 'proxy' block/range 192.168.1.100-192.168.1.10. Then set your bypass rules as above to be any computer on 192.168.1.11-254.
If you wanted, you could add your subdomain as a full DNS service here. However, that costs $20/yr. I'd recommend for another $5 just getting your own vanity domain and tying it in to the dynamic DNS service. You can do that here.