I've been a Clear Partner since 2002. We use the software as a general small business server, as a filtering firewall for K-12 and also for some home users.
Thanks Yes, I am a bit of a "commit freak" and there's always a lot of cleanup just before a release. Just wait until the translation stuff starts to roll -- that's going to be a commit hurricane!
@ Dylan - hold off on implementing a mail server right now This initial release was really intended for getting some initial design feedback and I would not be surprised if some functionality is not working. The next step is to integrate the suggested changes and start running a live server (eat or own dog foot). We'll then release a beta and we can go from there.
I've never really investigated it, but Zarafa offers a Zarafa-contacts functionality such that users can store contact information in LDAP...is that feasible?
That will have to wait. This should be done in a generic way so that other software packages could take advantage of it. Kolab has the same functionality and I'm sure others do too.
Will Zarafa support a multi-tenancy setup? or are you still going for the single mail domain target for SOHO use
Multi-tenancy won't be supported.
Its also been requested in the past to be able to configure 'zarafaSendAsPrivilege' so that nominated users can send on behalf of someone else. Such that user1@domain.com can actually appear as full.name@domain.com when sending mail. I couldn't spot a better way of achieving except without some clever maps in postfix to change outgoing mail. Is it possible to select the outgoing mail based on the users list of predefined aliases?
I'll have to look into that. Adding to the Zarafa Extension is the first step - tracker #616
for some reason the default /etc/zarafa/server.cfg disables POP3 and IMAP (see disabled_features = imap pop3), not really sure why
This is a bit of a late post, but better late than never. The Samba initialization bug fix was released quite some time ago. If you are still seeing initialization issues, please let us know.
There's also an update the cleans up the LDAP directory and fixes any lingering security IDs (SID) issues from the early 6.2.0 release. This update has been in test mode for over a week and you can install it with:
Sorry for the confusion. The repos were in flux today as we pushed out a kernel update (more on that later). With the VMware instructions from herballizard, this becomes a moot point, but you can now get a clean update and brand new kernel devel packages:
Code:
yum --enablerepo=clearos* clean all
yum upgrade
yum --enablerepo=clearos-dev install kernel-devel
Our previous VMware images from about a year ago had the VM tools included, but they turned out to be problematic on some products. What we should do in the future is add the VMware repos to the VMware images to make it easy to install the tools if desired.
As for registering a system after a re-install, you can chose the "reinstall/upgrade" option in the registration wizard. This is useful for re-downloading paid apps and things like remote configuration backup. You can also delete an old system via the online portal @ secure.clearcenter.com/portal/
I have released an initial version of ClearOS Mobile Demo for Android.
To install:
# yum install app-mobile-demo
Once installed, you can find the demo under System > Developer > Mobile Demo. From that page you can click on Download & Install to get the app from Google play.
Just a few points to reiterate:
- This is a developer demo! Don't expect a full-featured app that provides much of any real world use.
- After you have added a new system to the application, you may have to wait up to 10 minutes before you start to see data synchronizing. This all depends on how many other sync accounts you have (GMail, Facebook, Twitter, Dropbox, etc). This is apparently "normal" behavior.
- The app will install on Android 2.1 and up, but older API versions do not support periodic data sync, this has to be done in some manual way. Periodic sync works from API level 8 (2.2.x FROYO) and up.
- The password you use to authenticate with is never stored on the phone. It is used once to obtain a session cookie. These cookies will expire after 2 hours. You will be notified with a sign-in error when the session expired. I will be updating the Webconfig/CodeIgniter framework to extend sessions time-outs dynamically so this won't be an issue for future real world apps.
That "mail gateway" feature needs to be implemented properly and should really be a separate app. That has been a feature request for quite some time, but it has yet to materialize. I realize that version 5.2 can be configured as a mail gateway, but it's not a proper implementation. Here's why.
A mail gateway needs to have a list of valid e-mail addresses so that it can reject invalid mail addresses right away. Without this information, the target mail system will be creating backscatter. That's not being a good Internet citizen and it will get the mail gateway listed on blacklists too.
In the first mail stack release, the SMTP Server app no longer has the "Mail Forward" configuration option. We have to be good Internet stewards, and making it easy to create backscatter doesn't fit the bill. That "Mail Forward" feature in SMTP should really transform into the Mail Gateway app. This new app would need a way for an administrator to provide a list of valid e-mail addresses. This could be done via:
- an LDAP / Active Directory Connector
- a simple import tool
- manually editing a list in the app web interface
The "Mail Forward" feature will likely still appear in the final version of 6 since its original intention (forwarding outbound mail) is still required. I'm no a fan of enabling backscatter though.
The Samba output looks good. If Samba is okay, then the underlying non-Samba elements would be fine too. So I'm still stumped on the #2 and #3 issues. The Flexshare looping fix will be on the way to the build system today. Many the bandwidth manager extras too (but that will require a couple of weeks of feedback/testing).
When you use the "Reinstall/Upgrade" option in the registration on a older system (5.x or 6 betas), it will default to disabling the Marketplace. You can re-enable the Marketplace via your ClearCenter account:
- Login to the portal @ secure.clearcenter.com/portal/
- Click on "Systems - Marketplace Settings" in the menu
- Select the system that you wish to update
- Click on "Enable" for Marketplace
This is just a safety mechanism for folks managing older installs, notably:
- Partners who are managing client systems sometimes don't want clients messing around with the install.
- Organizations with multiple ClearOS installs in multiple locations. Same issue really - the "super admin" often doesn't want the local administrator to mess around with the ClearOS box.
For the Community Edition, we should probably set the Marketplace default to enabled on an upgrade.
Darren Best wrote: Unless you can see any reason why mixing Greens and Blacks together in the same RAID would cause any issues?
Nope, I don't... other than for read-access, your lowest common denominator will of course be the slower "green" drives. As you mentioned, the bottle neck in your case will always be network I/O, so this should not be an issue for you provided there won't be any other heavy I/O tasks happening internally on the server.
Yes, I am a bit of a "commit freak" and there's always a lot of cleanup just before a release. Just wait until the translation stuff starts to roll -- that's going to be a commit hurricane! 
This initial release was really intended for getting some initial design feedback and I would not be surprised if some functionality is not working. The next step is to integrate the suggested changes and start running a live server (eat or own dog foot). We'll then release a beta and we can go from there.
