Looking for the latest version? Download README (9.4 kB)
Home / livecd / collabsuite / 20130121
Name Modified Size Downloads / Week Status
Parent folder
collabsuite-20130121-i386-standard.md5sum 2013-01-23 73 Bytes 0
collabsuite-20130121-i386-standard.iso 2013-01-23 659.6 MB 0
collabsuite-20130121-amd64-standard.md5sum 2013-01-23 74 Bytes 0
collabsuite-20130121-amd64-standard.iso 2013-01-23 636.5 MB 11 weekly downloads
Totals: 4 Items   1.3 GB 1
CollabSuite Overview ---------------------------- The below document will be helpful in giving you an overview of some of the interesting features of CollabSuite: http://sourceforge.net/projects/collabsuite/files/collabsuite-features.odt Interested in trying out CollabSuite? Read on. CollabSuite LiveCD --------------------------- The easiest way to try out CollabSuite is by downloading and installing the LiveCD. You can download the latest livecd from: http://sourceforge.net/projects/collabsuite/files/livecd/collabsuite/ Once you download the latest 32-bit (i386) or 64-bit (amd64) iso, follow the rest of this guide to install and setup CollabSuite. CollabSuite Screencasts ------------------------------- Through out this guide, we will point you to relevant screencasts. All of these screencasts can be accessed on Synovel's YouTube channel at: http://www.youtube.com/user/synovel These are also available for download at: http://sourceforge.net/projects/collabsuite/files/screencasts/ Collabsuite OS Installation ----------------------------------- Related Screencasts: Collabsuite OS Installation - http://www.youtube.com/watch?v=xEX9ucW4jvY 1. Minimum of 1.5 GB and a recommended of 2 GB of RAM is required to run Collabsuite. Also, please keep the below information ready: a. Mail Domain (ex. example.com) b. FQDN (Fully Qualified Domain Name) of the server (ex. mail.example.com) c. Root Password of your choice for the OS d. User "admin" password (Administrator password) of your choice 2. Next either boot the LiveCD or install it to a VM (suggested) Collabsuite Configuration (Default OpenLDAP backend) ------------------------------------------------------------ Related Screencasts: Collabsuite Hostname Check & Configuration - http://www.youtube.com/watch?v=uMYJka5kAX4 1. Edit /etc/hosts and add an entry for your FQDN. If you do not plan to access the server across the network, you can also map it to an IP in the local range. For example, the below entry can be added to /etc/hosts (assuming mail.example.com is your FQDN): mail.example.com 2. Start the webadmin console setup at https://localhost:10000/setup/. You will have to fill the following mandatory information at a minimum: - Basic Information Tab -> Primary Domain (this is mail domain) - Nodes Tab -> Fully Qualified domain name (this is FQDN of the server) - Nodes Tab -> Privileged Password (this is Root password) - Admin Console Tab -> Admnistrator Password (this is Administrator Password) 3. Click on Verify. If there are no errors, you can then click on "Start Install" and the collabsuite will be setup. 4. After installation is completed, and in case you don't see any errors, restart apache2 and scs-server # sudo /etc/init.d/apache2 restart # sudo /etc/init.d/scs-server restart 5. Admin console is accessible at https://localhost:10000/. You can use username "admin" and administrator password that you had given during setup to access them. Collabsuite Configuration (Active Directory Backend) ------------------------------------------------------------- Related Screencasts: Active Directory CopSSH Installation - http://www.youtube.com/watch?v=LPz0EZS7blk Collabsuite Hostname Check & Configuration (Active Directory Backend) - http://www.youtube.com/watch?v=rvbGn8u-CgM Active Directory Deleting Self-Signed Certificate - http://www.youtube.com/watch?v=XMrWYOvt2vk It is recommended that you do not run this setup directly on a live production Windows Server. Instead, first do a test setup, and then only install in production. 1. For illustrative purposes, we assume the following: - Mail domain - example.com - Mail server FQDN - mail.example.com - Active Directory FQDN - ads.example.local - Active Directory Domain - example.local 2. For Windows 2003, you will have to perform an additional step of raising the domain and forest functional level to Windows 2003 (instructions are available at http://technet.microsoft.com/en-us/library/cc776703%28WS.10%29.aspx and http://technet.microsoft.com/en-us/library/cc780862%28WS.10%29.aspx). 3. Install Support Tools (by running \support\tools\suptools.msi on first cd or by downloading it from Internet). This is not necessary for Windows 2008 (R2). 4. Download CopSSH from http://sourceforge.net/projects/collabsuite/files/misc/Copssh_4.1.0_Installer.zip and install it. 5. Start the CopSSH Control Panel and activate the user Administrator (or any other user with administrative privileges). While activating the user Administrator, you have have to select the machine hostname as the "Domain" value. For advanced security, private key could be used for Administrator SSH authentication (not covered in this guide). 6. Open Incoming SSH Port 22 in Windows Sever Firewall. 7. Test if SSH access is enabled for Administrator by running the below command from mail server (you should be able to successfully login): # ssh Administrator@ads.example.local 8. In your mail server, edit /etc/hosts and add an entry for your FQDN and active directory server. 9. Now visit the Collabsuite Setup Admin Console at https://mail.example.com:10000/setup/ and enter the following values. - Basic Information: - Primary Domain - example.com (this is the mail domain) - Realm - EXAMPLE.LOCAL (this is the Active Directory Domain) - Use Windows AD Server - Checked - Realm Domains - .example.com (or mail.example.com) - Nodes - Primary Server Information - Fully Qualified Domain - mail.example.com - Privileged Password - Enter password for root - Nodes - Active Directory - Fully Qualified Domain - ads.example.local - Privileged Password - Enter password of Administrator User - Admin Console - Administrator Password - Enter password which you would like to be set for "admin" user 10. After entering the above details, click on Verify. After a few checks, the Install button will be enabled. Click on Install to complete the installation. 11. It is possible that sometimes the installation might fail. In this case, you will first have to delete the self-signed certificate for ads.example.local (which gets installed automatically in Windows Server) by following the below steps. - Go to Start -> Run... and execute "mmc" - Go to File -> Add/Remove Snap-in... - From the list of availabe snap-ins, select Certificates -> Add -> Computer account -> Local computer. Click on OK. - Now in the left pane, go to Certificates -> Personal -> Certificates and delete the certificate for ads.example.local. - Similarly, go to Certificates -> Trusted Root Certification Authorities -> Certificates and delete the certificate for ads.example.local. - Now revisit the Collabsuite Setup Admin Console, and re-rerun the setup (use the same values which you used last time). Configuring Collabsuite Webclient ----------------------------------------- Related Screencasts: Collabsuite Webclient - http://www.youtube.com/watch?v=dV8tPK5l5F4 Webmail is accessible at https://localhost/. You can use username "admin" and administrator password that you had given during setup to access them. It should work out-of-the box for most of the scenarios. You can change some global options in config/scs-webclient.conf. Configuring Collabsuite Archiver ---------------------------------------- Related Screencasts: Collabsuite Archiver - http://www.youtube.com/watch?v=8RwFIQY-IK0 SCS Archiver is accessible at https://localhost/scs-archiver/. You can also access this by logging into the webadmin console and clicking on "Mail and IM" in "Archival & Statistics". The username is "admin" and default password is "admin". Once you login, follow the below steps to set it up. 1. Go to Configuration -> Volumes - Enter a new "Email Encryption Password" - Click on 'Save' to save the changes 2. Go to Configuration -> Login - Enter a new "Master Admin Login Password" - Click on 'Save' to save the changes - Logout and login with the new password 3. Go to Configuration -> Volumes - Add a new volume with index "/data/mailarchiva/index/index0" and store "/data/mailarchiva/store/store0". It is assumed that /data/mailarchiva/ is where you have mounted the partition to be used for archiving mails. It is recommended but not necessary to create a separate partition for archiving mails. - Click on 'Save' to save the changes 4. In webadmin console (https://localhost:10000/), go to "Email and Anti-Spam", double-click on "SMTP Daemon" (which will bring up the daemon edit interface), go to tab "Domain and Networks", set "inet:" as a SMTPD Milter, and click on Save. Archiving of mails will now start. 5. For accessing chat archives, first copy the ejabberd database password by going to "IM and Calendaring" section in webadmin console, double-clcking on "XMPP Daemon" and clicking on "(Show Password)" in Advanced Details. You will have to set this password in /opt/scs-archiver/server/webapps/mailarchiva/WEB-INF/conf/chatsearch.conf. Chat archives should now be accessible. 6. Send a test mail. You should be able to retrieve this mail using the "Email Search" interface. Similary send a test chat message and you should be able to retrieve it using the "Chat Search" interface.
Source: README, updated 2013-01-29

Thanks for helping keep SourceForge clean.

Screenshot instructions:
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks