Do you have an upstream proxy? Your system is making many remote calls (using HTTPS) to connect to the ClearCenter site to get to the stage you're at...the software updates then uses YUM (non SSL) to fetch the updates...I wonder if a proxy in front of ClearOS is denying or disrupting downloads.
Yeah, that always_send_delegates=yes parameter has been brought up in the forum before. The problem then becomes your recipients receive "firstname.lastname@example.org sent on behalf of user@ genericdomain.com" in all the message headers they receive from your clients. Roundcube mail is a better app for avoiding this. Not trying to sell it because I prefer Zarafa. I'm just saying.
Or how about the ftp server? Install that app and enable the server and give your users ftp privileges and it should create home directories for them. Then maybe try their Dropbox. I know when it's working a Dropbox subdirectory should be created in their home directory.
For whatever reason, ClearOS is very popular in South Africa and has a large user install base (community and business).
Thinking out loud, perhaps its time to start a thread asking to organize a SA ClearOS user group (SACOSG....sounds military cool!) with the goal of finding an local ISP or tech company that has bandwidth to host an official SA-based mirror. The YUM plugin to locate the closest mirror would automatically pick up this location and safe everyone on bandwidth going out of country.
We can provide documentation and I'm sure ClearFoundation would give some mention to any organization supporting a local mirror. Seems like a win-win for everyone.
Did you add a user account in the webconfig for the dropbox user (i.e. System->Users), while you were logged in as an administrator, such as 'root'? When you add a user in the webconfig, a home directory is created for the user. Once the user is created in the webconfig, you can go into their user account (logged in as an administrator) and give them privileges to the dropbox server. Once this is done they can login to the webconfig with minimal rights.
That repo doesn't exist any more...we made changes to the private repos wrt to packages that need to be tested before going to the masses.
Edit the conf file that has the zarafa_community_testing entry and disable it...
grep zarafa_community_testing /etc/yum.repos.d/*
You need to be running 6.5beta2, but the new way to update packages from private repositories like Zarafa Community is to add a flag supported in the new yum Marketplace Plugin. So, running:
yum clean all
yum --enablebeta upgrade zarafa-community
This will pull updates down for Zarafa 7.0.15.
BTW, this is fixed in an upcoming package release so you won't need to do this manually...Pete just hasn't pushed out the updates to zarafa-community that makes the changes to your /etc/yum.repos.d/ entries.
All went fine for me too except I bumped into the same problem as Tim reported (blank /usr/clearos/sandbox/etc/httpd/conf.d/devel-paths.conf file)...even after 'clearos reload' when checking the sudoers file.
As soon as I added the directives you posted in a previous post, everything worked.