https://wiki.koozali.org/api.php?action=feedcontributions&user=Pfloor&feedformat=atom
SME Server - User contributions [en]
2024-03-29T11:33:46Z
User contributions
MediaWiki 1.35.5
https://wiki.koozali.org/index.php?title=GeoIP&diff=31756
GeoIP
2016-07-28T19:04:17Z
<p>Pfloor: /* Abbreviated Country Code List */</p>
<hr />
<div>{{Languages}}<br />
=== Maintainer ===<br />
[mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br /><br />
=== Version ===<br />
{{ #smeversion: smeserver-geoip }}<br />
<br />
===Description===<br />
<br />
The GeoIP plugin lets us know where our mail server is receiving mail from. If we're receiving too much spam from a particular location, this will help track it down. We can then use that info to reject connections from that place taking the load off our server.<br />
<br />
===Installation===<br />
<br />
yum install smeserver-geoip --enablerepo=smecontribs<br />
then <br />
signal-event geoip-update<br />
<br />
or if you prefer to reboot your server<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
each time you will do <br />
signal-event geoip-update<br />
you will download the geoip database, otherwise a cron script will do it each month.<br />
<br />
==Testing==<br />
<br />
Now that the package and database are installed, we can test it (refer to Country Code list at end of page as required). <br />
<br />
geoiplookup 216.17.211.37 <br />
<br />
It should return: <br />
<br />
GeoIP Country Edition: US, United States<br />
<br />
It gives us the country code (US) and the long name (United States). Let's test it again with a domain name. <br />
<br />
geoiplookup contribs.org <br />
<br />
Same result. So we know it works with ip addresses or domain names. Let's test it again around the world. <br />
<br />
geoiplookup gormand.com.au <br />
<br />
It should return: <br />
<br />
GeoIP Country Edition: AU, Australia <br />
<br />
One last time:<br />
<br />
geoiplookup swerts-knudsen.dk <br />
<br />
It should return: <br />
<br />
GeoIP Country Edition: DK, Denmark<br />
<br />
==Usage==<br />
===Tracking e-mail===<br />
GEOIP plugin should now do its work. Check the qpsmtpd logs and you'll see the countries from where mail is sent. <br />
<br />
cat /var/log/qpsmtpd/current <br />
<br />
We'll use a simple shell script to do the work then we'll run it. <br />
<br />
First, create the the script.<br />
<br />
vi geoipstats.sh<br />
<br />
Insert the following: Code:<br />
<br />
#!/bin/sh <br />
# Read the qpsmtpd log file.<br />
# Read all of the countries and count them. <br />
cat /var/log/qpsmtpd/* | \<br />
grep 'GeoIP Country:' | \<br />
sed -e 's/^.*\(..\)$/\1/' | \<br />
sort | uniq -c | sort -n <br />
<br />
Now run the script. It will show the number of messages sent by country code. <br />
<br />
sh geoipstats.sh<br />
<br />
See where your mail is coming from. Now ask the question, "why am I receiving thousands of email from RU -Russia? I don't even know anyone there." Good point. In addition, your server has to process all that mail, taking resources away from the server. In the next section we'll block the countries that we consider bad.<br />
<br />
===Blocking email===<br />
Add the values to the SME CADNHO db. In our case, Russia and Poland seem to causing issues. You can type in any country codes you wish.<br />
<br />
config setprop qpsmtpd BadCountries RU,PL<br />
<br />
Signal the email-update event.<br />
<br />
signal-event email-update<br />
<br />
No more mail from domains ending on .ru or .pl. The beauty of this is that the SME Server lookups happen locally on the local database rather than looking up the IP address via dns. This results in very fast responses. In addition, the plugin happens before most other plugins. This means the mail is dropped before the SME Server even has to check to see if it's on a blacklist or if it's spam.<br />
<br />
===Abbreviated Country Code List===<br />
<br />
A1 Anonymous Proxy<br />
A2 Satellite Provider<br />
AC Ascension Island<br />
AD Andorra<br />
AE United Arab Emirates<br />
AERO members of the air-transport industry<br />
AF Afghanistan<br />
AG Antigua and Barbuda<br />
AI Anguilla<br />
AL Albania<br />
AM Armenia<br />
AN Netherlands Antilles (being phased out)<br />
AO Angola<br />
AQ Antarctica<br />
AP Asia/Pacific<br />
AR Argentina<br />
AS American Samoa<br />
ASIA Restricted to the Pan-Asia and Asia Pacific community<br />
AT Austria<br />
AU Australia<br />
AW Aruba<br />
AX Aland Islands<br />
AZ Azerbaijan<br />
BA Bosnia and Herzegovina<br />
BB Barbados<br />
BD Bangladesh<br />
BE Belgium<br />
BF Burkina Faso<br />
BG Bulgaria<br />
BH Bahrain<br />
BI Burundi<br />
BIZ Restricted for Business<br />
BJ Benin<br />
BL Saint Barthelemy<br />
BM Bermuda<br />
BN Brunei Darussalam<br />
BO Bolivia<br />
BQ Bonaire, Sint Eustatius and Saba<br />
BR Brazil<br />
BS Bahamas<br />
BT Bhutan<br />
BV Bouvet Island<br />
BW Botswana<br />
BY Belarus<br />
BZ Belize<br />
CA Canada<br />
CC Cocos (Keeling) Islands<br />
CD Congo, The Democratic Republic of the<br />
CF Central African Republic<br />
CG Congo<br />
CH Switzerland<br />
CI Cote d'Ivoire<br />
CK Cook Islands<br />
CL Chile<br />
CM Cameroon<br />
CN China<br />
CO Colombia<br />
COM Generic top-level domain<br />
COOP cooperative associations<br />
CR Costa Rica<br />
CU Cuba<br />
CV Cape Verde<br />
CW Curaçao<br />
CX Christmas Island<br />
CY Cyprus<br />
CZ Czech Republic<br />
DE Germany<br />
DJ Djibouti<br />
DK Denmark<br />
DM Dominica<br />
DO Dominican Republic<br />
DZ Algeria<br />
EC Ecuador<br />
EDU Educational Institutions<br />
EE Estonia<br />
EG Egypt<br />
EH Western Sahara<br />
ER Eritrea<br />
ES Spain<br />
ET Ethiopia<br />
EU European Union<br />
FI Finland<br />
FJ Fiji<br />
FK Falkland Islands (Malvinas)<br />
FM Micronesia, Federated States of<br />
FO Faroe Islands<br />
FR France<br />
GA Gabon<br />
GB United Kingdom<br />
GD Grenada<br />
GE Georgia<br />
GF French Guiana<br />
GG Guernsey<br />
GH Ghana<br />
GI Gibraltar<br />
GL Greenland<br />
GM Gambia<br />
GN Guinea<br />
GOV United States Government<br />
GP Guadeloupe<br />
GQ Equatorial Guinea<br />
GR Greece<br />
GS South Georgia and the South Sandwich Islands<br />
GT Guatemala<br />
GU Guam<br />
GW Guinea-Bissau<br />
GY Guyana<br />
HK Hong Kong<br />
HM Heard Island and McDonald Islands<br />
HN Honduras<br />
HR Croatia<br />
HT Haiti<br />
HU Hungary<br />
ID Indonesia<br />
IE Ireland<br />
IL Israel<br />
IM Isle of Man<br />
IN India<br />
INFO Generic top-level domain<br />
IO British Indian Ocean Territory<br />
IQ Iraq<br />
IR Iran, Islamic Republic of<br />
IS Iceland<br />
IT Italy<br />
JE Jersey<br />
JM Jamaica<br />
JO Jordan<br />
JOBS Reserved to serve needs of the international human resource management community<br />
JP Japan<br />
KE Kenya<br />
KG Kyrgyzstan<br />
KH Cambodia<br />
KI Kiribati<br />
KM Comoros<br />
KN Saint Kitts and Nevis<br />
KP Korea, Democratic People's Republic of<br />
KR Korea, Republic of<br />
KW Kuwait<br />
KY Cayman Islands<br />
KZ Kazakhstan<br />
LA Lao People's Democratic Republic<br />
LB Lebanon<br />
LC Saint Lucia<br />
LI Liechtenstein<br />
LK Sri Lanka<br />
LR Liberia<br />
LS Lesotho<br />
LT Lithuania<br />
LU Luxembourg<br />
LV Latvia<br />
LY Libyan Arab Jamahiriya<br />
MA Morocco<br />
MC Monaco<br />
MD Moldova, Republic of<br />
ME Montenegro<br />
MF Saint Martin (French part)<br />
MG Madagascar<br />
MH Marshall Islands<br />
MIL United States Military<br />
MK Macedonia, The Former Yugoslav Republic of<br />
ML Mali<br />
MM Myanmar<br />
MN Mongolia<br />
MO Macao<br />
MOBI consumers and providers of mobile products and services<br />
MP Northern Mariana Islands<br />
MQ Martinique<br />
MR Mauritania<br />
MS Montserrat<br />
MT Malta<br />
MU Mauritius<br />
MUSEUM museums<br />
MV Maldives<br />
MW Malawi<br />
MX Mexico<br />
MY Malaysia<br />
MZ Mozambique<br />
NA Namibia<br />
NAME individuals<br />
NC New Caledonia<br />
NE Niger<br />
NET Generic top-level domain<br />
NF Norfolk Island<br />
NG Nigeria<br />
NI Nicaragua<br />
NL Netherlands<br />
NO Norway<br />
NP Nepal<br />
NR Nauru<br />
NU Niue<br />
NZ New Zealand<br />
OM Oman<br />
ORG Generic top-level domain<br />
PA Panama<br />
PE Peru<br />
PF French Polynesia<br />
PG Papua New Guinea<br />
PH Philippines<br />
PK Pakistan<br />
PL Poland<br />
PM Saint Pierre and Miquelon<br />
PN Pitcairn<br />
PR Puerto Rico<br />
PRO Restricted to credentialed professionals and related entities<br />
PS Palestinian Territory, Occupied<br />
PT Portugal<br />
PW Palau<br />
PY Paraguay<br />
QA Qatar<br />
RE Reunion<br />
RO Romania<br />
RS Serbia<br />
RU Russian Federation<br />
RW Rwanda<br />
SA Saudi Arabia<br />
SB Solomon Islands<br />
SC Seychelles<br />
SD Sudan<br />
SE Sweden<br />
SG Singapore<br />
SH Saint Helena<br />
SI Slovenia<br />
SJ Svalbard and Jan Mayen<br />
SK Slovakia<br />
SL Sierra Leone<br />
SM San Marino<br />
SN Senegal<br />
SO Somalia<br />
SR Suriname<br />
SS South Sudan<br />
ST Sao Tome and Principe<br />
SU Soviet Union (being phased out)<br />
SV El Salvador<br />
SX Saint Maarten (Dutch part)<br />
SY Syrian Arab Republic<br />
SZ Swaziland<br />
TC Turks and Caicos Islands<br />
TD Chad<br />
TEL businesses and individuals to publish their contact data<br />
TF French Southern Territories<br />
TG Togo<br />
TH Thailand<br />
TJ Tajikistan<br />
TK Tokelau<br />
TL Timor-Leste<br />
TM Turkmenistan<br />
TN Tunisia<br />
TO Tonga<br />
TP Portuguese Timor (being phased out)<br />
TR Turkey<br />
TRAVEL entities whose primary area of activity is in the travel industry<br />
TT Trinidad and Tobago<br />
TV Tuvalu<br />
TW Taiwan, Province of China<br />
TZ Tanzania, United Republic of<br />
UA Ukraine<br />
UG Uganda<br />
UK United Kingdom<br />
UM United States Minor Outlying Islands<br />
US United States<br />
UY Uruguay<br />
UZ Uzbekistan<br />
VA Holy See (Vatican City State)<br />
VC Saint Vincent and the Grenadines<br />
VE Venezuela, Bolivarian Republic of<br />
VG Virgin Islands, British<br />
VI Virgin Islands, US<br />
VN Viet Nam<br />
VU Vanuatu<br />
WF Wallis and Futuna<br />
WS Samoa<br />
XXX the adult entertainment community<br />
YE Yemen<br />
YT Mayotte<br />
ZA South Africa<br />
ZM Zambia<br />
ZW Zimbabwe<br />
<br />
Country Code Info Source:<br />
<br />
http://en.wikipedia.org/wiki/ISO_3166-1<br />
http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements<br />
<br />
==Troubleshooting==<br />
<br />
At April 2012 there may be some problems with countries not being blocked, possibly related to the way the geo database is updated for free users. User experience and opinion vary, and following a complaint, the original forum post about this has been deleted - http://forums.contribs.org/index.php/topic,48560.0.html<br />
<br />
Users are advised to determine the effectiveness of the database for themselves.<br />
=== Bugs ===<br />
Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla]<br />
and select the smeserver-geoip component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-geoip|title=this link}}.<br />
<br />
<br />
<br />
{{#bugzilla:columns=id,product,version,status,summary |sort=id |order=desc |component=smeserver-geoip|noresultsmessage="No open bugs found."}}<br />
<br />
===Changelog===<br />
Only released version in smecontrib are listed here.<br />
<br />
{{ #smechangelog: smeserver-geoip}}<br />
<br />
<br />
----<br />
<noinclude>[[Category:Howto]]</noinclude><br />
[[Category: Contrib]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Backup_with_dar&diff=30871
Backup with dar
2016-04-05T08:42:38Z
<p>Pfloor: /* Howto set the backup file slice size */</p>
<hr />
<div>== Backup with dar using e-smith-backup ==<br />
<br />
http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter10#Backup_or_restore<br />
<br />
[http://dar.linux.free.fr/ DAR homepage]<br />
<br />
===Typical scenarios===<br />
<br />
Select ''Configure Workstation Backup'' and click perform<br />
<br />
====Windows Share====<br />
<br />
With Server backing up to a removable or shared drive in a workstation, with a weekly full backup on Friday and subsequent daily incremental backups & you wish to retain 2 backup sets on each disk, with backup to start at 8pm and finish at 8am.<br />
<br />
Backup is enabled.<br />
Backup is made on LAN workstation netshare via cifs<br />
Destination backup share folder is backup<br />
Login is backupuser<br />
Password is ********<br />
Number of rotating backup sets is 2<br />
Number of daily backups contained in each set is 7<br />
Compression level (0-9) of backup is 4<br />
Daily backup occurs at 20:00<br />
Each daily backup session is cleanly timed out after 12h except full backups which are cleanly timed out after 24 hours<br />
Full backup session (new backup sets) is allowed only on Friday<br />
<br />
====USB Disk attached to Server====<br />
For help with USB Disk preparation see [[:USBDisks]]<br />
<br />
Backup is Enabled.<br />
Backup is made on local USB disk<br />
Destination backup share folder is media/Diskname<br />
Number of rotating backup sets is 2<br />
Number of daily backups contained in each set is 14<br />
Compression level (0-9) of backup is 4<br />
Daily backup occurs at 18:30<br />
Each daily backup session is cleanly timed out after 8 hours.<br />
Full backup sessions (new backup set) are allowed everyday<br />
<br />
<br />
====More common scenarios & explanation of backup selection settings====<br />
<br />
Here are some typical scenarios, keep in mind the choice of full backup on a specified day or every day will also interact with these settings.<br />
<br />
<br />
If you wanted to do a full backup every day, & only retain 1 historical backup, then select<br />
<br />
Number of daily backups contained in each set is 1.<br />
<br />
Number of rotating backup sets is 1.<br />
<br />
<br />
If you wanted to do a full backup once every 7 days, then daily incremental backups every other day, & only retain 1 historical backup, select<br />
<br />
Number of daily backups contained in each set is 7.<br />
<br />
Number of rotating backup sets is 1.<br />
<br />
<br />
If you wanted to do a full backup once every 14 days, then daily incremental backups every other day, & only retain 1 historical backup, select<br />
<br />
Number of daily backups contained in each set is 14.<br />
<br />
Number of rotating backup sets is 1.<br />
<br />
<br />
If you wanted to do a full backup once every 28 days, then daily incremental backups every other day, & only retain 1 historical backup, select<br />
<br />
Number of daily backups contained in each set is 28.<br />
<br />
Number of rotating backup sets is 1.<br />
<br />
<br />
For any of the above, if you want to retain more historical backup sets, then change the<br />
<br />
Number of rotating backup sets to 2 or 3 or 4 as desired<br />
<br />
<br />
So let's say the full backup is set to run on Friday only, & the backup time is set for 11pm.<br />
<br />
On the first Friday night at 11pm a full backup is done, this may take many hours or even time out if there is a lot of data to backup.<br />
<br />
On the first Saturday night at 11pm if the full backup did not complete the night before (timed out as per time out setting or reached 24 hours run time), then the full backup is continued on from where it left off.<br />
<br />
If the full backup did complete, then an incremental backup is done, so only the additions & changes of data are added to the first full backup.<br />
<br />
These are added as incremental backups, in a seperate incremental backup file with a date identifier.<br />
<br />
Then every day of the backup period (being the Number of daily backups contained in each set), ie 7, 14 or 28 days, an incremental backup is done.<br />
<br />
Then on the Friday (being either day 8, 15 or 29 in examples above) at 11pm a new full backup is done.<br />
<br />
After that incremental backups are done each day, & so the cycle continues on.<br />
<br />
<br />
Note, when a full backup is done:<br />
<br />
If Number of rotating backup sets is set to 1, then the original (first) backup is deleted.<br />
<br />
If Number of rotating backup sets is set to 2, then the original (first) backup set is retained & a new backup set is created/started.<br />
<br />
If Number of rotating backup sets is set to 3, then the first & second backup sets are retained & a new backup set is created/started.<br />
<br />
If Number of rotating backup sets is set to 4, then the first, second & third backup sets are retained & a new backup set is created/started.<br />
<br />
.... & so on.<br />
<br />
Note that if a full restore is needed, the full & incremental backups are used, so all data is restored.<br />
<br />
<br />
A "practical" backup approach may be to configure for a Full backup every 7 days & daily incremental backups in between, with 2 rotating sets, so a new full backup is created each Friday & you retain a complete 7 days worth of backups for historical purposes.<br />
<br />
You could even extend that to retaining 4 sets of historical backups, in case you wanted to restore some individual files from 25 days ago.<br />
<br />
Another approach is to have 2 backup USB disks, & swap the disk every Friday (during the day) so the new full backup (on Friday night) is done to the alternate USB drive, and that alternate drive is used for the rest of the 7 days period for daily incremental backups.<br />
<br />
How often you want to create a full backup & how many daily incrementals you want to have in a set & how many historical sets & whether you swap disks off site etc, is really a part of your overall backup protocol or strategy for the site/server in question.<br />
<br />
===Backup Sets===<br />
The number of increments in a set is only equal to the "Daily backups in each set" <br />
if a multiple of 7. For instance choose 27, and you only get 21 increments, <br />
whereas 28 gives 28 increments. Or choose 3, and it gives 7 increments. <br />
(This assumes that "Full backup is allowed on" is not set to everyday).<br />
<br />
If you want the rotation, and full backup, to occur on a specified day, then<br />
choose that day in the panel, and choose a multiple of 7 for "Daily backups in<br />
each set".<br />
<br />
if you want a fixed number of increments in each set, then choose "Full backup<br />
is allowed on" = Anyday.<br />
<br />
<br />
The above descriptions can relate to unusual combination of settings, where the number of incrementals does not match or equate to the full backup period.<br />
It is probably simpler to use (& to understand) setting values that are relative to each other eg weekly (7 day) full backup with 7 incrementals.<br />
<br />
===Backup timeouts explained===<br />
Even if you choose not to timeout your full backups, a full backup cannot<br />
exceed 24h (or the cron will launch a conflicting backup job).<br />
<br />
So when you choose "Don't timeout full backup sessions", there is a default<br />
timeout just before 24h. Then the full backup can stop cleanly, and the new<br />
(incremental) backup will continue the backup.<br />
<br />
The real goal of setting a timeout+"Don't timeout full backup sessions" is for<br />
big user files systems, when we want that the backup session occurs only the<br />
night on the week days (we need the cpu and the bandwith for something else<br />
than backuping, and if we backup on the time there is too much activity, the<br />
risk of a failing backup with dar grows up, because a file can be modified<br />
during his backup), and all the days on saturday and sunday (for most common<br />
case).<br />
<br />
We can set :<br />
<br />
Backup time : 10:00 PM<br />
DaysInSet : 7<br />
FullDay on friday or saturday<br />
IncOnlyTimeOut : yes<br />
Timeout : 8 (backup stops at 6:00 AM on week days)<br />
<br />
On monday morning we can have fully backuped our server, even if the time to do<br />
it is about 32 hours (24+8). On the week days the server and the lan are are<br />
not busy with backups between 6:00 AM and 10:00 PM<br />
<br />
For servers that have large amounts of data, 200 GB+, you may see the following error with incremental backups<br />
Aborting program. User refused to continue while asking:<br />
/mnt/smb/server.2activepr.ro/set0/full-20090404.1.dar is required for further<br />
operation, please provide the file.<br />
<br />
To workaround set timeout to 23 hrs, this allows the backup to timeout cleanly, it will restart and attempt to complete the first full backup on the next run.<br />
<br />
<br />
===Using the same backup share to backup several SME servers===<br />
<br />
If you have more than one SME server on your LAN, you can use the same share (nfs or cifs) to backup all your servers. Each server will backup his data in a specific directory (the name of this directory is the FDQN of the server).<br />
<br />
<br />
===Backup disk size limits workaround===<br />
<br />
{{Warning box|The method described here permits to get daily backup work on a support with not enough space to do a new daily full backup without, before, deleting the current backup. So it must be considered with caution : if the backup fails, you'll be whithout any backup available. As explained, use this method only if security of your data is not essential, or buy a larger disk for storage.}}<br />
<br />
If having issues with the size of removable backup disks (eg 120Gb IDE on a workstation) versus the resultant backup data size (eg 120Gb of data compressing to approx 50Gb), then you can manually setup a cron job to delete the old backup file(s) before saving the new backup file(s).<br />
<br />
The specific issue experienced was being able to get one full backup onto a disk, and a weeks worth of daily incrementals, but the next weekly full backup failed, due to the need to save the new backup in the tmp folder on the removable disk, before deleting the old backup files. There was not enough space on the disk (size) being used.<br />
<br />
To workaround this, create a cron job and put it in /etc/cron.d with a script in /opt/scripts/XXX, which mounts the drive and deletes the old backup just before the new full backup commences.<br />
This will delete the old backup before the new backup commences, which is different to how the backup is designed to work by default. It is necessary to forgot the security of retaining the old backup until the new one has completed, in order to use the available hardware (smaller disk).<br />
<br />
<br />
Create the deletion script<br />
pico -w /opt/scripts/deletebkp1<br />
<br />
Enter the following (using your share name, user, pasword & domain)<br />
umount /mnt/smb<br />
/bin/mount -t cifs //stationXX/bkp1 /mnt/smb -o username=XXXXXX,password=XXXXXXXXXXXXX<br />
rm -f -R /mnt/smb/servername.yourdomain.com/<br />
rm -f -R /mnt/smb/tmp_dir/<br />
<br />
Then save & exit<br />
Ctrl o<br />
Ctrl x<br />
<br />
<br />
Create the cron job<br />
pico -w /etc/cron.d/deletebkp1<br />
<br />
Enter the following (setting the time & day to be just before your scheduled backup time), see below.<br />
The following values suit a scheduled full backup for 2.00am on Saturday morning (ie Friday evening), where the old backup gets deleted at 1:50am<br />
<br />
50 1 * * 6 root . /opt/scripts/deletebkp1<br />
<br />
Then save & exit<br />
Ctrl o<br />
Ctrl x<br />
<br />
<br />
Cron entries format is as follows:<br />
+-----------------------Minute (0-59)<br />
| +-------------------Hour of Day (0-23)<br />
| | +---------------Day of Month (1-31)<br />
| | | +-----------Month of Year (1-12)<br />
| | | | +-------Day of Week (0=Sun,6=Sat)<br />
<br />
50 1 * * 6 root . /opt/scripts/deletebkp1<br />
<br />
===Howto set the backup file slice size===<br />
<br />
The default slice or part setting is 700Mb (to suit CD's).<br />
The slice size can be changed for example to suit 4.7Gb DVD's, by making 3 parts fit on to a DVD, so the required slice size is 1529Mb (allowing for overheads & real data size).<br />
<br />
Set the Slice size in the config DB<br />
config setprop backupwk Slice 1529M<br />
<br />
Then expand the template with<br />
expand-template /etc/dar/DailyBackup.dcf<br />
<br />
The next time the backup runs, the resultant backup file will be split into 1.529Gb part sizes.<br />
<br />
===Adding/Excluding Directories and Files from the backup list===<br />
<br />
{{Warning box|The e-smith-backup panel is designed to be used as a full disaster recovery backup & restore method for your sme server, and as such relies on the correct directories being included in the backup. Do not delete any of the default directories from 40go-into as these are all essential for a successful full Restore of your backup to a clean install of the sme server operating system (you will need to reinstall add on apps or contribs). You can safely add directories eg /opt, as indicated, but that should typically be the extent of changes made.}}<br />
====Adding Files and Directories====<br />
The default backup does not include /opt<br />
<br />
To add /opt to the backup inclusion list, create a custom template fragment and add opt to the list.<br />
<br />
Create custom template fragment to add needed files and directories<br />
mkdir -p /etc/e-smith/templates-custom/etc/dar/DailyBackup.dcf<br />
<br />
pico -w /etc/e-smith/templates-custom/etc/dar/DailyBackup.dcf/41go-into<br />
<br />
--go-into opt<br />
<br />
Then expand the template<br />
expand-template /etc/dar/DailyBackup.dcf<br />
<br />
<br />
Check your backup (eg using the [[Midnight Commander plugin for DAR|mc dar plugin]]) to see that /opt is now included.<br />
It is also prudent to do a test full restore and verify that /opt (& all other backed up directories & files) are restored, as anticipated.<br />
If something is wrong with your backup or restore procedures, then required files may not be backed up and restored, so it is wise to do a test full backup & restore to fully prove your procedures are working correctly.<br />
<br />
{{Note box|<tt>--include <mask></tt> will include single files into the backup when using a path (without leading '/' ) and file name for the mask, or all files matching the mask when using wildcards. Like:<br />
--include path/to/file/sampleFileName.txt<br />
--include "*.backMeUp"<br />
<tt>--go-into <path></tt> will include entire directories with all of it's contents (files and subdirs) into the backup. Like:<br />
--go-into path/to/dir/sampleDirName<br />
}}<br />
<br />
====Excluding Files and Directories====<br />
As an example let's say you have an ibay called 'mirror' you don't want backed-up. To exclude this ibay from the backup list, create a custom template fragment and exclude it from the the list.<br />
<br />
Create custom template fragment to exclude the unneeded files and directories<br />
mkdir -p /etc/e-smith/templates-custom/etc/dar/DailyBackup.dcf<br />
pico -w /etc/e-smith/templates-custom/etc/dar/DailyBackup.dcf/45prune<br />
<br />
--prune home/e-smith/files/ibays/mirror/cgi-bin<br />
--prune home/e-smith/files/ibays/mirror/files<br />
--prune home/e-smith/files/ibays/mirror/html<br />
<br />
Then expand the template<br />
expand-template /etc/dar/DailyBackup.dcf<br />
<br />
Again, check your backup (eg using the mc dar plugin) to see that the ibay is not backed-up any more.<br />
<br />
{{Note box|<tt>--exclude <mask></tt> will exclude single files when using a path (without leading '/' ) and file name for the mask or all files matching the mask when using wildcards, from the backup. Like:<br />
--exclude path/to/file/sampleFileName.txt<br />
--exclude "*.NoBackup"<br />
<tt>--prune <path></tt> will exclude entire directories with all of it's contents (files and subdirs) from the backup. Like:<br />
--prune path/to/dir/sampleDirName<br />
}}<br />
<br />
===Use WOL to power on Workstation=== <br />
{{Note box|This is a new feature and not implimented in SME 8.0. It will be available from SME 8.1}}<br />
Wake On Lan can be used to power up the backup target workstation before starting the backup.<br />
<br />
To use WOL there simply needs to be a new variable added to the backupwk section of the configuration database, nothing else is required. This variable holds the MAC address of the target workstation, if the MAC address is 00:4E:89:F5:FD:2B use:<br />
<br />
db configuration setprop backupwk SmbHostMAC 00:4E:89:F5:FD:2B<br />
<br />
There is also the ability to specify how long to wait between the WOL packet being sent and attempting to start the backup process. The default wait time is 300 seconds, this can be varied via another configuration database setting. It is recommended to not set the wait period below 300 seconds. To set the wait time to 600 seconds:<br />
<br />
db configuration setprop backupwk SmbHostDelay 600<br />
<br />
The target system must support, and be set up to respond to, the WOL "magic packets". The network infrastructure must also support WOL packets. WOL should work across the local network without problem. WOL packets are not routeable so it won't work across the internet without additional support from hardware and/or software such as a VPN tunnel. Getting WOL to work across the internet is beyond the scope of this documentation but there are plenty of resources available elsewhere. Most wireless connected devices do not work with WOL. <br />
<br />
Note that there is no checking that the supplied MAC address is the correct one for the IP address/hostname of the target workstation. MAC address's are effectively static but IP address's/hostnames can change particularly if the target gets its IP address via DHCP. It is quite possible to have the correct target woken up and be ready but the backup to fail because the IP address has changed. However SME's DHCP server very rarely changes the IP address of a given MAC address.<br />
<br />
To stop using WOL simply delete the SmbHostMAC variable:<br />
<br />
db configuration delprop backupwk SmbHostMAC<br />
<br />
and to be tidy if the optional delay parameter has been set:<br />
<br />
db configuration delprop backupwk SmbHostDelay<br />
<br />
===How to start a one-off backup===<br />
<br />
To backup up to workstation as a one-off, not a scheduled event, run<br />
<br />
/sbin/e-smith/do_backupwk<br />
<br />
However note that scheduled backups must be enabled for the above command to work.<br />
<br />
== Some notes ==<br />
Some things to keep in mind when using SME-Server backup:<br />
<br />
=== Backup file slices are NOT autonomous ===<br />
The catalogue of the contents of the backup is put in the last slice. If for some reason the last slice can not be written (e.g. backup medium is full or network failure), is lost or corrupt, the slices already saved are useless.<br />
<br />
=== NFS ===<br />
<br />
27/06/2012 - With the current version of SME Version 8 and 9 it would appear that NFS is not installed by default.<br />
<br />
To enable backup via nfs you will need to install nfs-utils from base :<br />
<br />
yum install nfs-utils<br />
<br />
For further information please see this bug http://bugs.contribs.org/show_bug.cgi?id=7006<br />
<br />
=== Naming of the backups on the workstation share or USB disk ===<br />
<br />
* For a SME server all backups sets are put in a directory which has the FQDN of the server as a name, ie '''hostname.domain/'''<br />
<br />
* All backups of a set are put in a subdirectory with the name of the set, ie. '''hostname.domain/set''0''/''', '''hostname.domain/set''1''/''', etc.<br />
<br />
* During a backup session, all session files are temporary put in the directory '''hostname.domain/tmp_dir/'''<br />
<br />
* In a set the full backup is named '''full-yyyymmdd'''<br />
<br />
* In a set the incremental backups are named '''inc''1''-yyyymmdd''', '''inc''2''-yyyymmdd''', etc. <br />
<br />
* In a full backup the files (slices) are named '''full-yyyymmdd.1.dar''', '''full-yyyymmdd.2.dar''', etc.<br />
<br />
* In an incremental backup the files (slices) are named '''inc''n''-yyyymmdd.1.dar''', '''inc''n''-yyyymmdd.2.dar''', etc.<br />
<br />
All backup files have allways distinct names. If the backup files are moved elsewhere for archiving, you must recreate the directory structure before doing a restore with the server manager.<br />
<br />
=== cifs - mount error 20 = Not a directory ===<br />
<br />
Some network drives don't function correctly with Backup with DAR and the cifs file system. The mount command returns "mount error 20 = Not a directory". See [http://bugs.contribs.org/show_bug.cgi?id=4923 Bug 4923]. <br />
<br />
This can be worked around by adding the "nounix" option to the mount command in the /etc/e-smith/events/actions/workstation-backup-dar file. <br />
<br />
{{Warning box|This change may not be preserved across updates/upgrades to the Backup with Dar sub-system or to SME Server itself.<br />
<br />
An update/upgrade may stop your backups working and require this change to be made again.}}<br />
<br />
Edit the above file and find the line:<br />
<br />
$err = qx(/bin/mount -t cifs "$smbhost:$smbshare" $mntdir -o user=$login,pass=$password 2>&1);<br />
<br />
and change it to:<br />
<br />
$err = qx(/bin/mount -t cifs "$smbhost:$smbshare" $mntdir -o nounix,user=$login,pass=$password 2>&1);<br />
<br />
Save the file.<br />
<br />
== Manually restoring from dar archive created by e-smith-backup ==<br />
<br />
Restores can be done for:<br />
<br />
-the entire system.<br />
<br />
-a selected file only.<br />
<br />
-a selected directory and all of its contents.<br />
<br />
The entire system and a selected file only can be done through the server-manager.<br />
<br />
The selected directory can be done via shell.<br />
(You will have to adjust for your particular situation.)<br />
<br />
First, MOUNT THE BACKUP DRIVE (if required):<br />
mount /dev/sdc1 /media/BackupDrive1/<br />
<br />
Then, RESTORE THE DIRECTORY:<br />
dar -x /media/BackupDrive1/server.domain.local/set2/full-201408092200 -N -R / -w -g home/e-smith/files/ibays/share_data/files<br />
<br />
You may also have to RESTORE ANY INCREMENTS:<br />
dar -x /media/BackupDrive1/server.domain.local/set2/inc-001-201408102200.1.dar -N -R / -w -g home/e-smith/files/ibays/share_data/files<br />
dar -x /media/BackupDrive1/server.domain.local/set2/inc-002-201408112200.1.dar -N -R / -w -g home/e-smith/files/ibays/share_data/files<br />
dar -x /media/BackupDrive1/server.domain.local/set2/inc-003-201408122200.1.dar -N -R / -w -g home/e-smith/files/ibays/share_data/files<br />
dar -x /media/BackupDrive1/server.domain.local/set2/inc-004-201408132200.1.dar -N -R / -w -g home/e-smith/files/ibays/share_data/files<br />
<br />
<br />
----<br />
[[Category:Contrib]]<br />
[[Category: Backup]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=29632
Zarafa on SME 9
2015-11-27T01:18:55Z
<p>Pfloor: /* MySQL */</p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|<br />
'''This wiki page is specific to SME9 only.'''<br />
<br />
'''There is a separate wiki page on how to install Zarafa 7.x on SME7 [[Zarafa|Zarafa on SME 7]].'''<br />
<br />
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME8 [[Zarafa_on_SME8|Zarafa on SME 8]].'''<br />
}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta2. It should be ready for production servers when SME9 reaches RC stage.<br />
This contrib will NOT work on SME 7 or SME8, there are unresolved dependencies.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries. <br /><br /><br />
If Zarafa was used with the db-plugin before, the InnoDB engine has to be enabled. To enable the InnoDB engine, run the following commands:<br />
<br />
db configuration setprop mysqld InnoDB enabled<br /><br />
expand-template /etc/my.cnf<br /><br />
sv t /service/mysqld<br /><br /><br />
Users accounts have to match the existing zarafa-users.}}<br />
Now install smeserver-zarafa-unix by performing the following:<br />
yum install smeserver-zarafa-unix --enablerepo=smecontribs<br />
<br />
NOTE: If you installed the GPL version of Zarafa, you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
After rpm install execute the following:<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
=====MySQL=====<br />
The default MySQL database created is named 'zarafa' and the default user is named 'zarafa'<br />
<br />
The MySQL password is a strong random string and automatically set. See:<br />
config show zarafa-server<br />
<br />
To reset the existing database password you can use:<br />
/etc/e-smith/events/actions/zarafa-reset-db-password<br />
<br />
=====Controlling Zarafa Services=====<br />
To control the zarafa services (start/stop etc.) the following command can be used:<br />
signal-event zarafa-services [option]<br />
Where the [option] can be on of the following:<br />
start|stop|restart|update|enabled|disabled<br />
The update option will rebuild the zarafa config files based on the current db settings.<br />
<br />
=====To disable global Zarafa for all users=====<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
=====To enable an individual user if Global is disabled=====<br />
db accounts setprop $USERNAME Zarafa enabled<br />
signal-event user-modify $USERNAME<br />
=====To enable the admin account=====<br />
db accounts setprop admin Zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
=====Known working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=====Additional Mobile Synchronization Information=====<br />
<br />
'''SSL Synchronization with Windows Mobile devices'''<br />
<br />
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/<br />
<br />
{{#bugzilla:columns=id,product,version,status,summary |sort=id|order=desc |component=smeserver-zarafa|noresultsmessage="No open bugs found."}}</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=29631
Zarafa on SME 9
2015-11-27T00:37:54Z
<p>Pfloor: /* MySQL */</p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|<br />
'''This wiki page is specific to SME9 only.'''<br />
<br />
'''There is a separate wiki page on how to install Zarafa 7.x on SME7 [[Zarafa|Zarafa on SME 7]].'''<br />
<br />
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME8 [[Zarafa_on_SME8|Zarafa on SME 8]].'''<br />
}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta2. It should be ready for production servers when SME9 reaches RC stage.<br />
This contrib will NOT work on SME 7 or SME8, there are unresolved dependencies.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries. <br /><br /><br />
If Zarafa was used with the db-plugin before, the InnoDB engine has to be enabled. To enable the InnoDB engine, run the following commands:<br />
<br />
db configuration setprop mysqld InnoDB enabled<br /><br />
expand-template /etc/my.cnf<br /><br />
sv t /service/mysqld<br /><br /><br />
Users accounts have to match the existing zarafa-users.}}<br />
Now install smeserver-zarafa-unix by performing the following:<br />
yum install smeserver-zarafa-unix --enablerepo=smecontribs<br />
<br />
NOTE: If you installed the GPL version of Zarafa, you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
After rpm install execute the following:<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
=====MySQL=====<br />
The default MySQL database created is named 'zarafa' and the default user is named 'zarafa'<br />
<br />
The MySQL password is a strong random string and automatically set. See:<br />
config showp zarafa-server<br />
<br />
To reset the existing database password you can use:<br />
/etc/e-smith/events/actions/zarafa-reset-db-password<br />
<br />
=====Controlling Zarafa Services=====<br />
To control the zarafa services (start/stop etc.) the following command can be used:<br />
signal-event zarafa-services [option]<br />
Where the [option] can be on of the following:<br />
start|stop|restart|update|enabled|disabled<br />
The update option will rebuild the zarafa config files based on the current db settings.<br />
<br />
=====To disable global Zarafa for all users=====<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
=====To enable an individual user if Global is disabled=====<br />
db accounts setprop $USERNAME Zarafa enabled<br />
signal-event user-modify $USERNAME<br />
=====To enable the admin account=====<br />
db accounts setprop admin Zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
=====Known working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=====Additional Mobile Synchronization Information=====<br />
<br />
'''SSL Synchronization with Windows Mobile devices'''<br />
<br />
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/<br />
<br />
{{#bugzilla:columns=id,product,version,status,summary |sort=id|order=desc |component=smeserver-zarafa|noresultsmessage="No open bugs found."}}</div>
Pfloor
https://wiki.koozali.org/index.php?title=SME9.0_Contribs_QA&diff=24494
SME9.0 Contribs QA
2014-06-24T20:21:44Z
<p>Pfloor: /* smeserver-zarafa-unix */</p>
<hr />
<div>=Version 9 beta3 Contrib testing=<br />
This document lists Contribs that, need to be tested or have had been tested running under SME 9<br />
<br />
Contribs should work if they are perl or php based (unless php53 deprecated some functions needed) . Some binary applications will work as well.<br />
<br />
Contribs using perl modules might be broken due to change of path<br />
<br />
Please also see [[Contribs Bugreport]]<br />
<br />
==Test guidelines==<br />
Considerations_before_installing advises that Contribs for SME 9 have not yet been released, this is to avoid dev workload diagnosing bugs caused by contribs.<br />
<br />
Please don't post SME 9 bugs unless you can replicate the bug with the contrib removed or isolated.<br />
<br />
{{Note box|If you have suggestions, issues or solutions for a contrib, please post them in bugzilla {{BugzillaFileBug|product=SME%20Contribs|component=|summary=|comment=|title=against the contrib.}} }}<br />
<br />
==Setup==<br />
During the transition from SME8 to SME9, contrib packages will be migrated to the SME9 contrib repository. If the contrib is not yet in the SME8 Contrib repository and an entry in this Q&A suggests it will install properly then you will need to install the contrib from the SME8 repository.<br />
<br />
Check to see if you already have the sme8contribs repository set up using the command:<br />
db yum_repositories show sme8contribs<br />
If it returns nothing then you will need to create a repo named sme8contribs, which points to the SME 8 smecontribs repo<br />
<br />
<br />
db yum_repositories set sme8contribs repository \<br />
Name 'SME 8 - contribs' \<br />
MirrorList 'http://mirrorlist.contribs.org/mirrorlist/smecontribs-8' \<br />
GPGCheck yes \<br />
Visible no \<br />
status disabled<br />
<br />
signal-event yum-modify<br />
yum clean all<br />
<br />
<br />
{{Note box|'''now you will need to add the package from sme8contribs and smecontribs to resolve some problems of dependencies...'''}}<br />
<br />
{{Note box|'''you might also consider to add some external repo such as [[dag]] and [[epel]]...'''}}<br />
<br />
<br />
The following shows an example of how to install a contrib from the SME 8 repo:<br />
<br />
yum '''--enablerepo=sme8contribs,smecontribs''' install smeserver-openvpn-s2s<br />
<br />
Notice the additional phrase "sme8contribs," in the command line.<br />
<br />
Another example is as follows:<br />
yum install smeserver-usbdisksmanager --enablerepo=sme8contribs --enablerepo=smecontribs<br />
<br />
==Template for testing==<br />
<br />
=== not working===<br />
please open a bug {{BugzillaFileBug|product=SME%20Contribs|component=|summary=|comment=|title=against the contrib.}}, and write in the wiki you tested it and it fails.<br /><br />
{{Tip box|the title of your bug should look to "'''sme9contribs:'''Can't locate esmith/FormMagick/Panel/passwordopt.pm" for example.}}<br />
BROKEN with your signature (<nowiki>--~~~~</nowiki>)<br />
* wikipage : [[smeserver-contrib]]<br />
* bugs : [[bugzilla:NUMBER]]<br />
* to install : yum install smeserver-contrib --enablerepo=sme8contribs,smecontribs,epel<br />
* version-release tried:<br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
* error :<br />
* workaround :<br />
* tested beyond installation : yes / no<br />
<br />
=== working===<br />
write here it works, with theses informations :<br /><br />
<br />
WORKS with your signature. (<nowiki>--~~~~</nowiki>)<br />
* wikipage : [[smeserver-contrib]]<br />
* to install : yum install smeserver-contrib --enablerepo=sme8contribs,smecontribs,epel<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
* tested beyond installation : yes / no<br />
<br />
Then please open a bug {{BugzillaFileBug|product=SME%20Contribs|component=|summary=|comment=|title=against the contrib.}}, to ask to push the contribs to sme9contribs.<br /><br />
<br />
{{Tip box|The title of your bug should be for example "'''first import to sme9 tree [smeserver-mediawiki]'''"}}<br />
<br />
=Contribs=<br />
<br />
List of Contribs being tested<br />
* [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=component&product=SME+Contribs&format=table&action=wrap&version=9beta Bugs related to contribs in SME 9]<br />
<br />
<br />
<br />
==Need to test==<br />
<br />
===smeserver-adv-samba===<br />
*[[Advanced_Samba]]<br />
<br />
===smeserver-affa===<br />
*[[Affa]]<br />
<br />
===smeserver-ajaxterm===<br />
*[[Ajaxterm]]<br />
<br />
<br />
===smeserver-arpwatch===<br />
*[[arpwatch]]<br />
<br />
===smeserver-automysqlbackup===<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 17:20, 15 January 2014 (MST)<br />
*wikipage : [[AutoMysqlBackup]]<br />
*to install :<br />
yum install --enablerepo=stephdl smeserver-automysqlbackup<br />
*version-release installed:<br />
automysqlbackup-3.0.RC6-3.el5.sme.noarch <br />
smeserver-automysqlbackup-3.0.RC6-3.el5.sme.noarch<br />
*dependencies not in smeos,smeaddons,smecontribs: all in [[stephdl]]<br />
*tested beyond installation : yes<br />
Works as expected, just follow instructions as per the wiki above. see [[bugzilla:8339]]<br />
<br />
===smeserver-awstats===<br />
*[[AWStats]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 16:06, 19 June 2014 (MDT) see [[bugzilla:8435]]<br />
* wikipage : [[AWStats]]<br />
* to install : for now you have to install from epel, dag and smedev : yum --enablerepo=dag,epel,smedev install smeserver-awstats<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs: awstats from dag, perl-Geo-IP from epel<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-BackupPC===<br />
<br />
*[[BackupPC]]<br />
<br />
'''WORKS''' --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 11:57, 21 April 2014 (MDT)<br />
* wikipage : [[BackupPC]]<br />
* to install :<br />
yum install smeserver-contrib --enablerepo=smecontribs,epel<br />
* version-release installed:<br />
smeserver-BackupPC-0.1-12.el5.sme.noarch.rpm <br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
see epel repository for backuppc<br />
BackupPC-3.3.0-2.el6.i686.rpm<br />
* tested beyond installation : yes<br />
it works as expected, it is my main network backup software. see [[bugzilla:8336]] for import to smecontribs<br />
<br />
===smeserver-bandwidthd===<br />
*[[bandwidthd]]<br />
<br />
===smeserver-bridge-interface===<br />
* [[BridgeInterface]]<br />
<br />
'''WORKS''' --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 12:19, 21 April 2014 (MDT)<br />
* wikipage : [[BridgeInterface]]<br />
* to install :<br />
yum --enablerepo=smecontribs,epel,dag install smeserver-bridge-interface<br />
* version-release installed:<br />
from sme9contribs<br />
smeserver-bridge-interface-0.2-1.el6.sme.noarch.rpm<br />
from base<br />
openssl098e-0.9.8e-17.el6.centos.2.i686.rpm <br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
from epel,dag<br />
openvpn-2.3.1-3.el5.i386.rpm<br />
pkcs11-helper-1.07-2.el5.1.i386.rpm<br />
* tested beyond installation : yes<br />
<br />
It works as expected except that we must use some dependencies from dag and epel, see [[bugzilla:8337]]<br />
<br />
===smeserver-bugzilla===<br />
* no wiki<br />
<br />
===smeserver-cacti===<br />
*[[cacti]]<br />
<br />
===smeserver-crontab_manager===<br />
*[[Crontab_Manager]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 15:33, 19 June 2014 (MDT) see [[bugzilla:8412]]<br />
* wikipage : [[Crontab_Manager]]<br />
* to install : yum install smeserver-crontab_manager --enablerepo=smecontribs<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-dansguardian===<br />
*[[Dansguardian]]<br />
<br />
<br />
===smeserver-dar2===<br />
*[[DAR2]]<br />
<br />
===smeserver-ddclient===<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 06:30, 21 June 2014 (MDT)<br />
*wikipage : [[ddclient]]<br />
*to install :<br />
yum install --enablerepo=stephdl,epel smeserver-ddclient<br />
*version-release installed:<br />
<br />
*dependencies not in smeos,smeaddons,smecontribs: all in [[stephdl]] and [[epel]]<br />
<br />
*tested beyond installation : yes<br />
Works as expected, just follow instructions as per the wiki above. see [[bugzilla:8338]]<br />
<br />
===smeserver-denyhosts===<br />
* [[Denyhosts]]<br />
<br />
===smeserver-dimp===<br />
* no wiki<br />
<br />
===smeserver-diskusage===<br />
*[[Diskusage]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 15:37, 19 June 2014 (MDT) see [[bugzilla:8410]]<br />
* wikipage : [[Diskusage]]<br />
* to install : yum install smeserver-diskusage --enablerepo=smecontribs<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-durep===<br />
*[[durep]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 05:22, 21 June 2014 (MDT) see [[bugzilla:8454]]<br />
* wikipage : [[durep]]<br />
* to install : yum install smeserver-durep --enablerepo=stephdl,epel<br />
* version-release installed: smeserver-durep-1.5.0-1<br />
* dependencies not in smeos,smeaddons,smecontribs: [[stephdl]] and [[epel]] repositories<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-egroupware===<br />
*[[egroupware]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 13:28, 24 June 2014 (MDT) see [[bugzilla:8438]]<br />
* wikipage : [[egroupware]]<br />
* to install : yum install smeserver-egroupware --enablerepo=smedev,Server_eGroupWare<br />
* version-release installed: <br />
smeserver-egroupware-1.8.6-1.el6.sme.noarch<br /><br />
<br />
eGroupware-1.8.007.20140512-5.1.noarch<br />
* dependencies not in smeos,smeaddons,smecontribs: [[Server_eGroupWare]] repository and smedev for now but see [[bugzilla:8438]], the bug is pending the release in smecontribs (9.0)<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-ejabberd===<br />
*[[Ejabberd]]<br />
<br />
===smeserver-ezmlm-web===<br />
*[[Ezmlm]]<br />
<br />
===smeserver-fetchmail===<br />
WORKS --[[User:Eastend99|Eastend99]] ([[User talk:Eastend99|talk]]) 14:36, 9 juni 2014 (CET) and --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 05:47, 21 June 2014 (MDT) see [[bugzilla:8455]]<br />
*wikipage : [[Fetchmail]]<br />
*to install :<br />
yum install --enablerepo=stephdl smeserver-fetchmail<br />
*version-release installed:<br />
smeserver-fetchmail.noarch 0:1.6-1.el6.sme <br />
*dependencies not in smeos,smeaddons,smecontribs: all in [[stephdl]]<br />
<br />
*tested beyond installation : yes<br />
Works as expected, successfull retrieved e-mail<br />
<br />
===smeserver-freepbx===<br />
*[[FreePBX]]<br />
<br />
===smeserver-geoip===<br />
*[[GeoIP]]<br />
<br />
===smeserver-gollem===<br />
* no wiki, Horde plugin<br />
<br />
===smeserver-groupmembers-panel===<br />
*[[Groupmembers_Panel]]<br />
<br />
===smeserver-htbwshaper===<br />
*[[Wondershaper]] (need update)<br />
please see [[Qos]] this contrib is no longer maintained<br />
<br />
===smeserver-hwinfo===<br />
*[[Hardware Info]]<br />
<br />
===smeserver-hylafax===<br />
*[[HylaFax]]<br />
<br />
===smeserver-isoqlog===<br />
*[[isoqlog]]<br />
<br />
===smeserver-jeta===<br />
* no wiki<br />
<br />
===smeserver-kplaylist===<br />
*[[KPlaylist]]<br />
<br />
===smeserver-kronolith===<br />
*[[Kronolith]]<br />
<br />
===smeserver-Lazy_Admin_Tools===<br />
*[[Lazy_Admin_Tools]]<br />
<br />
===smeserver-madsonic===<br />
*[[Madsonic]]<br />
<br />
===smeserver-mailman===<br />
*[[Mailman]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 10:01, 20 June 2014 (MDT) see [[bugzilla:8453]]<br />
* wikipage : [[Mailman]]<br />
* to install : yum install smeserver-mailman --enablerepo=stephdl<br />
* version-release installed: mailman.x86_64 3:2.1.12-25.el6.sme smeserver-mailman.noarch 0:1.5.0-1.el6.sme<br />
* dependencies not in smeos,smeaddons,smecontribs: [[stephdl]] repository<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-mailsorting===<br />
*[[mailsorting]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 12:29, 23 June 2014 (MDT) see [[bugzilla:8465]]<br />
* wikipage : [[mailsorting]]<br />
* to install : yum install smeserver-mailsorting --enablerepo=stephdl,dav<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs: perl-Unicode-IMAPUtf7 (dav)<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-mailstats===<br />
*[[mailstats]]<br />
Brian Read - 28Jan14 and --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 13:56, 23 June 2014 (MDT) see [[bugzilla:8445]]<br />
* Installed ok.<br />
* tested beyond installation : only to the extent that it works with no data!! However it is pure perl, so I am not expecting it to fail<br />
Someone could build an RPM.<br />
tested beyond installation : Yes --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 13:56, 23 June 2014 (MDT)<br />
<br />
===smeserver-mimp===<br />
* no wiki<br />
<br />
===smeserver-mnemo===<br />
*[[Mnemo]]<br />
<br />
===smeserver-mod_dav===<br />
*[[DAV]]<br />
<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 15:35, 19 June 2014 (MDT) see [[bugzilla:8340]]<br />
* wikipage : [[DAV]]<br />
* to install : yum install smeserver-mod_dav --enablerepo=smecontribs<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-mod_deflate===<br />
*[[mod_deflate]]<br />
<br />
===smeserver-mod_python===<br />
*[[Mod_Python]]<br />
<br />
===smeserver-nag===<br />
*[[Nag]]<br />
<br />
===smeserver-nagios===<br />
*[[Nagios]]<br />
<br />
===smeserver-nagios-backup===<br />
*[[Nagios]]<br />
<br />
===smeserver-nagios-nrpe===<br />
*[[Nagios_NRPE]]<br />
<br />
===smeserver-nagios-nsca===<br />
*[[Nagios_NSCA]]<br />
<br />
===smeserver-nagios-plugins-mysql===<br />
*[[Nagios]]<br />
<br />
===smeserver-nfs===<br />
*[[NFS]]<br />
<br />
===smeserver-oats===<br />
*[[Oats]]<br />
<br />
===smeserver-ocsinventory===<br />
*[[OCS_Inventory]]<br />
<br />
===smeserver-openoffice-portable===<br />
*[[OpenOffice_for_Windows]]<br />
<br />
===smeserver-openvpn-bridge===<br />
*[[OpenVPN_Bridge]]<br />
'''WORKS''' --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 13:11, 21 April 2014 (MDT)<br />
* wikipage : [[OpenVPN_Bridge]]<br />
* to install :<br />
yum --enablerepo=smecontribs install smeserver-openvpn-bridge<br />
* version-release installed:<br />
perl-Net-OpenVPN-Manage-0.02-2.el6.sme.noarch.rpm<br />
perl-Net-Telnet-3.03-11.el6.noarch.rpm<br />
smeserver-openvpn-bridge-2.1-1.el6.sme.noarch.rpm<br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
* tested beyond installation : yes<br />
all rpms are available in sme9contribs<br />
<br />
===smeserver-openvpn-s2s===<br />
*[[OpenVPN_SiteToSite]]<br />
<br />
===smeserver-password===<br />
<br />
Work see [[bugzilla:8137]]<br />
<br />
* wikipage : [[Password]]<br />
* to install :<br />
yum install --enablerepo=smecontribs smeserver-password<br />
* version-release tried:<br />
smeserver-password-1.0.0-32.el5.sme.noarch.rpm<br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
all in smecontribs<br />
* error :<br />
* workaround : see [[bugzilla:8137]]<br />
* tested beyond installation : YES<br />
<br />
===smeserver-phpki=== <br />
*[[PHPki]]<br />
'''WORKS''' --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 12:25, 21 April 2014 (MDT)<br />
* wikipage : [[PHPki]]<br />
* to install :<br />
yum --enablerepo=smecontribs install smeserver-phpki<br />
* version-release installed:<br />
php-process-5.3.3-27.el6_5.i686.rpm <br />
phpki-0.82-16.el6.sme.noarch.rpm<br />
smeserver-phpki-0.2-1.el6.sme.noarch.rpm<br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
nothing at all<br />
* tested beyond installation : yes<br />
all rpms are in sme9contribs tree<br />
<br />
===smeserver-phpldapadmin===<br />
*[[Phpldapadmin]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 11:14, 21 June 2014 (MDT)-- see [[bugzilla:8456]]<br />
* wikipage : [[Phpldapadmin]]<br />
* to install : yum install smeserver-phpldapadmin --enablerepo=stephdl,epel<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs: all is in [[stephdl]] and [[epel]] repo<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-phpmyadmin===<br />
*[[PHPMyAdmin]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 15:38, 19 June 2014 (MDT) see [[bugzilla:8413]]<br />
* wikipage : [[PHPMyAdmin]]<br />
* to install : yum install smeserver-phpmyadmin --enablerepo=stephdl,epel<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs: all is in [[stephdl]] and [[epel]] repo<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-phpsysinfo===<br />
*[[Phpsysinfo]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 17:41, 21 June 2014 (MDT)<br />
*wikipage : [[Phpsysinfo]]<br />
*to install :<br />
yum install --enablerepo=stephdl smeserver-phpsysinfo<br />
*version-release installed: smeserver-phpsysinfo-3.1.13<br />
*dependencies not in smeos,smeaddons,smecontribs: all in [[stephdl]]<br />
*tested beyond installation : yes<br />
Works as expected, just follow instructions as per the wiki above<br />
<br />
===smeserver-phpvirtualbox===<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 17:37, 15 January 2014 (MST)<br />
*wikipage : [[Phpvirtualbox]]<br />
*to install :<br />
yum install --enablerepo=stephdl,virtualbox smeserver-virtualbox smeserver-phpvirtualbox<br />
*version-release installed:<br />
smeserver-phpvirtualbox.noarch 0:4.3.0-10.el5.sme<br />
smeserver-virtualbox.noarch 0:4.3.0-5.el5.sme <br />
*dependencies not in smeos,smeaddons,smecontribs: Virtualbox is in the virtualbox repository<br />
You have to install dkms but it is in the relevant epel repository<br />
*tested beyond installation : yes<br />
Works as expected, just follow instructions as per the wiki above<br />
<br />
===smeserver-phpwebftp===<br />
*[[PhpWebFtp]]<br />
<br />
===smeserver-popfile===<br />
*[[popfile]]<br />
<br />
===smeserver-postgresql===<br />
*[[Postgres]] ?? should update this wiki page<br />
<br />
===smeserver-print-monitor===<br />
*[[LPRng print queue monitor]]<br />
<br />
===smeserver-qmHandle===<br />
*[[Qmhandle_mail_queue_manager]]<br />
<br />
===smeserver-qpsmtpd-spamassassinlevelstars===<br />
*[[Email#X-Spam-Level_Header_in_Email_Messages]]<br />
<br />
===smeserver-raidmonitor===<br />
*[[raidmonitor]]<br />
obsolete<br />
<br />
===smeserver-rdiff-backup===<br />
*[[rdiff-backup]]<br />
<br />
===smeserver-remoteuseraccess===<br />
*[[remoteuseraccess]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 11:17, 21 June 2014 (MDT)<br />
* wikipage : [[remoteuseraccess]]<br />
* to install : yum install smeserver-remoteuseraccess --enablerepo=smecontribs<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs: all is in smecontribs<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-rkhunter===<br />
*[[rkhunter]]<br />
<br />
===smeserver-roundcube===<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 17:37, 15 January 2014 (MST)<br />
*wikipage : [[RoundCube]]<br />
*to install :<br />
yum install --enablerepo=stephdl smeserver-roundcube<br />
*version-release installed:<br />
<br />
*dependencies not in smeos,smeaddons,smecontribs: all in [[stephdl]]<br />
*tested beyond installation : yes<br />
Works as expected, just follow instructions as per the wiki above<br />
<br />
===smeserver-sane===<br />
*[[SANE]]<br />
<br />
===smeserver-sarg===<br />
*[[Sarg]]<br />
<br />
===smeserver-shared-folders===<br />
*[[SharedFolders]]<br />
[[User:Easren99|Eastend99]] ([[User talk:Eastend99|talk]]) 10:35, 27 March 2014 (CET) and --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 10:41, 21 June 2014 (MDT)<br />
* wikipage : [[SharedFolders]], see also [http://forums.contribs.org/index.php/topic,50325.msg253425.html#msg253425 this] forum post<br />
* to install : <br />
yum --enablerepo=smecontribs install smeserver-shared-folders<br />
* version-release installed: <br />
smeserver-shared-folders noarch 0.3-2.el6.sme smecontribs<br />
* dependencies not in smeos,smeaddons,smecontribs: <br />
smeserver-mod_dav noarch 1.0-1.el5.sme smecontribs <br />
* tested beyond installation : shared folder creation works, local and public access not tested<br />
<br />
===smeserver-sitemaker===<br />
*[[SME_Site_Maker]]<br />
<br />
===smeserver-sme8admin===<br />
*[[Sme8admin]]<br />
obsoletes; see sme9admin<br />
<br />
===smeserver-sme9admin===<br />
*[[Sme9admin]]<br />
<br />
===smeserver-subsonic===<br />
*[[Subsonic]]<br />
<br />
===smeserver-subversion===<br />
*[[subversion]]<br />
<br />
===smeserver-sysmon===<br />
*[[sysmon]]<br />
<br />
===smeserver-tftp-server===<br />
*[[Tftp_server]]<br />
<br />
===smeserver-theaddressbook===<br />
*[[The Address Book]]<br />
<br />
===smeserver-thinclient===<br />
*[[Thinclient]]<br />
Warning: The contrib allows to specify the TFTP server as "Self". This worked well under SME7 but not under SME8. To get this working under SME8, we had to choose the SME server's IP address to achieve the same result as "self" otherwise the clients cannot find/load from the TFTP server. We have reported this as bug 6542 for the contrib but with this workaround, the contrib is working well under SME8. <br />
Bug has been reported as work for me, so please comment on it if you can replicate.<br />
<br />
===smeserver-transmission===<br />
Works see [[bugzilla:8134]]<br />
<br />
* wikipage : [[transmission]]<br />
* to install :<br />
yum install --enablerepo=stephdl smeserver-transmission<br />
* version-release tried: smeserver-transmission-0.0.2-1.el6.sme.noarch.rpm <br />
* dependencies not in smeos,smeaddons,smecontribs: in stephdl<br />
transmission-2.76-1geekery.x86_64.rpm<br />
transmission-cli-2.76-1geekery.x86_64.rpm<br />
transmission-common-2.76-1geekery.x86_64.rpm<br />
transmission-daemon-2.76-1geekery.x86_64.rpm <br />
libevent2-2.0.10-1geekery.x86_64.rpm<br />
<br />
* tested beyond installation : Go :)<br />
<br />
===smeserver-tw-logonscript===<br />
*[[Smeserver-tw-logonscript]]<br />
<br />
===smeserver-unjunkmgr===<br />
*[[Sme-unjunkmgr]]<br />
BROKEN --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 10:07, 25 April 2014 (MDT)<br />
* bugs : [[bugzilla:8353]]<br />
* to install : yum install smeserver-contrib --enablerepo=sme8contribs,smecontribs,epel<br />
* version-release tried:<br />
# rpm -qa smeserver-unjunkmgr<br />
smeserver-unjunkmgr-2.1-3.el5.sme.noarch<br />
* dependencies not in smeos,smeaddons,smecontribs:<br />
* error : see bug report<br />
* workaround : see bug report<br />
* tested beyond installation : broken<br />
<br />
===smeserver-updates===<br />
*[[Smeserver-updates]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 10:17, 23 June 2014 (MDT) see [[bugzilla:8463]]<br />
* wikipage : [[Smeserver-updates]]<br />
* to install : yum install Smeserver-updates --enablerepo=stephdl<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs: all is in stephdl<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-usbdisksmanager===<br />
*[[Disk_Manager]]<br />
<br />
===smeserver-userpanel===<br />
*[[UserManager]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 12:14, 23 June 2014 (MDT) see [[bugzilla:8464]]<br />
* wikipage : [[UserManager]]<br />
* to install : yum install smeserver-userpanel enablerepo=stephdl<br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs: all in stephdl<br />
* tested beyond installation : Yes<br />
<br />
===smeserver-userpanels===<br />
*[http://www.dungog.net/wiki/Usermanager#Change_password Smeserver-userpanels] , needs wiki page at contribs<br />
<br />
===smeserver-UserWebSpace===<br />
* no wiki page<br />
<br />
===smeserver-vacation===<br />
*[[Vacation]]<br />
<br />
===smeserver-virtualbox===<br />
see [[SME9.0_Contribs_QA#smeserver-phpvirtualbox]]<br />
<br />
Works as expected, just follow instructions as per the wiki above<br />
<br />
===smeserver-wbl===<br />
*[[Email#Email_WBL_server_manager_panel]]<br />
<br />
===smeserver-webconsole===<br />
*[[webconsole]]<br />
<br />
===smeserver-webshare===<br />
*[[Webshare]] <br />
<br />
===smeserver-wordpress===<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 17:38, 15 January 2014 (MST)<br />
*wikipage : [[wordpress]] see [[bugzilla:8451]]<br />
*to install :<br />
yum install --enablerepo=stephdl,epel smeserver-wordpress<br />
*version-release installed:<br />
smeserver-wordpress-1.2-1.el6.sme.noarch<br />
*dependencies not in smeos,smeaddons,smecontribs: all in epel<br />
php-IDNA_Convert-0.8.0-1.el6.noarch 1/8 <br />
php-simplepie-1.3.1-3.el6.noarch 2/8 <br />
php-process-5.3.3-27.el6_5.x86_64 3/8 <br />
1:enchant-1.5.0-4.el6.x86_64 4/8 <br />
php-enchant-5.3.3-27.el6_5.x86_64 5/8 <br />
php-PHPMailer-5.2.2-1.el6.noarch 6/8 <br />
wordpress-3.8-1.el6.noarch <br />
*tested beyond installation : yes<br />
Works as expected, just follow instructions as per the wiki above<br />
<br />
===smeserver-xinetd===<br />
*[[xinetd]]<br />
===smeserver-zarafa-unix===<br />
*[[Zarafa_on_SME_9]]<br />
WORKS --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 15:46, 19 June 2014 (MDT) see [[bugzilla:7383]]<br />
* wikipage : [[Zarafa_on_SME_9]]<br />
* to install : please see How to install directly in the [[Zarafa_on_SME_9|wikipage]] <br />
* version-release installed:<br />
* dependencies not in smeos,smeaddons,smecontribs: All Zarafa RPM's must be downloaded, extracted and installed using "yum localinstall". See Wiki page for detailed instructions.<br />
* tested beyond installation : Yes<br />
<br />
== Won't be ported to SME9 ==<br />
===smeserver-vmware-server===<br />
vmware server is not supported anymore please consider using virtualbox, or KVM...</div>
Pfloor
https://wiki.koozali.org/index.php?title=Main_Page&diff=24488
Main Page
2014-06-24T19:34:23Z
<p>Pfloor: </p>
<hr />
<div>__NOTOC__<br />
{{Languages}}<br />
{| style="border: solid 1px; border-color:lightgray;" width=100% cellpadding=5 cellspacing=0<br />
| align=left valign=top cellspacing=0 cellpadding=0 style="background-color: #ffff99;" | '''Current Stable Release:'''<br />
[[SME Server:8.1 |SME Server 8.1]] released on 28th February 2014<br />
| align=left valign=top cellspacing=0 cellpadding=0 style="background-color: #ffff99;" |[http://batchgeo.com/map/e875e05b857ef93f1ad61ea1e3324fc2 The World map of SME Server]<br />
| align=left valign=top cellspacing=0 cellpadding=0 style="background-color: #ffff99;" | '''Under Development:'''<br />
[[SME Server:9.0|SME Server 9 Release Candidate 1]] released on 12th May 2014.<br />
|- |<br />
|}<br />
{| width 100% cellpadding=5 cellspacing=0 <br />
|-<br />
| align=left valign=top rowspan="9"| <br />
{{Tip box|msg=A comparative test on SME Server by Distrowatch : [http://distrowatch.com/weekly.php?issue=20140106 DistroWatch Weekly, Issue 540, 6 January 2014]. Read more [[SME_Server:About#Product_Reviews|product reviews]]. The SME Server Development seen by [https://www.ohloh.net/p/SME_Server Ohloh]}}<br />
<br />
===Chris Burnat===<br />
<br />
[[File:ChrisBurnat.png|100|left]]<br />
<br />
It is with the deepest regret we have to inform you that on Wednesday 11th June Chris passed away. He was one of the most ardent supporters of Koozali SME and we all owe him an enormous debt of gratitude.<br />
<br />
We intend to dedicate the upcoming release of v9 to Chris. Without him it would be nowhere near ready.<br />
<br />
If you [[SME_Server:Download|download]] and [[SME_Server:Documentation|use it]], please remember him and his work, and that of all the other contributors who work tirelessly to make Koozali SME as good as it is.<br />
<br />
We extend our thoughts and deepest sympathies to his family. [http://forums.contribs.org/index.php/topic,50888.0.html Please go here] for further details<br />
<br />
Koozali Foundation Inc.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
===SME Server===<br />
Welcome to http://contribs.org, the home of the SME Server. We're here to provide collaborative documentation of the SME Server project. Please see [[Help:Contents#How_to_get_a_wiki_account.3F|'''how to get a wiki account''']] and read [[Help:Contents|'''the wiki help content'''.]]<br />
<br />
SME Server is a leading Open Source distribution for small and medium enterprises. It is a simple, powerful, secure Linux server for networking and communicating, used by thousands of individuals, companies and organizations all over the world. SME Server provides a friendly, free alternative to expensive proprietary software, standing apart from the competition by shipping with most common functionality preconfigured, and features a number of popular additional enhancements in the form of downloadable [[:Category:Contrib| Contributions]]. <br />
<br />
SME Server is built on [http://www.centos.org CentOS] using the publicly available open source [http://www.redhat.com Red Hat] Enterprise Linux sources. It's advantages include:<br />
* Simple to set up and use<br />
* Secure and stable to operate<br />
* Cross platform and extendible to meet future needs<br />
* Open source and Free to use<br />
<br />
SME Server provides the following standard functionality (See [[SME_Server:About|About SME Server]] for more detail):<br />
* Ease of Administration<br />
* File and print sharing<br />
* Sharing of a single Internet connection between multiple computers<br />
* A robust email server, which includes virus and spam filtering and webmail<br />
* A network firewall to protect against Internet intruders<br />
* Secure remote access<br />
* Directory services<br />
* Web application server, including support for Apache, MySQL, PHP and Python (LAMPP)<br />
* RAID and Backup<br />
* Automatic updates<br />
* Extendibility<br />
* Support for multiple languages<br />
* and much more ...<br />
all managed through an intuitive web interface<br />
<br />
The wiki menu bar at the left together with the links to the right provide comprehensive access to all the available Documentation for SME Server including details of the [[SME_Server:Community|Community]], [[SME_Server:Documentation|Server Manuals]] (including screenshots), [[SME_Server:Documentation:FAQ|FAQ]], [[:Category:Contrib|Contribs]] and [[:Category:Howto|How To's]]. There are also links for [[:SME_Server:Download|Downloads]], [http://bugs.contribs.org Bugzilla] to report any bugs, and the vibrant user community [http://forums.contribs.org Forums].<br />
<br />
Many individuals and corporations contribute to the ongoing development of SME Server, which is made available freely under the GNU General Public License. This license requires the public release of any modifications to the server, and allows these to be used to improve later versions.<br />
<br />
While SME Server is freely available under the GPL license, if you find SME Server useful we ask that you make a [[:Donate| Donation]] in order to help keep this project alive.<br />
====Support====<br />
Support for SME Server is via the [[SME_Server:Community|Community]] and it is highly recommended that you make yourself familiar with it and the [[SME_Server:Documentation|Documentation]] (read this at least twice) before diving in. You should also read the [[SME_Server:Advice|Advice]] for new and existing users.<br />
<br />
The three main methods of support available are:<br />
<br />
; [[:SME_Server:Documentation |Documentation]]:<br />
* The Wiki documentation is the primary source of information for SME Server. This should always be your first port of call when seeking help and support for SME Server<br />
* 'Google' is your friend (as well as all other internet search engines)<br />
<br />
; [http://bugs.contribs.org Bugzilla]:<br />
* If you do something and it doesn't 'just work', or it doesn't work as per the Wiki, raise a [http://bugs.contribs.org Bug]<br /><br />
* If you want to do, or are trying to do, something which is not ''standard'' SME or not in the Wiki, ask in the [http://forums.contribs.org Forums]<br />
* For more information on Bugzilla see the [[:Bugzilla Help]] page.<br />
{{Note box|The place of choice of the Developers to solve problems is [http://bugs.contribs.org Bugzilla], so don't be afraid to use it.<br />
}}<br />
<br />
; [http://forums.contribs.org Forums]:<br />
* Use the [http://forums.contribs.org Forums] if you want advice on how to do something not covered in the Wiki <br /><br />
* Post to the [http://forums.contribs.org Forums] if you found or did something, and you think other people might find it interesting or helpful to share <br /><br />
* If you don't know how to do something, or don't understand the Wiki, ask in the [http://forums.contribs.org Forums] <br /><br />
* If you report a problem in the forums, and it relates to how ''standard'' SME Server, a Contributed Add-on or Howto should work, you will more than likely be directed to raise it as a [http://bugs.contribs.org Bug] to be given structured advice and help you resolve it<br />
<br />
| width="30px" height="20px" align=right valign=top | <br />
| align=left valign=top |<br />
:<paypal></paypal><br />
:'''For Koozali SME Server'''<br />
====Documentation====<br />
|-<br />
| width="30px" height="60px" align=right valign=center | <br />
[[Image:Kdict.png | link=:SME_Server:Documentation | 48px ]]<br />
|'''[[:SME_Server:Documentation|Additional Documentation]]''' <br /><br />
[[SME_Server:Documentation| Documentation]] - The official Manual<br /><br />
[[:SME_Server:Documentation:FAQ|FAQ]] - Frequently Asked Questions <br /><br />
[[:Category:Howto|HowTo's]] - Specific Help, Instructions and Tutorials<br />
|-<br />
| width="30px" height="60px" align=right valign=center | <br />
[[Image:Blockdevice.png | link=:Category:Contrib | 48px ]]<br />
|'''[[:Category:Contrib|Contributions]]''' <br /><br />
[[:Category:Contrib|Contribs]] - SME Server Contributed add-on packages<br />
|-<br />
| width="30px" height="60px" align=right valign=center | <br />
[[Image:koozali-development.png | link=http://bugs.contribs.org/ | 48px ]]<br />
|'''[http://bugs.contribs.org/ Bugzilla ]'''<br /><br />
SME Server Development <br />
|-<br />
| width="30px" height="60px" align=right valign=center | <br />
[[Image:forum-contribs.png | link=http://forums.contribs.org/ | 48px ]]<br />
|'''[http://forums.contribs.org/ Forums ]'''<br /><br />
Meet People around the world<br /><br />
'''[http://forums.contribs.org/index.php?action=unread Unread posts]'''<br />
|-<br />
| width="30px" height="60px" align=right valign=center | <br />
[[Image:Kdict-new.png | link=:Category:Categorisation | 48px ]]<br />
|'''[[:Category:Categorisation| Categorised Contribs and Howto's]]''' <br /><br />
|-<br />
| width="30px" height="60px" align=right valign=center | <br />
[[Image:Kdict-new2.png | link=Category:Level | 48px ]]<br />
|'''Contribs and Howto's rated by Skill Level <br /><br />
[[:Category:Easy|Easy]] <br /><br />
[[:Category:Medium|Medium]] <br /><br />
[[:Category:Advanced|Advanced]] <br /><br />
[[:Category:Developer|Developer]]<br />
|-<br />
| width="30px" height="60px" align=right valign=center |<br />
[[Image:Help.png | link=Help:Contents | width=22px | height=22px ]]<br />
|'''Wiki Help''' <br /><br />
[[Help:Contents|Help]] with reading and editing this Wiki <br /><br />
[[Template:Languages| Language]] Template and Translation Help for this Wiki <br /><br />
[http://meta.wikimedia.org/wiki/Help:Contents#For_editors|Full MediaWiki Help] with editing MediaWiki's generally<br />
|-<br />
| width="30px" align=right valign=center | <br />
| valign=top |<br />
...and don't forget all the navigation links in the sidebar to the left.<br />
|}</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME8&diff=23459
Zarafa on SME8
2014-01-26T18:34:27Z
<p>Pfloor: </p>
<hr />
<div>{{Level|Developer}}<br />
{{Note box|<br />
'''This wiki page is specific to SME8 only.'''<br />
<br />
'''There is a separate wiki page on how to install Zarafa 7.x on SME7 [[Zarafa|Zarafa on SME 7]].'''<br />
<br />
'''There is a separate wiki page with a ''fully automated'' install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa on SME 9|Zarafa on SME 9]].'''<br />
}}<br />
<br />
<br />
*'''New zarafa-7.0.x- and z-push-install/upgradescripts for SME8'''<br> These new scipts always take the default NEW-config-files from the zarafa.rpms (found in /usr/share/doc/zarafa/example-config/) and make SME-templates of these default config-files ! So, you will always have the newest templated config-files, even after upgrading to a new Zarafa-version with altered config-files !<br> There is even more integration with the SME-perlDB too. (Most of the zarafa-config-keys can be set in the SME-perlDB !).<br> <br />
*You can find a upgrade-path to Z-push 2.0 (tested with Zarafa 7.0.12 and Z-push 2.0.7).<br><br />
*For version 1.3 of the Webapp you need minimum zarafa 7.0.12.<br />
<br />
_____________________<br />
<br />
*Placeholder for [[Zarafa quick install script]]<br />
<br />
<br />
== Maintainer ==<br />
Frederik POLLET : [mailto:frederik.pollet@pollet-ghys.be email]<br />
<br />
== Description ==<br />
*http://www.zarafa.com<br />
*http://z-push.sourceforge.net/soswp/<br />
<br />
Zarafa is a groupware-server which enables the sharing of mail, contacts, appointments, notes and tasks in a web-interface and/or Microsoft Outlook (or even other clients). It supports MAPI, POP3, IMAP, CalDAV/iCal. It can be used as a MS Exchange replacement, even featuring public folders. Connecting Microsoft Outlook with this groupware-server is simple, enabling most of the MS Exchange-functions.<br />
<br />
Z-push is an implementation of Microsoft's ActiveSync protocol which is used 'over-the-air' for multi platform active sync devices, including Windows Mobile and active sync used on Apple's iPhone, Sony Ericsson and Nokia phones. Open source Z-Push enables any PHP-based groupware package to become fully syncable with any ActiveSync-compliant device.<br />
<br />
== Making some decisions before installing : ==<br />
<br />
Zarafa can be configured with 3 different 'user-backends' :<br />
*database (db)<br />
*unix-users<br />
*LDAP/AD (not implemented in this howto)<br />
<br />
Using the '''db-plugin''' in the Zarafa-configuration, let you make your zarafa-users in the MySQL-zarafadatabase, with a separate user-password for every Zarafa-user and a store. So, you make your separated Zarafa-users and the stores for these Zarafa-users one by one in the Zarafa-MySQL-database with the '''zarafa-admin'''-tool and sripts in this howto. There is no syncronisation between the SME-user-passwords and the Zarafa-user-passwords. You can only enable maildelivery for a SME/unix-user to a Zarafa-user <u>with the same logon-name</u>.<br><br />
<br />
When using the '''unix-plugin''' in the Zarafa-configuration, Zarafa makes a store for every SME/unix-user on your system, except for those who are excluded by the template used in this howto. Zarafa uses the passwords of the SME/unix-users. There are no separated Zarafa-users and no separated passwords. You can enable maildelivery for a SME/unix-user to Zarafa. Since the unix files do not contain enough information for Zarafa, there are some properties of a user that will be stored in the MySQL-zarafadatabase. These properties are the email address, overriding quota settings, and administrator settings. The '''zarafa-admin'''-tool has to be used to update these user properties. All other user-properties are done using the normal unix tools. '''The unix-plugin seems to be your best choice if all your SME-users will use Zarafa Webaccess/Microsoft Outlook, and you don't need a multicompany-environment'''.<br><br />
<br />
[http://doc.zarafa.com/7.0/Administrator_Manual/en-US/html-single/index.html#_user_authentication MORE INFORMATION]<br />
<br />
In a multicompany-evironment every company has his own Global Adressbook and public folders.<br />
{{Warning box|A multicompany-evironment is only possible with the DB-plugin.<br>}}<br />
{{Warning box|IMPORTANT : If you want to have a multicompany-environment, <u>format of the SME/unix-username and the ZARAFA-username has to be [username].[companyname]</u> !!!<br>}}<br />
<br />
== INSTALLATION of VERSION 7.0.x ==<br />
=== Search latest php53-mapi.rpm ===<br />
<br />
SME8 uses PHP5.3<br><br />
Unfortunately, PHP 5.1 and PHP 5.3 are ABI incompatible, that means that PHP modules that were compiled for PHP 5.1 (like the php-mapi.rpm compiled in the Zarafa-rpms for RHEL 5) can not be run using PHP 5.3 :<br><br />
<br />
https://community.zarafa.com/pg/blog/read/1837/support-for-php-53-in-rhel-5-via-new-php53mapi-rpm-package<br />
<br />
So, search on the EPEL-repositories <u>'''the latest''' php53-mapi-package</u>.<br />
<br />
https://admin.fedoraproject.org/updates/search/php53-mapi?<br />
<br />
=== Set the epel-repository (incl. epel-testing) :===<br />
<br />
/sbin/e-smith/db yum_repositories set epel repository \<br />
Name 'Epel - EL5' \<br />
BaseUrl 'http://download.fedoraproject.org/pub/epel/5/$basearch' \<br />
MirrorList 'http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch' \<br />
EnableGroups no \<br />
GPGCheck yes \<br />
GPGKey http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL \<br />
Visible no \<br />
status disabled <br />
<br />
/sbin/e-smith/db yum_repositories set epel-testing repository \<br />
Name 'Epel-testing - EL5' \<br />
BaseUrl 'http://download.fedoraproject.org/pub/epel/testing/5/$basearch' \<br />
MirrorList 'http://mirrors.fedoraproject.org/mirrorlist?repo=testing-epel5&arch=$basearch' \<br />
EnableGroups no \<br />
GPGCheck yes \<br />
GPGKey http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL \<br />
Visible no \<br />
status disabled <br />
<br />
signal-event yum-modify<br />
<br />
=== Download via the Zarafawebsite the package for ZCP <u>''corresponding'' with the php53-mapi.rpm (cf. version above !!)</u> ===<br />
<br />
Make an installdirectory (ex. : /root/InstallZarafa)<br />
<br />
mkdir -p /root/InstallZarafa<br />
<br />
Go (cd /...) to the installdirectory (ex. : /root/InstallZarafa) : <br />
<br />
cd /to the installdirectory<br />
<br />
ex.: <br />
<br />
cd /root/InstallZarafa<br />
<br />
wget http://download.zarafa.com/community/final/7.0/[version]/zcp-[version]-rhel-5-[cpu-arch]-free.tar.gz<br />
<br />
The 'free'-version has the ability to connect with Microsoft Outlook (default 3 users for free, buy zarafa-CAL's if you want more).<br />
<br />
=== Unpack the corresponding package for ZCP :===<br />
<br />
tar -zxvf zcp-*<br />
<br />
=== Remove the devel packages ===<br />
Go (cd ./zcp-...) to the created subdirectory (zcp-...) :<br />
<br />
cd ./zcp- ... <br />
rm -f *-dev*.rpm<br />
<br />
Move the windows-directory to an installshare in your network<br />
<br />
=== Download the latest webapp.rpm too in the same subdirectory :===<br />
<br />
wget http://download.zarafa.com/community/final/WebApp/[version]/rhel/[zarafa-webapp-version.noarch.rpm]<br />
<br />
=== Install all rpm's in the unpacked package of ZCP and the webapp.rpm too :===<br />
<br />
yum localinstall *.rpm<br />
<br />
All packages have dependencies that cannot be resolved if you install only part of the rpm's.<br />
<br />
=== Remove the default php-mapi.rpm ===<br />
<br />
We have to remove the installation of the default php-mapi (because it's not built for php 5.3).<br />
<br />
rpm -e php-mapi --nodeps<br />
<br />
=== Install the php53-mapi.rpm ===<br />
-If you downloaded the rpm :<br />
<br />
rpm -Uvh --force php53-mapi<br />
<br />
-If you did set the EPEL-repository :<br />
<br />
yum install php53-mapi --enablerepo=epel --enablerepo=epel-testing<br />
<br />
=== Make install/update-actions ===<br />
==== INSTALLSCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/zarafa-install =====<br />
<br />
<nowiki><br />
#!/usr/bin/env bash<br />
clear<br />
<br />
if [ `whoami` != "root" ]; then<br />
echo "This installation must be run as user root."<br />
echo "Become root, and run this script again."<br />
echo<br />
exit 1<br />
fi<br />
<br />
##########################################<br />
# Creating some Zarafa-actions<br />
##########################################<br />
<br />
#<br />
#--- zarafa-expand-templates ---<br />
#<br />
echo<br />
echo "Creating zarafa-expand-templates-action ..."<br />
echo<br />
cat <<HERE1 > /etc/e-smith/events/actions/zarafa-expand-templates<br />
#!/bin/sh<br />
/sbin/e-smith/expand-template /etc/zarafa/gateway.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/ical.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/server.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/unix.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/monitor.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/indexer.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/spooler.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/dagent.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/licensed.cfg<br />
/etc/e-smith/events/actions/qmail-update-user<br />
HERE1<br />
<br />
<br />
#<br />
#--- zarafa-services ---<br />
#<br />
echo<br />
echo "Creating zarafa-services-action ..."<br />
echo<br />
cat <<HERE2 > /etc/e-smith/events/actions/zarafa-services<br />
#!/bin/sh<br />
FILE=/etc/rc.d/init.d/zarafa-licensed<br />
if [ "\$1" == start ]; then<br />
/etc/rc.d/init.d/zarafa-dagent start<br />
/etc/rc.d/init.d/zarafa-gateway start<br />
/etc/rc.d/init.d/zarafa-ical start<br />
if [ -a \$FILE ]; then \$FILE start; fi<br />
/etc/rc.d/init.d/zarafa-monitor start<br />
/etc/rc.d/init.d/zarafa-spooler start<br />
/etc/rc.d/init.d/zarafa-indexer start<br />
/etc/rc.d/init.d/zarafa-server start<br />
exit 0<br />
fi<br />
if [ "\$1" == stop ]; then<br />
/etc/rc.d/init.d/zarafa-dagent stop<br />
/etc/rc.d/init.d/zarafa-gateway stop<br />
/etc/rc.d/init.d/zarafa-ical stop<br />
if [ -a \$FILE ]; then \$FILE stop; fi<br />
/etc/rc.d/init.d/zarafa-indexer stop<br />
/etc/rc.d/init.d/zarafa-spooler stop<br />
/etc/rc.d/init.d/zarafa-server stop<br />
/etc/rc.d/init.d/zarafa-monitor stop <br />
exit 0<br />
fi<br />
if [ "\$1" == restart ]; then<br />
/etc/rc.d/init.d/zarafa-dagent stop<br />
/etc/rc.d/init.d/zarafa-gateway stop<br />
/etc/rc.d/init.d/zarafa-ical stop<br />
if [ -a \$FILE ]; then \$FILE stop; fi<br />
/etc/rc.d/init.d/zarafa-monitor stop<br />
/etc/rc.d/init.d/zarafa-indexer stop<br />
/etc/rc.d/init.d/zarafa-spooler stop<br />
/etc/rc.d/init.d/zarafa-server stop<br />
/etc/rc.d/init.d/zarafa-dagent start<br />
/etc/rc.d/init.d/zarafa-gateway start<br />
/etc/rc.d/init.d/zarafa-ical start<br />
if [ -a \$FILE ]; then \$FILE start; fi<br />
/etc/rc.d/init.d/zarafa-monitor start<br />
/etc/rc.d/init.d/zarafa-server start<br />
/etc/rc.d/init.d/zarafa-spooler start<br />
/etc/rc.d/init.d/zarafa-indexer start<br />
exit 0<br />
fi<br />
if [ "\$1" == enabled ]; then<br />
config setprop zarafa-gateway status enabled<br />
config setprop zarafa-ical status enabled<br />
if [ -a \$FILE ]; then config setprop zarafa-licensed status enabled; fi<br />
config setprop zarafa-monitor status enabled<br />
config setprop zarafa-server status enabled<br />
config setprop zarafa-spooler status enabled<br />
config setprop zarafa-indexer status enabled<br />
config setprop zarafa-dagent status enabled<br />
exit 0<br />
fi<br />
if [ "\$1" == disabled ]; then<br />
config setprop zarafa-gateway status disabled<br />
config setprop zarafa-ical status disabled<br />
if [ -a \$FILE ]; then config setprop zarafa-licensed status disabled; fi<br />
config setprop zarafa-monitor status disabled<br />
config setprop zarafa-server status disabled<br />
config setprop zarafa-spooler status disabled<br />
config setprop zarafa-indexer status disabled<br />
config setprop zarafa-dagent status disabled<br />
exit 0<br />
fi<br />
echo "Usage: start|stop|restart|enabled|disabled"<br />
exit 0<br />
HERE2<br />
<br />
<br />
#<br />
#--- zarafa-create-user-action ---<br />
#<br />
echo<br />
echo "Creating zarafa-create-user-action ..."<br />
echo<br />
cat <<HERE3 > /etc/e-smith/events/actions/zarafa-create-user<br />
#!/bin/sh<br />
clear<br />
/bin/echo "Enter the username of the ZARAFA-user"<br />
/bin/echo "If you have a multicompany-setup, format of the SME-username and the ZARAFA-username"<br />
/bin/echo "has to be [username].[companyname] !!!"<br />
read USERNAME<br />
/bin/echo "Enter password:"<br />
read PASSWORD<br />
/bin/echo "Enter e-mail address:"<br />
read EMAIL<br />
/bin/echo "Enter full name:"<br />
read FULLNAME<br />
/bin/echo "Executing..."<br />
/usr/bin/zarafa-admin -c "\$USERNAME" -p "\$PASSWORD" -e "\$EMAIL" -f "\$FULLNAME"<br />
/usr/bin/zarafa-admin -l<br />
/sbin/e-smith/db accounts setprop \$USERNAME zarafa enabled <br />
/etc/e-smith/events/actions/qmail-update-user<br />
HERE3<br />
<br />
<br />
#<br />
#--- zarafa-create-company-action ---<br />
#<br />
echo<br />
echo "Creating zarafa-create-company-action ..."<br />
echo<br />
cat <<HERE4 > /etc/e-smith/events/actions/zarafa-create-company<br />
#!/bin/sh<br />
clear<br />
/bin/echo "Enter the companyname :"<br />
read COMPANYNAME<br />
/bin/echo "Executing..."<br />
/usr/bin/zarafa-admin --create-company "\$COMPANYNAME"<br />
HERE4<br />
<br />
<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-expand-templates<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-services<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-create-user<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-create-company<br />
<br />
#<br />
#--- zarafa-configuration-helper-action ---<br />
#<br />
echo<br />
echo "Creating zarafa-configuration-helper-action ..."<br />
echo<br />
cat <<HERE5 > /etc/e-smith/events/actions/helpers.inc<br />
# -*- Mode: sh -*-<br />
replace() {<br />
file=\$1<br />
option=\$2<br />
value=\$3<br />
<br />
# escape &-signs, and % for sed<br />
value=\`echo \$value | sed -e 's/\&/\\\\\&/g' -e 's/\%/\\\\\%/g'\`<br />
sed -i -e "s%\([[:space:]]*\$option[[:space:]]*=[[:space:]]*\).*%\1\$value%" \$file<br />
<br />
}<br />
HERE5<br />
<br />
. /etc/e-smith/events/actions/helpers.inc<br />
<br />
##########################################<br />
# Creating zarafa-db-creation-templates<br />
##########################################<br />
<br />
#<br />
#--- /etc/e-smith/db/configuration/migrate/80zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/db/configuration/migrate/80zarafa ..."<br />
echo<br />
cat <<HERE6 > /etc/e-smith/db/configuration/migrate/80zarafa<br />
{<br />
use MIME::Base64 qw(encode_base64);<br />
<br />
my \$rec = \$DB->get('zarafa-server') || \$DB->new_record('zarafa-server', {type => 'service'});<br />
<br />
my \$pw = \$rec->prop('DbPassword');<br />
return "" if \$pw;<br />
<br />
\$rec->set_prop('DbPassword', sprintf("%15.0f", int( (1000000000000000) * rand() )));<br />
}<br />
HERE6<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/e-smith/sql/init/80zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/e-smith/sql/init/80zarafa ..."<br />
echo<br />
cat <<HERE7 > /etc/e-smith/templates/etc/e-smith/sql/init/80zarafa<br />
{<br />
my \$db = \${'zarafa-server'}{DbName} || 'zarafa';<br />
my \$user = \${'zarafa-server'}{DbUser} || 'zarafa';<br />
my \$pass = \${'zarafa-server'}{DbPassword} || 'changeme';<br />
\$OUT .= <<END<br />
#! /bin/sh<br />
if [ -d /var/lib/mysql/\$db ]; then<br />
exit<br />
fi<br />
/usr/bin/mysql <<EOF<br />
CREATE DATABASE \$db DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
use \$db;<br />
<br />
use mysql;<br />
GRANT ALL PRIVILEGES ON \$db.* TO \$user\@localhost<br />
IDENTIFIED BY '\$pass';<br />
flush privileges;<br />
EOF<br />
END<br />
}<br />
HERE7<br />
<br />
#<br />
#--- /etc/e-smith/templates.metadata/etc/e-smith/sql/init/80zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates.metadata/etc/e-smith/sql/init/80zarafa ..."<br />
echo<br />
cat <<HERE8 > /etc/e-smith/templates.metadata/etc/e-smith/sql/init/80zarafa<br />
PERMS=0750<br />
HERE8<br />
<br />
##########################################<br />
# Creating SME-HTTPD-templates<br />
##########################################<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ..."<br />
echo<br />
cat <<HERE9 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases<br />
{<br />
# vim: ft=perl:<br />
<br />
\$haveSSL = (exists \${modSSL}{status} and \${modSSL}{status} eq "enabled") ? 'yes' : 'no';<br />
my \$zwebmailStatus = \$zarafa{'status'} || "disabled";<br />
my \$zwebmailAccessType = \$zarafa{'access'} || "SSL";<br />
<br />
my \$dirs;<br />
\$dirs{zarafa} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webaccess} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webmail} = '/usr/share/zarafa-webaccess';<br />
if (\$imp{'status'} eq 'enabled') {\$dirs{webmail} = ''};<br />
\$dirs{webapp} = '/usr/share/zarafa-webapp';<br />
<br />
return " # Zarafa is disabled in this VirtualHost\n"<br />
unless \$zwebmailStatus eq 'enabled';<br />
<br />
foreach \$place ('zarafa','webmail','webaccess','webapp')<br />
{<br />
if ((\$port eq "80") && (\$haveSSL eq 'yes') && (\$zwebmailAccessType eq 'SSL'))<br />
{<br />
\$OUT .= " RewriteRule ^/\$place(/.*|\\$) https://%{HTTP_HOST}/\$place\\\$1 [L,R]\n";<br />
} else {<br />
if ((\$dirs{\$place}) ne '') {\$OUT .= " Alias /\$place \$dirs{\$place}\n"};<br />
}<br />
} <br />
}<br />
HERE9<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ..."<br />
echo<br />
cat <<HERE10 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias<br />
{<br />
my \$zstatus = \$zarafa{'status'};<br />
<br />
if (defined \$zstatus && \$zstatus eq 'enabled')<br />
{<br />
\$OUT .= qq(<br />
#--------------------------------------------------------------------<br />
# Zarafa specific configuration files.<br />
#--------------------------------------------------------------------<br />
<br />
Alias /zarafa /usr/share/zarafa-webaccess/<br />
<Directory /usr/share/zarafa-webaccess/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
Alias /webapp /usr/share/zarafa-webapp/<br />
<Directory /usr/share/zarafa-webapp/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
);<br />
} <br />
else<br />
{<br />
\$OUT .= "# Zarafa Webmail is not configured as it is disabled in the config db";<br />
}<br />
}<br />
HERE10<br />
<br />
##########################################<br />
# Creating SME-QMAIL-user-templates<br />
##########################################<br />
<br />
#<br />
#--- /etc/e-smith/templates-user/.qmail/80Zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates-user/.qmail/80Zarafa ..."<br />
echo<br />
cat <<HERE11 > /etc/e-smith/templates-user/.qmail/80Zarafa<br />
{<br />
my \$zarafa = \$user->prop('zarafa') || 'disabled';<br />
my \$zarafa2 = \${'zarafa-server'}{GlobalForward} || 'disabled';<br />
<br />
if (\$zarafa eq 'enabled' || \$zarafa2 eq 'enabled')<br />
{ return "| /usr/bin/zarafa-dagent -q \$USERNAME ; if [ \\$\\? -ne 0 ] ; then exit -1; else exit 99; fi;"<br />
}<br />
}<br />
HERE11<br />
<br />
#<br />
#--- /etc/e-smith/templates-user/.qmail-junkmail/01Zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates-user/.qmail-junkmail/01Zarafa ..."<br />
echo<br />
cat <<HERE12 > /etc/e-smith/templates-user/.qmail-junkmail/01Zarafa<br />
{<br />
# vim: ft=perl:<br />
die "USERNAME not set." unless defined (\$USERNAME);<br />
<br />
use esmith::AccountsDB;<br />
\$adb = esmith::AccountsDB->open_ro or die "Couldn't open AccountsDB";<br />
<br />
\$user = \$adb->get(\$USERNAME) or die "No user \$USERNAME in AccountsDB";<br />
<br />
my \$zarafa = \$user->prop('zarafa') || 'disabled';<br />
my \$zarafa2 = \${'zarafa-server'}{GlobalForward} || 'disabled';<br />
return "| /usr/bin/zarafa-dagent -qj \$USERNAME ; if [ \\$\\? -ne 0 ] ; then exit -1; else exit 99; fi;"<br />
if (\$zarafa eq 'enabled' || \$zarafa2 eq 'enabled');<br />
}<br />
HERE12<br />
<br />
<br />
##########################################<br />
# Creating Zarafa-configuration-templates<br />
##########################################<br />
<br />
#<br />
#--- unix config ---<br />
#<br />
echo<br />
echo "Creating zarafa-unix-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/unix.cfg<br />
cat <<HERE13 > /etc/e-smith/templates/etc/zarafa/unix.cfg/unix.cfg<br />
{<br />
use esmith::AccountsDB<br />
}<br />
##############################################################<br />
# UNIX USER PLUGIN SETTINGS<br />
#<br />
# Any of these directives that are required, are only required if the<br />
# userplugin parameter is set to unix.<br />
<br />
# Charset used in /etc/passwd for the fullname of a user. Normally this<br />
# is us-ascii, but this can differ according to your setup.<br />
# The charset specified here must be supported by your iconv(1)<br />
# setup. See iconv -l for all charsets.<br />
fullname_charset = iso-8859-15<br />
<br />
# Default email domain for constructing new users<br />
# Required, no default<br />
default_domain = { \${'zarafa-server'}{DomainName} || \$DomainName; }<br />
<br />
# The lowest user id that is considered a regular user<br />
# Optional, default = 1000<br />
min_user_uid = 101<br />
<br />
# The highest user id that is considered a regular user<br />
# Optional, default = 10000<br />
max_user_uid = 10000<br />
<br />
# A list of user ids that are not considered to be regular users<br />
# Optional, default = empty<br />
# except_user_uids =<br />
except_user_uids = {<br />
\$accounts = esmith::AccountsDB->open_ro or die "Could not open AccountsDB";<br />
{<br />
while ((\$name, \$passwd, \$uid, \$gid, \$quota,<br />
\$comment, \$gcos, \$dir, \$shell) = getpwent())<br />
{<br />
\$user = \$accounts->get(\$name);<br />
<br />
\$OUT .= "\$uid "<br />
unless \$uid <= 101 or (defined \$user and \$user->prop('type') eq "user");<br />
}<br />
}<br />
}<br />
<br />
# The lowest group id that is considered a regular group<br />
# Optional, default = 1000<br />
min_group_gid = 5000<br />
<br />
# The highest group id that is considered a regular group<br />
# Optional, default = 10000<br />
max_group_gid = 10000<br />
<br />
# A list of group ids that are not considered to be regular groups<br />
# Optional, default = empty<br />
# except_group_gids =<br />
except_group_gids = {<br />
setpwent();<br />
while ((\$name, \$passwd, \$uid, \$gid, \$quota,<br />
\$comment, \$gcos, \$dir, \$shell) = getpwent())<br />
{<br />
\$group = \$accounts->get(\$name);<br />
<br />
\$OUT .= "\$gid "<br />
unless \$gid < 5000 or (defined \$group and \$group->prop('type') eq "group");<br />
}<br />
endpwent();<br />
}<br />
<br />
# Create a user as non-active when it has this unix shell<br />
non_login_shell = /bin/false<br />
HERE13<br />
<br />
<br />
#<br />
#--- sysconfig config ---<br />
#<br />
echo<br />
echo "Creating zarafa-sysconfig-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/sysconfig/zarafa<br />
cat /etc/sysconfig/zarafa | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa<br />
replace /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa ZARAFA_LOCALE '"{ ${'\''zarafa'\''}{language} || '\''en_US.UTF-8'\'' ; }"'<br />
replace /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa ZARAFA_USERSCRIPT_LOCALE '"{ ${'\''zarafa'\''}{language} || '\''en_US.UTF-8'\'' ; }"'<br />
<br />
<br />
#<br />
#--- licensed config ---<br />
#<br />
echo<br />
echo "Creating zarafa-licensed-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/licensed.cfg<br />
cat /usr/share/doc/zarafa-licensed/example-config/licensed.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_method '{ ${'\''zarafa-licensed'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_level '{ ${'\''zarafa-licensed'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_timestamp '{ ${'\''zarafa-licensed'\''}{log_timestamp} || '\''1'\''; }'<br />
<br />
#<br />
#--- server config ---<br />
#<br />
echo<br />
echo "Creating zarafa-server-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/server.cfg<br />
cat /usr/share/doc/zarafa/example-config/server.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_tcp_enabled '{ ${'\''zarafa-server'\''}{server_tcp_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_tcp_port '{ ${'\''zarafa-server'\''}{TCPPort} || '\''236'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_pipe_enabled '{ ${'\''zarafa-server'\''}{server_pipe_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_name '{ ${'\''zarafa-server'\''}{server_name} || '\''Zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg database_engine '{ ${'\''zarafa-server'\''}{database_engine} || '\''mysql'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg allow_local_users '{ ${'\''zarafa-server'\''}{allow_local_users} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg local_admin_users '{ ${'\''zarafa-server'\''}{local_admin_users} || '\''root'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg system_email_address '{ ${'\''zarafa-server'\''}{system_email_address} || '\''postmaster@localhost'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg session_timeout '{ ${'\''zarafa-server'\''}{session_timeout} || '\''300'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg license_timeout '{ ${'\''zarafa-server'\''}{license_timeout} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_method '{ ${'\''zarafa-server'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_level '{ ${'\''zarafa-server'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_timestamp '{ ${'\''zarafa-server'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_enabled '{ ${'\''zarafa-server'\''}{audit_log_enabled} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_level '{ ${'\''zarafa-server'\''}{audit_log_level} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_timestamp '{ ${'\''zarafa-server'\''}{audit_log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_host '{ ${'\''zarafa-server'\''}{mysql_host} || '\''localhost'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_port '{ ${'\''zarafa-server'\''}{mysql_port} || '\''3306'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_user '{ ${'\''zarafa-server'\''}{DbUser} || '\''zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_password '{ ${'\''zarafa-server'\''}{DbPassword}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_database '{ ${'\''zarafa-server'\''}{DbName} || '\''zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_storage '{ ${'\''zarafa-server'\''}{attachment_storage} || '\''files'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_path '/home/e-smith/files/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_compression '{ ${'\''zarafa-server'\''}{attachment_compression} || '\''6'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_enabled '{ ${'\''zarafa-ssl'\''}{server_ssl_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_port '{ ${'\''zarafa-ssl'\''}{TCPPort} || '\''237'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_key_file '/home/e-smith/ssl.pem/{$SystemName}.{$DomainName}.pem'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_key_pass '{ ${'\''zarafa-server'\''}{DbPassword}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_ca_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_ca_path '/home/e-smith/ssl.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sslkeys_path '/home/e-smith/ssl.pem'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg threads '{ ${'\''zarafa-server'\''}{threads} || '\''8'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg watchdog_frequency '{ ${'\''zarafa-server'\''}{watchdog_frequency} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg watchdog_max_age '{ ${'\''zarafa-server'\''}{watchdog_max_age} || '\''500'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_max_keep_alive_requests '{ ${'\''zarafa-server'\''}{server_max_keep_alive_requests} || '\''100'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_recv_timeout '{ ${'\''zarafa-server'\''}{server_recv_timeout} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_read_timeout '{ ${'\''zarafa-server'\''}{server_read_timeout} || '\''60'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_send_timeout '{ ${'\''zarafa-server'\''}{server_send_timeout} || '\''60'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg softdelete_lifetime '{ ${'\''zarafa-server'\''}{softdelete_lifetime} || '\''30'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_lifetime '{ ${'\''zarafa-server'\''}{sync_lifetime} || '\''365'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_log_all_changes '{ ${'\''zarafa-server'\''}{sync_log_all_changes} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_sso '{ ${'\''zarafa-server'\''}{enable_sso} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_gab '{ ${'\''zarafa-server'\''}{enable_gab} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg auth_method '{ ${'\''zarafa-server'\''}{auth_method} || '\''plugin'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg pam_service '{ ${'\''zarafa-server'\''}{pam_service} || '\''passwd'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_cell_size '{ ${'\''zarafa-server'\''}{cache_cell_size} || '\''268435456'\''; }' <br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_object_size '{ ${'\''zarafa-server'\''}{cache_object_size} || '\''5242880'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_indexedobject_size '{ ${'\''zarafa-server'\''}{cache_indexedobject_size} || '\''16777216'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_quota_size '{ ${'\''zarafa-server'\''}{cache_quota_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_quota_lifetime '{ ${'\''zarafa-server'\''}{cache_quota_lifetime} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_acl_size '{ ${'\''zarafa-server'\''}{cache_acl_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_store_size '{ ${'\''zarafa-server'\''}{cache_store_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_user_size '{ ${'\''zarafa-server'\''}{cache_user_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_userdetails_size '{ ${'\''zarafa-server'\''}{cache_userdetails_size} || '\''26214400'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_userdetails_lifetime '{ ${'\''zarafa-server'\''}{cache_userdetails_lifetime} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_server_size '{ ${'\''zarafa-server'\''}{cache_server_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_server_lifetime '{ ${'\''zarafa-server'\''}{cache_server_lifetime} || '\''30'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_warn '{ ${'\''zarafa-server'\''}{quota_warn} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_soft '{ ${'\''zarafa-server'\''}{quota_soft} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_hard '{ ${'\''zarafa-server'\''}{quota_hard} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg companyquota_warn '{ ${'\''zarafa-server'\''}{companyquota_warn} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_plugin '{ ${'\''zarafa-server'\''}{user_plugin} || '\''db'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_plugin_config '{ ${'\''zarafa-server'\''}{user_plugin_config}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_safe_mode '{ ${'\''zarafa-server'\''}{user_safe_mode} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg thread_stacksize '{ ${'\''zarafa-server'\''}{thread_stacksize} || '\''512'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_hosted_zarafa '{ ${'\''zarafa-server'\''}{enable_hosted_zarafa} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_distributed_zarafa '{ ${'\''zarafa-server'\''}{enable_distributed_zarafa} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg storename_format '{ ${'\''zarafa-server'\''}{storename_format} || '\''%f'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg loginname_format '{ ${'\''zarafa-server'\''}{loginname_format} || '\''%u'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_enabled '{ ${'\''zarafa-server'\''}{client_update_enabled} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_path '{ ${'\''zarafa-server'\''}{client_update_path} || '\''/var/lib/zarafa/client'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_log_level '{ ${'\''zarafa-server'\''}{client_update_log_level} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg hide_everyone '{ ${'\''zarafa-server'\''}{hide_everyone} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg hide_system '{ ${'\''zarafa-server'\''}{hide_system} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_enabled '{ ${'\''zarafa-server'\''}{index_services_enabled} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_search_timeout '{ ${'\''zarafa-server'\''}{index_services_search_timeout} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_prefix_chars '{ ${'\''zarafa-server'\''}{index_services_prefix_chars} || '\''3'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_enhanced_ics '{ ${'\''zarafa-server'\''}{enable_enhanced_ics} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_gab_realtime '{ ${'\''zarafa-server'\''}{sync_gab_realtime} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg disabled_features '{ ${'\''zarafa-server'\''}{disabled_features}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg max_deferred_records '{ ${'\''zarafa-server'\''}{max_deferred_records} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg max_deferred_records_folder '{ ${'\''zarafa-server'\''}{max_deferred_records_folder} || '\''20'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg coredump_enabled '{ ${'\''zarafa-server'\''}{coredump_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_enable_v2 '{ ${'\''zarafa-server'\''}{server_ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- dagent config ---<br />
#<br />
echo<br />
echo "Creating zarafa-dagent-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/dagent.cfg<br />
cat /usr/share/doc/zarafa-dagent/example-config/dagent.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_method '{ ${'\''zarafa-dagent'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_level '{ ${'\''zarafa-dagent'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_timestamp '{ ${'\''zarafa-dagent'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_raw_message '{ ${'\''zarafa-dagent'\''}{log_raw_message} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg lmtp_port '{ ${'\''zarafa-dagent'\''}{lmtp_port} || '\''2003'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg lmtp_max_threads '{ ${'\''zarafa-dagent'\''}{lmtp_max_threads} || '\''20'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg process_model '{ ${'\''zarafa-dagent'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg spam_header_name '{ ${'\''zarafa-dagent'\''}{spam_header_name} || '\''X-Spam-Status'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg spam_header_value '{ ${'\''zarafa-dagent'\''}{spam_header_value} || '\''Yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg archive_on_delivery '{ ${'\''zarafa-dagent'\''}{archive_on_delivery} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg set_rule_headers '{ ${'\''zarafa-dagent'\''}{set_rule_headers} || '\''yes'\''; }'<br />
<br />
<br />
#<br />
#--- spooler config ---<br />
#<br />
echo<br />
echo "Creating zarafa-spooler-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/spooler.cfg<br />
cat /usr/share/doc/zarafa-spooler/example-config/spooler.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg smtp_port '{ ${'\''zarafa-spooler'\''}{smtp_port} || '\''25'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_method '{ ${'\''zarafa-spooler'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_level '{ ${'\''zarafa-spooler'\''}{log_level} || '\''3'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_timestamp '{ ${'\''zarafa-spooler'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg max_threads '{ ${'\''zarafa-spooler'\''}{max_threads} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg fax_domain '{ ${'\''zarafa-spooler'\''}{fax_domain} || '\''fax.local'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg fax_international '{ ${'\''zarafa-spooler'\''}{fax_international} || '\''00'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_delegates '{ ${'\''zarafa-spooler'\''}{always_send_delegates} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_redirect_spoofing '{ ${'\''zarafa-spooler'\''}{allow_redirect_spoofing} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg copy_delegate_mails '{ ${'\''zarafa-spooler'\''}{copy_delegate_mails} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_delegate_meeting_request '{ ${'\''zarafa-spooler'\''}{allow_delegate_meeting_request} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_send_to_everyone '{ ${'\''zarafa-spooler'\''}{allow_send_to_everyone} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_tnef '{ ${'\''zarafa-spooler'\''}{always_send_tnef} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_utf8 '{ ${'\''zarafa-spooler'\''}{always_send_utf8} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg charset_upgrade '{ ${'\''zarafa-spooler'\''}{charset_upgrade} || '\''windows-1252'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg expand_groups '{ ${'\''zarafa-spooler'\''}{expand_groups} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg archive_on_send '{ ${'\''zarafa-spooler'\''}{archive_on_send} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- monitor config ---<br />
#<br />
echo<br />
echo "Creating zarafa-monitor-configuration-template ..."<br />
echo "The monitor program sends quota warning mails to users who are over quota."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/monitor.cfg<br />
cat /usr/share/doc/zarafa-monitor/example-config/monitor.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_method '{ ${'\''zarafa-monitor'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_level '{ ${'\''zarafa-monitor'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_timestamp '{ ${'\''zarafa-monitor'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg quota_check_interval '{ ${'\''zarafa-monitor'\''}{quota_check_interval} || '\''15'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg mailquota_resend_interval '{ ${'\''zarafa-monitor'\''}{mailquota_resend_interval} || '\''1'\''; }'<br />
<br />
<br />
#<br />
#--- gateway config ---<br />
#<br />
echo<br />
echo "Creating zarafa-gateway-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/gateway.cfg<br />
cat /usr/share/doc/zarafa-gateway/example-config/gateway.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg server_socket 'http://localhost:{${'\''zarafa-server'\''}{TCPPort}||'\''236'\'';}/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3_enable '{ if (${'\''zarafa-pop3'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3_port '{ ${'\''zarafa-pop3'\''}{TCPPort} || '\''8110'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3s_enable '{ if (${'\''zarafa-pop3s'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3s_port '{ ${'\''zarafa-pop3s'\''}{TCPPort} || '\''8995'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_enable '{ if (${'\''zarafa-imap'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_port '{ ${'\''zarafa-imap'\''}{TCPPort} || '\''8143'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imaps_enable '{ if (${'\''zarafa-imaps'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imaps_port '{ ${'\''zarafa-imaps'\''}{TCPPort} || '\''8993'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_only_mailfolders '{ ${'\''zarafa-imap'\''}{imap_only_mailfolders} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_public_folders '{ ${'\''zarafa-imap'\''}{imap_public_folders} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_capability_idle '{ ${'\''zarafa-imap'\''}{imap_capability_idle} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_max_messagesize '{ ${'\''zarafa-imap'\''}{imap_max_messagesize} || '\''134217728'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_generate_utf8 '{ ${'\''zarafa-imap'\''}{imap_generate_utf8} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_expunge_on_delete '{ ${'\''zarafa-imap'\''}{imap_expunge_on_delete} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_store_rfc822 '{ ${'\''zarafa-imap'\''}{imap_store_rfc822} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_private_key_file '/home/e-smith/ssl.key/{$SystemName}.{$DomainName}.key'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_certificate_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_verify_client '{ ${'\''zarafa-gateway'\''}{ssl_verify_client} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg process_model '{ ${'\''zarafa-gateway'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_method '{ ${'\''zarafa-gateway'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_level '{ ${'\''zarafa-gateway'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_timestamp '{ ${'\''zarafa-gateway'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_enable_v2 '{ ${'\''zarafa-gateway'\''}{ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- ical config ---<br />
#<br />
echo<br />
echo "Creating zarafa-ical-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/ical.cfg<br />
cat /usr/share/doc/zarafa-ical/example-config/ical.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ical_enable '{ if (${'\''zarafa-ical'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ical_port '{ ${'\''zarafa-ical'\''}{TCPPort} || '\''8088'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg icals_enable '{ if (${'\''zarafa-icals'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg icals_port '{ ${'\''zarafa-icals'\''}{TCPPort} || '\''8089'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg server_socket 'http://localhost:{${'\''zarafa-server'\''}{TCPPort}||'\''236'\'';}/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg process_model '{ ${'\''zarafa-ical'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_method '{ ${'\''zarafa-ical'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_level '{ ${'\''zarafa-ical'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_timestamp '{ ${'\''zarafa-ical'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_private_key_file '/home/e-smith/ssl.key/{$SystemName}.{$DomainName}.key'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_certificate_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_verify_client '{ ${'\''zarafa-ical'\''}{ssl_verify_client} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg server_timezone '{$TimeZone}'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg default_charset '{ ${'\''zarafa-ical'\''}{default_charset} || '\''utf-8'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg enable_ical_get '{ ${'\''zarafa-ical'\''}{enable_ical_get} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_enable_v2 '{ ${'\''zarafa-ical'\''}{ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- indexer config ---<br />
#<br />
echo<br />
echo "Creating zarafa-indexer-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/indexer.cfg<br />
cat /usr/share/doc/zarafa-indexer/example-config/indexer.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg cleanup_lockfiles '{ ${'\''zarafa-indexer'\''}{cleanup_lockfiles} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg limit_results '{ ${'\''zarafa-indexer'\''}{limit_results} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_method '{ ${'\''zarafa-indexer'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_level '{ ${'\''zarafa-indexer'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_timestamp '{ ${'\''zarafa-indexer'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_interval '{ ${'\''zarafa-indexer'\''}{index_interval} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_threads '{ ${'\''zarafa-indexer'\''}{index_threads} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_field_length '{ ${'\''zarafa-indexer'\''}{index_max_field_length} || '\''10000'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_merge_factor '{ ${'\''zarafa-indexer'\''}{index_merge_factor} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_buffered_docs '{ ${'\''zarafa-indexer'\''}{index_max_buffered_docs} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_min_merge_docs '{ ${'\''zarafa-indexer'\''}{index_min_merge_docs} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_merge_docs '{ ${'\''zarafa-indexer'\''}{index_max_merge_docs} || '\''2147483647'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_term_interval '{ ${'\''zarafa-indexer'\''}{index_term_interval} || '\''128'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_cache_timeout '{ ${'\''zarafa-indexer'\''}{index_cache_timeout} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachments '{ ${'\''zarafa-indexer'\''}{index_attachments} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_max_size '{ ${'\''zarafa-indexer'\''}{index_attachment_max_size} || '\''5120'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_parser_max_memory '{ ${'\''zarafa-indexer'\''}{index_attachment_parser_max_memory} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_parser_max_cputime '{ ${'\''zarafa-indexer'\''}{index_attachment_parser_max_cputime} || '\''0'\''; }'<br />
<br />
<br />
######################################<br />
# Configuring SME-events : Templates to expand<br />
######################################<br />
<br />
/bin/echo <br />
/bin/echo "Configuring SME-events : Templates2expand"<br />
/bin/echo <br />
mkdir -p /etc/e-smith/events/email-update/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/gateway.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/ical.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/server.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/unix.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/spooler.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/licensed.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/monitor.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/dagent.cfg<br />
<br />
mkdir -p /etc/e-smith/events/group-create/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/group-create/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/group-delete/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/group-delete/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/group-modify/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/group-modify/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/user-create/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/user-create/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/user-delete/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/user-delete/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/user-modify/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/user-modify/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/ibay-create/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/ibay-create/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/machine-account-create/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/machine-account-create/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/e-smith/sql/init/80zarafa<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/gateway.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/ical.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/server.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/unix.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/spooler.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/licensed.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/monitor.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/dagent.cfg<br />
<br />
<br />
######################################<br />
# Configuring SME-events : Services to adjust<br />
######################################<br />
<br />
/bin/echo <br />
/bin/echo "Configuring SME-events : Services2adjust"<br />
/bin/echo <br />
mkdir -p /etc/e-smith/events/machine-account-create/services2adjust<br />
ln -s reload /etc/e-smith/events/group-create/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/group-delete/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/group-modify/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/user-create/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/user-delete/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/user-modify/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/ibay-create/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/machine-account-create/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/timezone-update/services2adjust/zarafa-server<br />
<br />
<br />
######################################<br />
# Setting up SME-db-entries<br />
######################################<br />
<br />
/bin/echo <br />
/bin/echo "Enter the language of your choice for your zarafa-mailboxes and public store(s)."<br />
/bin/echo "Values: en_US.UTF-8, en_GB.UTF-8, nl_NL.UTF-8, fr_FR.UTF-8, de_DE.UTF-8, ..."<br />
/bin/echo <br />
read ZARAFALANGUAGE<br />
/sbin/e-smith/config set zarafa service status enabled language $ZARAFALANGUAGE<br />
/sbin/e-smith/expand-template /etc/sysconfig/zarafa<br />
<br />
/bin/echo <br />
/bin/echo "Initialize-default-databases"<br />
/bin/echo <br />
/etc/e-smith/events/actions/initialize-default-databases<br />
<br />
/bin/echo <br />
/bin/echo "Setting up db-entries for Zarafa"<br />
/bin/echo <br />
/sbin/e-smith/db configuration setprop mysqld InnoDB enabled<br />
/sbin/e-smith/db configuration setprop smtpd tnef2mime disabled<br />
/sbin/e-smith/db configuration setprop zarafa-server access private status enabled TCPPort 236 index_services_enabled yes<br />
/bin/echo <br />
/bin/echo "Enter your user plugin."<br />
/bin/echo "Values: unix or db (ldap is not supported, multicompany-support only with db-plugin)."<br />
/bin/echo <br />
read USERPLUGIN<br />
/sbin/e-smith/db configuration setprop zarafa-server user_plugin $USERPLUGIN<br />
<br />
if [ "$USERPLUGIN" == unix ]; then<br />
/sbin/e-smith/db configuration setprop zarafa-server user_plugin_config /etc/zarafa/unix.cfg<br />
fi<br />
<br />
if [ "$USERPLUGIN" == db ]; then<br />
/bin/echo<br />
/bin/echo "Do you want to set up a multicompany-environment ?"<br />
/bin/echo "Values: yes or no."<br />
/bin/echo<br />
read MULTICOMPANY<br />
/sbin/e-smith/db configuration setprop zarafa-server Multicompany $MULTICOMPANY<br />
/sbin/e-smith/db configuration delprop zarafa-server user_plugin_config<br />
if [ "$MULTICOMPANY" == yes ]; then<br />
/sbin/e-smith/db configuration setprop zarafa-server enable_hosted_zarafa true<br />
/sbin/e-smith/db configuration setprop zarafa-server loginname_format %u.%c<br />
else<br />
/sbin/e-smith/db configuration setprop zarafa-server enable_hosted_zarafa false<br />
/sbin/e-smith/db configuration setprop zarafa-server loginname_format %u<br />
fi<br />
fi<br />
<br />
/sbin/e-smith/db configuration setprop zarafa access SSL<br />
/sbin/e-smith/db configuration set zarafa-ical service access private status enabled TCPPort 8088<br />
/sbin/e-smith/db configuration set zarafa-icals service access public status enabled TCPPort 8089<br />
/sbin/e-smith/db configuration set zarafa-imap service access private status enabled TCPPort 8143<br />
/sbin/e-smith/db configuration set zarafa-imaps service access public status enabled TCPPort 8993<br />
/sbin/e-smith/db configuration set zarafa-pop3 service access private status enabled TCPPort 8110<br />
/sbin/e-smith/db configuration set zarafa-pop3s service access public status enabled TCPPort 8995<br />
/sbin/e-smith/db configuration set zarafa-ssl service access public status enabled TCPPort 237<br />
/sbin/e-smith/db configuration set zarafa-gateway service status enabled<br />
/sbin/e-smith/db configuration set zarafa-spooler service status enabled<br />
/sbin/e-smith/db configuration set zarafa-monitor service status enabled<br />
/sbin/e-smith/db configuration set zarafa-indexer service status enabled<br />
/sbin/e-smith/db configuration set zarafa-licensed service status enabled<br />
/sbin/e-smith/db configuration set zarafa-dagent service status enabled<br />
<br />
<br />
######################################<br />
# Setting up the Zarafa-db<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Expanding the my.cnf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/my.cnf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting mysqld"<br />
/bin/echo<br />
/usr/bin/sv t /service/mysqld<br />
<br />
/bin/echo<br />
/bin/echo "Signal-event remoteaccess-update"<br />
/bin/echo<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
<br />
/bin/echo<br />
/bin/echo "Creating the Zarafa-database"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/e-smith/sql/init/80zarafa<br />
/etc/rc.d/init.d/mysql.init start<br />
<br />
<br />
######################################<br />
# Expanding the Zarafa-configuration-templates<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Expanding the Zarafa-configuration-templates"<br />
/bin/echo<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
<br />
<br />
######################################<br />
# Configuration of the Webaccess<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of the Webaccess"<br />
/bin/echo<br />
/bin/chown -R www:www /var/lib/zarafa-webaccess/tmp<br />
/bin/chown -R www:www /var/lib/zarafa-webapp/tmp<br />
FILE=/etc/httpd/conf.d/zarafa-webaccess.conf; if [ -a $FILE ]; then /bin/rm -f $FILE; fi<br />
FILE=/etc/httpd/conf.d/zarafa-webapp.conf; if [ -a $FILE ]; then /bin/rm -f $FILE; fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
<br />
######################################<br />
# Setting up more symbolic links<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Setting up more symbolic links"<br />
/bin/echo<br />
if [ `getconf LONG_BIT` = "64" ]; then<br />
ln -s /usr/lib64/zarafa /usr/lib/zarafa<br />
ln -s /lib64/libcrypto.so.0.9.8e /usr/lib/libcrypto.so.0.9.8<br />
ln -s /lib64/libssl.so.0.9.8e /usr/lib/libssl.so.0.9.8 <br />
else<br />
ln -s /lib/libcrypto.so.0.9.8e /usr/lib/libcrypto.so.0.9.8<br />
ln -s /lib/libssl.so.0.9.8e /usr/lib/libssl.so.0.9.8<br />
fi<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-dagent<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-gateway<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-indexer<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-licensed<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-monitor<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-spooler<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-ical<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-server<br />
<br />
<br />
#######################################<br />
# Installing a license-key<br />
#######################################<br />
<br />
/bin/echo <br />
/bin/echo "Installing a license-key"<br />
/bin/echo <br />
if [ -x /usr/bin/zarafa-licensed ]; then<br />
if [ ! -f /etc/zarafa/license/base ]; then<br />
mkdir -p /etc/zarafa/license<br />
SERIAL="0"<br />
while [ ${#SERIAL} -ne 25 -a ${#SERIAL} -ne 0 ]; do<br />
if [ -n "$SERIAL" ]; then<br />
echo "Serial number must be 25 characters or empty"<br />
fi<br />
echo -ne "Server serial number (leave empty for none) []\t\t: "<br />
read SERIAL<br />
done<br />
SERIAL=`echo $SERIAL | tr [a-z] [A-Z]`<br />
echo $SERIAL > /etc/zarafa/license/base<br />
echo<br />
echo "The correctness of the serial will be checked when the Zarafa-server starts."<br />
echo<br />
fi<br />
fi<br />
<br />
<br />
#######################################<br />
# Starting Zarafa<br />
#######################################<br />
<br />
/bin/echo <br />
/bin/echo "Starting Zarafa-services"<br />
/bin/echo <br />
/etc/e-smith/events/actions/zarafa-services start<br />
<br />
/bin/echo<br />
/bin/echo "Setting permissions on files"<br />
/bin/echo<br />
FILE=/var/log/zarafa/dagent.log; if [ -a $FILE ]; then /bin/chmod 666 $FILE; fi<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-update<br />
<br />
<br />
#######################################<br />
# Creating public store(s)<br />
#######################################<br />
<br />
if [ "$USERPLUGIN" == unix ]; then<br />
/bin/echo<br />
/bin/echo "creating Public store"<br />
/bin/echo<br />
/usr/bin/zarafa-admin --utf8 -s<br />
fi<br />
<br />
if [ "$USERPLUGIN" == db ]; then<br />
if [ "$MULTICOMPANY" == no ]; then<br />
/bin/echo<br />
/bin/echo "creating Public store"<br />
/bin/echo<br />
/usr/bin/zarafa-admin --utf8 -s<br />
fi<br />
fi<br />
<br />
if [ "$USERPLUGIN" == db ]; then<br />
if [ "$MULTICOMPANY" == yes ]; then<br />
/bin/echo<br />
/bin/echo "Make your first company. Enter your first companyname :"<br />
/bin/echo<br />
read COMPANYNAME<br />
/usr/bin/zarafa-admin --create-company "$COMPANYNAME"<br />
/bin/echo<br />
/bin/echo "!!! REMEMBER !!! : for a multicompany-environment the username-format of the SME-user and the ZARAFA-user,"<br />
/bin/echo "has to be : [username].[companyname] !!!"<br />
/bin/echo<br />
fi<br />
fi<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== UPGRADESCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/zarafa-update =====<br />
<br />
<nowiki><br />
#!/bin/sh<br />
<br />
/bin/echo "Stopping the Zarafa-services"<br />
/etc/e-smith/events/actions/zarafa-services stop<br />
<br />
#<br />
#--- zarafa-configuration-helper-action ---<br />
#<br />
echo<br />
echo "Creating zarafa-configuration-helper-action ..."<br />
echo<br />
cat <<HERE1 > /etc/e-smith/events/actions/helpers.inc<br />
# -*- Mode: sh -*-<br />
replace() {<br />
file=\$1<br />
option=\$2<br />
value=\$3<br />
<br />
# escape &-signs, and % for sed<br />
value=\`echo \$value | sed -e 's/\&/\\\\\&/g' -e 's/\%/\\\\\%/g'\`<br />
sed -i -e "s%\([[:space:]]*\$option[[:space:]]*=[[:space:]]*\).*%\1\$value%" \$file<br />
<br />
}<br />
HERE1<br />
<br />
. /etc/e-smith/events/actions/helpers.inc<br />
<br />
#<br />
#--- sysconfig config ---<br />
#<br />
echo<br />
echo "Creating zarafa-sysconfig-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/sysconfig/zarafa<br />
cat /etc/sysconfig/zarafa | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa<br />
replace /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa ZARAFA_LOCALE '"{ ${'\''zarafa'\''}{language} || '\''en_US.UTF-8'\'' ; }"'<br />
replace /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa ZARAFA_USERSCRIPT_LOCALE '"{ ${'\''zarafa'\''}{language} || '\''en_US.UTF-8'\'' ; }"'<br />
<br />
<br />
#<br />
#--- licensed config ---<br />
#<br />
echo<br />
echo "Creating zarafa-licensed-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/licensed.cfg<br />
cat /usr/share/doc/zarafa-licensed/example-config/licensed.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_method '{ ${'\''zarafa-licensed'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_level '{ ${'\''zarafa-licensed'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_timestamp '{ ${'\''zarafa-licensed'\''}{log_timestamp} || '\''1'\''; }'<br />
<br />
#<br />
#--- server config ---<br />
#<br />
echo<br />
echo "Creating zarafa-server-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/server.cfg<br />
cat /usr/share/doc/zarafa/example-config/server.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_tcp_enabled '{ ${'\''zarafa-server'\''}{server_tcp_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_tcp_port '{ ${'\''zarafa-server'\''}{TCPPort} || '\''236'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_pipe_enabled '{ ${'\''zarafa-server'\''}{server_pipe_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_name '{ ${'\''zarafa-server'\''}{server_name} || '\''Zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg database_engine '{ ${'\''zarafa-server'\''}{database_engine} || '\''mysql'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg allow_local_users '{ ${'\''zarafa-server'\''}{allow_local_users} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg local_admin_users '{ ${'\''zarafa-server'\''}{local_admin_users} || '\''root'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg system_email_address '{ ${'\''zarafa-server'\''}{system_email_address} || '\''postmaster@localhost'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg session_timeout '{ ${'\''zarafa-server'\''}{session_timeout} || '\''300'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg license_timeout '{ ${'\''zarafa-server'\''}{license_timeout} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_method '{ ${'\''zarafa-server'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_level '{ ${'\''zarafa-server'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_timestamp '{ ${'\''zarafa-server'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_enabled '{ ${'\''zarafa-server'\''}{audit_log_enabled} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_level '{ ${'\''zarafa-server'\''}{audit_log_level} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_timestamp '{ ${'\''zarafa-server'\''}{audit_log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_host '{ ${'\''zarafa-server'\''}{mysql_host} || '\''localhost'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_port '{ ${'\''zarafa-server'\''}{mysql_port} || '\''3306'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_user '{ ${'\''zarafa-server'\''}{DbUser} || '\''zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_password '{ ${'\''zarafa-server'\''}{DbPassword}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_database '{ ${'\''zarafa-server'\''}{DbName} || '\''zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_storage '{ ${'\''zarafa-server'\''}{attachment_storage} || '\''files'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_path '/home/e-smith/files/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_compression '{ ${'\''zarafa-server'\''}{attachment_compression} || '\''6'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_enabled '{ ${'\''zarafa-ssl'\''}{server_ssl_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_port '{ ${'\''zarafa-ssl'\''}{TCPPort} || '\''237'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_key_file '/home/e-smith/ssl.pem/{$SystemName}.{$DomainName}.pem'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_key_pass '{ ${'\''zarafa-server'\''}{DbPassword}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_ca_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_ca_path '/home/e-smith/ssl.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sslkeys_path '/home/e-smith/ssl.pem'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg threads '{ ${'\''zarafa-server'\''}{threads} || '\''8'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg watchdog_frequency '{ ${'\''zarafa-server'\''}{watchdog_frequency} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg watchdog_max_age '{ ${'\''zarafa-server'\''}{watchdog_max_age} || '\''500'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_max_keep_alive_requests '{ ${'\''zarafa-server'\''}{server_max_keep_alive_requests} || '\''100'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_recv_timeout '{ ${'\''zarafa-server'\''}{server_recv_timeout} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_read_timeout '{ ${'\''zarafa-server'\''}{server_read_timeout} || '\''60'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_send_timeout '{ ${'\''zarafa-server'\''}{server_send_timeout} || '\''60'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg softdelete_lifetime '{ ${'\''zarafa-server'\''}{softdelete_lifetime} || '\''30'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_lifetime '{ ${'\''zarafa-server'\''}{sync_lifetime} || '\''365'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_log_all_changes '{ ${'\''zarafa-server'\''}{sync_log_all_changes} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_sso '{ ${'\''zarafa-server'\''}{enable_sso} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_gab '{ ${'\''zarafa-server'\''}{enable_gab} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg auth_method '{ ${'\''zarafa-server'\''}{auth_method} || '\''plugin'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg pam_service '{ ${'\''zarafa-server'\''}{pam_service} || '\''passwd'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_cell_size '{ ${'\''zarafa-server'\''}{cache_cell_size} || '\''268435456'\''; }' <br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_object_size '{ ${'\''zarafa-server'\''}{cache_object_size} || '\''5242880'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_indexedobject_size '{ ${'\''zarafa-server'\''}{cache_indexedobject_size} || '\''16777216'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_quota_size '{ ${'\''zarafa-server'\''}{cache_quota_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_quota_lifetime '{ ${'\''zarafa-server'\''}{cache_quota_lifetime} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_acl_size '{ ${'\''zarafa-server'\''}{cache_acl_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_store_size '{ ${'\''zarafa-server'\''}{cache_store_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_user_size '{ ${'\''zarafa-server'\''}{cache_user_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_userdetails_size '{ ${'\''zarafa-server'\''}{cache_userdetails_size} || '\''26214400'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_userdetails_lifetime '{ ${'\''zarafa-server'\''}{cache_userdetails_lifetime} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_server_size '{ ${'\''zarafa-server'\''}{cache_server_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_server_lifetime '{ ${'\''zarafa-server'\''}{cache_server_lifetime} || '\''30'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_warn '{ ${'\''zarafa-server'\''}{quota_warn} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_soft '{ ${'\''zarafa-server'\''}{quota_soft} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_hard '{ ${'\''zarafa-server'\''}{quota_hard} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg companyquota_warn '{ ${'\''zarafa-server'\''}{companyquota_warn} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_plugin '{ ${'\''zarafa-server'\''}{user_plugin} || '\''db'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_plugin_config '{ ${'\''zarafa-server'\''}{user_plugin_config}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_safe_mode '{ ${'\''zarafa-server'\''}{user_safe_mode} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg thread_stacksize '{ ${'\''zarafa-server'\''}{thread_stacksize} || '\''512'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_hosted_zarafa '{ ${'\''zarafa-server'\''}{enable_hosted_zarafa} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_distributed_zarafa '{ ${'\''zarafa-server'\''}{enable_distributed_zarafa} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg storename_format '{ ${'\''zarafa-server'\''}{storename_format} || '\''%f'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg loginname_format '{ ${'\''zarafa-server'\''}{loginname_format} || '\''%u'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_enabled '{ ${'\''zarafa-server'\''}{client_update_enabled} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_path '{ ${'\''zarafa-server'\''}{client_update_path} || '\''/var/lib/zarafa/client'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_log_level '{ ${'\''zarafa-server'\''}{client_update_log_level} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg hide_everyone '{ ${'\''zarafa-server'\''}{hide_everyone} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg hide_system '{ ${'\''zarafa-server'\''}{hide_system} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_enabled '{ ${'\''zarafa-server'\''}{index_services_enabled} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_search_timeout '{ ${'\''zarafa-server'\''}{index_services_search_timeout} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_prefix_chars '{ ${'\''zarafa-server'\''}{index_services_prefix_chars} || '\''3'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_enhanced_ics '{ ${'\''zarafa-server'\''}{enable_enhanced_ics} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_gab_realtime '{ ${'\''zarafa-server'\''}{sync_gab_realtime} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg disabled_features '{ ${'\''zarafa-server'\''}{disabled_features}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg max_deferred_records '{ ${'\''zarafa-server'\''}{max_deferred_records} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg max_deferred_records_folder '{ ${'\''zarafa-server'\''}{max_deferred_records_folder} || '\''20'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg coredump_enabled '{ ${'\''zarafa-server'\''}{coredump_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_enable_v2 '{ ${'\''zarafa-server'\''}{server_ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- dagent config ---<br />
#<br />
echo<br />
echo "Creating zarafa-dagent-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/dagent.cfg<br />
cat /usr/share/doc/zarafa-dagent/example-config/dagent.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_method '{ ${'\''zarafa-dagent'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_level '{ ${'\''zarafa-dagent'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_timestamp '{ ${'\''zarafa-dagent'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_raw_message '{ ${'\''zarafa-dagent'\''}{log_raw_message} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg lmtp_port '{ ${'\''zarafa-dagent'\''}{lmtp_port} || '\''2003'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg lmtp_max_threads '{ ${'\''zarafa-dagent'\''}{lmtp_max_threads} || '\''20'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg process_model '{ ${'\''zarafa-dagent'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg spam_header_name '{ ${'\''zarafa-dagent'\''}{spam_header_name} || '\''X-Spam-Status'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg spam_header_value '{ ${'\''zarafa-dagent'\''}{spam_header_value} || '\''Yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg archive_on_delivery '{ ${'\''zarafa-dagent'\''}{archive_on_delivery} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg set_rule_headers '{ ${'\''zarafa-dagent'\''}{set_rule_headers} || '\''yes'\''; }'<br />
<br />
<br />
#<br />
#--- spooler config ---<br />
#<br />
echo<br />
echo "Creating zarafa-spooler-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/spooler.cfg<br />
cat /usr/share/doc/zarafa-spooler/example-config/spooler.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg smtp_port '{ ${'\''zarafa-spooler'\''}{smtp_port} || '\''25'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_method '{ ${'\''zarafa-spooler'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_level '{ ${'\''zarafa-spooler'\''}{log_level} || '\''3'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_timestamp '{ ${'\''zarafa-spooler'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg max_threads '{ ${'\''zarafa-spooler'\''}{max_threads} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg fax_domain '{ ${'\''zarafa-spooler'\''}{fax_domain} || '\''fax.local'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg fax_international '{ ${'\''zarafa-spooler'\''}{fax_international} || '\''00'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_delegates '{ ${'\''zarafa-spooler'\''}{always_send_delegates} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_redirect_spoofing '{ ${'\''zarafa-spooler'\''}{allow_redirect_spoofing} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg copy_delegate_mails '{ ${'\''zarafa-spooler'\''}{copy_delegate_mails} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_delegate_meeting_request '{ ${'\''zarafa-spooler'\''}{allow_delegate_meeting_request} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_send_to_everyone '{ ${'\''zarafa-spooler'\''}{allow_send_to_everyone} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_tnef '{ ${'\''zarafa-spooler'\''}{always_send_tnef} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_utf8 '{ ${'\''zarafa-spooler'\''}{always_send_utf8} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg charset_upgrade '{ ${'\''zarafa-spooler'\''}{charset_upgrade} || '\''windows-1252'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg expand_groups '{ ${'\''zarafa-spooler'\''}{expand_groups} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg archive_on_send '{ ${'\''zarafa-spooler'\''}{archive_on_send} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- monitor config ---<br />
#<br />
echo<br />
echo "Creating zarafa-monitor-configuration-template ..."<br />
echo "The monitor program sends quota warning mails to users who are over quota."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/monitor.cfg<br />
cat /usr/share/doc/zarafa-monitor/example-config/monitor.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_method '{ ${'\''zarafa-monitor'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_level '{ ${'\''zarafa-monitor'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_timestamp '{ ${'\''zarafa-monitor'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg quota_check_interval '{ ${'\''zarafa-monitor'\''}{quota_check_interval} || '\''15'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg mailquota_resend_interval '{ ${'\''zarafa-monitor'\''}{mailquota_resend_interval} || '\''1'\''; }'<br />
<br />
<br />
#<br />
#--- gateway config ---<br />
#<br />
echo<br />
echo "Creating zarafa-gateway-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/gateway.cfg<br />
cat /usr/share/doc/zarafa-gateway/example-config/gateway.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg server_socket 'http://localhost:{${'\''zarafa-server'\''}{TCPPort}||'\''236'\'';}/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3_enable '{ if (${'\''zarafa-pop3'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3_port '{ ${'\''zarafa-pop3'\''}{TCPPort} || '\''8110'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3s_enable '{ if (${'\''zarafa-pop3s'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3s_port '{ ${'\''zarafa-pop3s'\''}{TCPPort} || '\''8995'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_enable '{ if (${'\''zarafa-imap'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_port '{ ${'\''zarafa-imap'\''}{TCPPort} || '\''8143'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imaps_enable '{ if (${'\''zarafa-imaps'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imaps_port '{ ${'\''zarafa-imaps'\''}{TCPPort} || '\''8993'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_only_mailfolders '{ ${'\''zarafa-imap'\''}{imap_only_mailfolders} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_public_folders '{ ${'\''zarafa-imap'\''}{imap_public_folders} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_capability_idle '{ ${'\''zarafa-imap'\''}{imap_capability_idle} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_max_messagesize '{ ${'\''zarafa-imap'\''}{imap_max_messagesize} || '\''134217728'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_generate_utf8 '{ ${'\''zarafa-imap'\''}{imap_generate_utf8} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_expunge_on_delete '{ ${'\''zarafa-imap'\''}{imap_expunge_on_delete} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_store_rfc822 '{ ${'\''zarafa-imap'\''}{imap_store_rfc822} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_private_key_file '/home/e-smith/ssl.key/{$SystemName}.{$DomainName}.key'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_certificate_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_verify_client '{ ${'\''zarafa-gateway'\''}{ssl_verify_client} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg process_model '{ ${'\''zarafa-gateway'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_method '{ ${'\''zarafa-gateway'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_level '{ ${'\''zarafa-gateway'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_timestamp '{ ${'\''zarafa-gateway'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_enable_v2 '{ ${'\''zarafa-gateway'\''}{ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- ical config ---<br />
#<br />
echo<br />
echo "Creating zarafa-ical-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/ical.cfg<br />
cat /usr/share/doc/zarafa-ical/example-config/ical.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ical_enable '{ if (${'\''zarafa-ical'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ical_port '{ ${'\''zarafa-ical'\''}{TCPPort} || '\''8088'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg icals_enable '{ if (${'\''zarafa-icals'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg icals_port '{ ${'\''zarafa-icals'\''}{TCPPort} || '\''8089'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg server_socket 'http://localhost:{${'\''zarafa-server'\''}{TCPPort}||'\''236'\'';}/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg process_model '{ ${'\''zarafa-ical'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_method '{ ${'\''zarafa-ical'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_level '{ ${'\''zarafa-ical'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_timestamp '{ ${'\''zarafa-ical'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_private_key_file '/home/e-smith/ssl.key/{$SystemName}.{$DomainName}.key'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_certificate_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_verify_client '{ ${'\''zarafa-ical'\''}{ssl_verify_client} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg server_timezone '{$TimeZone}'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg default_charset '{ ${'\''zarafa-ical'\''}{default_charset} || '\''utf-8'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg enable_ical_get '{ ${'\''zarafa-ical'\''}{enable_ical_get} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_enable_v2 '{ ${'\''zarafa-ical'\''}{ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- indexer config ---<br />
#<br />
echo<br />
echo "Creating zarafa-indexer-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/indexer.cfg<br />
cat /usr/share/doc/zarafa-indexer/example-config/indexer.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg cleanup_lockfiles '{ ${'\''zarafa-indexer'\''}{cleanup_lockfiles} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg limit_results '{ ${'\''zarafa-indexer'\''}{limit_results} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_method '{ ${'\''zarafa-indexer'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_level '{ ${'\''zarafa-indexer'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_timestamp '{ ${'\''zarafa-indexer'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_interval '{ ${'\''zarafa-indexer'\''}{index_interval} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_threads '{ ${'\''zarafa-indexer'\''}{index_threads} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_field_length '{ ${'\''zarafa-indexer'\''}{index_max_field_length} || '\''10000'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_merge_factor '{ ${'\''zarafa-indexer'\''}{index_merge_factor} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_buffered_docs '{ ${'\''zarafa-indexer'\''}{index_max_buffered_docs} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_min_merge_docs '{ ${'\''zarafa-indexer'\''}{index_min_merge_docs} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_merge_docs '{ ${'\''zarafa-indexer'\''}{index_max_merge_docs} || '\''2147483647'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_term_interval '{ ${'\''zarafa-indexer'\''}{index_term_interval} || '\''128'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_cache_timeout '{ ${'\''zarafa-indexer'\''}{index_cache_timeout} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachments '{ ${'\''zarafa-indexer'\''}{index_attachments} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_max_size '{ ${'\''zarafa-indexer'\''}{index_attachment_max_size} || '\''5120'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_parser_max_memory '{ ${'\''zarafa-indexer'\''}{index_attachment_parser_max_memory} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_parser_max_cputime '{ ${'\''zarafa-indexer'\''}{index_attachment_parser_max_cputime} || '\''0'\''; }'<br />
<br />
<br />
/bin/echo "webaccess config"<br />
/bin/chown -R www:www /var/lib/zarafa-webaccess/tmp<br />
/bin/chown -R www:www /var/lib/zarafa-webapp/tmp<br />
FILE=/etc/httpd/conf.d/zarafa-webaccess.conf; if [ -a $FILE ]; then /bin/rm -f $FILE; fi<br />
FILE=/etc/httpd/conf.d/zarafa-webapp.conf; if [ -a $FILE ]; then /bin/rm -f $FILE; fi<br />
<br />
<br />
/bin/echo "Expanding Zarafa-templates"<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
<br />
/bin/echo "Expanding http.conf-template"<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo "Restarting httpd"<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
/bin/echo "Starting Zarafa-services"<br />
/etc/e-smith/events/actions/zarafa-services start<br />
<br />
/bin/echo "Setting permissions on files"<br />
FILE=/var/log/zarafa/dagent.log; if [ -a $FILE ]; then /bin/chmod 666 $FILE; fi<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
=== Execute zarafa-install (see installscript above for 7.0.x !!!!) ===<br />
<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-install<br />
<br />
cd /etc/e-smith/events/actions/<br />
<br />
./zarafa-install<br />
<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
== UPGRADING of Zarafa ==<br />
<br />
=== VERSION 7.0.x (7.0.x -> 7.0.x) ===<br />
==== Download via the Zarafawebsite the package for ZCP corresponding with the newest php53-mapi.rpm (cf. version above) ====<br />
<br />
Go (cd /...) to the installdirectory (ex. : /root/InstallZarafa) : <br />
<br />
cd /to the installdirectory<br />
<br />
ex.: <br />
<br />
cd /root/InstallZarafa<br />
<br />
wget http://download.zarafa.com/community/final/7.0/[version]/zcp-[version]-rhel-5-[cpu-arch]-free.tar.gz<br />
<br />
==== Unpack the corresponding package for ZCP :====<br />
<br />
tar -zxvf zcp-*<br />
<br />
==== Remove the devel packages ====<br />
<br />
Go (cd ./zcp-...) to the created subdirectory (zcp-...) :<br />
<br />
cd ./zcp- ... <br />
rm -f *-dev*.rpm<br />
<br />
Move the windows-directory to an installshare in your network<br />
<br />
==== Download the latest webapp.rpm too in the same subdirectory :====<br />
<br />
wget http://download.zarafa.com/community/final/WebApp/[version]/rhel/[zarafa-webapp-version.noarch.rpm]<br />
<br />
==== !!! Remove the existing php53-mapi.rpm first : !!! ====<br />
<br />
rpm -e php53-mapi --nodeps<br />
<br />
==== Install all rpm's in the unpacked package of ZCP and the webapp.rpm too :====<br />
<br />
yum localinstall *.rpm<br />
<br />
All packages have dependencies that cannot be resolved if you install only part of the rpm's.<br />
<br />
If you only want to upgrade one package (ex. the Webapp) :<br />
<br />
cd /to the new Webapp.rpm<br />
rpm -Uvh --force zarafa-webapp-[version].noarch<br />
<br />
==== Remove the default php-mapi.rpm ====<br />
<br />
We have to remove the installation of the default php-mapi (because it's not built for php 5.3).<br />
<br />
rpm -e php-mapi --nodeps<br />
<br />
==== Install the NEW php53-mapi.rpm ====<br />
-If you downloaded the rpm :<br />
<br />
rpm -Uvh --force php53-mapi<br />
<br />
-If you did set the EPEL-repository :<br />
<br />
yum install php53-mapi --enablerepo=epel --enablerepo=epel-testing<br />
<br />
==== Execute zarafa-update (see upgradescript above for 7.0.x !!!!) ====<br />
<br />
cd /etc/e-smith/events/actions/<br />
<br />
./zarafa-update<br />
<br />
OPTIONAL : Search in the Zarafa-releasenotes for new keys/options in the config-files and adjust the values of these new keys/options in the zarafa-config-templates :<br />
<br />
http://doc.zarafa.com/7.0/Release_Notes/en-US/html-single/<br />
<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
== INSTALLATION of Z-push (1.5.x or 2.0.x) ==<br />
<br />
* You can test if z-push is installed and functioning by going to http://[your-server-ip]/Microsoft-Server-ActiveSync You should be presented with a login request, and if you cancel, you will see Z-Push info. If you see both, z-push is working just fine.<br />
* If you experience (all of a sudden) z-push issues with your smartphone, please increase the PHP memory limit as descibed [http://wiki.contribs.org/Useful_Commands#Memory_Limit here]<br />
* Please note that z-push version 2.1 works with the below 2.0.x instructions, but you need to install php-posix<br />
yum install php-posix<br />
<br />
=== VERSION 1.5.x ===<br />
==== Download the Z-push-package (version 1.5 !!)====<br />
<br />
wget http://zarafa-deutschland.de/z-push-download/final/1.5/[z-push-latest version]<br />
<br />
Save in an installdirectory, ex. : root/InstallZPush<br />
<br />
==== Unpack the package for Z-push :====<br />
<br />
Go (cd /...) to the installdirectory (if you haven't done this yet) : <br />
<br />
cd /to the installdirectory<br />
<br />
And unpack :<br />
<br />
tar -zxvf z-push-[latest version] -C /var/www/html<br />
<br />
==== Change the name of the created z-push-directory in /var/www/html to 'z-push'====<br />
<br />
==== INSTALLSCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/z-push-install =====<br />
<nowiki><br />
#!/bin/sh<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ..."<br />
echo<br />
cat <<HERE1 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases<br />
{<br />
# vim: ft=perl:<br />
<br />
\$haveSSL = (exists \${modSSL}{status} and \${modSSL}{status} eq "enabled") ? 'yes' : 'no';<br />
my \$zwebmailStatus = \$zarafa{'status'} || "disabled";<br />
my \$zwebmailAccessType = \$zarafa{'access'} || "SSL";<br />
<br />
my \$dirs;<br />
\$dirs{zarafa} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webaccess} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webmail} = '/usr/share/zarafa-webaccess';<br />
if (\$imp{'status'} eq 'enabled') {\$dirs{webmail} = ''};<br />
\$dirs{webapp} = '/usr/share/zarafa-webapp';<br />
\$dirs{'Microsoft-Server-ActiveSync'} = '/var/www/html/z-push/index.php';<br />
<br />
return " # Zarafa is disabled in this VirtualHost\n"<br />
unless \$zwebmailStatus eq 'enabled';<br />
<br />
foreach \$place ('zarafa','webmail','webaccess','webapp','Microsoft-Server-ActiveSync')<br />
{<br />
if ((\$port eq "80") && (\$haveSSL eq 'yes') && (\$zwebmailAccessType eq 'SSL'))<br />
{<br />
\$OUT .= " RewriteRule ^/\$place(/.*|\\$) https://%{HTTP_HOST}/\$place\\\$1 [L,R]\n";<br />
} else {<br />
if ((\$dirs{\$place}) ne '') {\$OUT .= " Alias /\$place \$dirs{\$place}\n"};<br />
}<br />
} <br />
}<br />
HERE1<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ..."<br />
echo<br />
cat <<HERE2 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias<br />
{<br />
my \$zstatus = \$zarafa{'status'};<br />
<br />
if (defined \$zstatus && \$zstatus eq 'enabled')<br />
{<br />
\$OUT .= qq(<br />
#--------------------------------------------------------------------<br />
# Zarafa specific configuration files.<br />
#--------------------------------------------------------------------<br />
<br />
Alias /zarafa /usr/share/zarafa-webaccess/<br />
<Directory /usr/share/zarafa-webaccess/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
Alias /webapp /usr/share/zarafa-webapp/<br />
<Directory /usr/share/zarafa-webapp/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
<Directory /var/www/html/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php .php3<br />
php_flag magic_quotes_gpc off<br />
</Directory><br />
<br />
<Directory /var/www/html/z-push/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag register_globals off<br />
php_flag magic_quotes_runtime off<br />
php_flag short_open_tag on<br />
</Directory><br />
<br />
);<br />
} <br />
else<br />
{<br />
\$OUT .= "# Zarafa Webmail is not configured as it is disabled in the config db";<br />
}<br />
}<br />
HERE2<br />
<br />
######################################<br />
# Configuration of Z-push<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of Z-push"<br />
/bin/echo<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
<br />
/bin/echo <br />
/bin/echo "Need to debug Z-push ?"<br />
/bin/echo "Values: yes or no."<br />
/bin/echo <br />
read DEBUGZPUSH<br />
if [ "$DEBUGZPUSH" == yes ]; then<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/touch /var/www/html/z-push/debug.txt; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chown www:www /var/www/html/z-push/debug.txt; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chmod 755 /var/www/html/z-push/debug.txt; fi<br />
else<br />
rm -f /var/www/html/z-push/debug.txt<br />
fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== UPGRADESCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/z-push-update =====<br />
<nowiki><br />
#!/bin/sh<br />
<br />
######################################<br />
# Configuration of Z-push<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of Z-push"<br />
/bin/echo<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
<br />
/bin/echo <br />
/bin/echo "Need to debug Z-push ?"<br />
/bin/echo "Values: yes or no."<br />
/bin/echo <br />
read DEBUGZPUSH<br />
if [ "$DEBUGZPUSH" == yes ]; then<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/touch /var/www/html/z-push/debug.txt; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chown www:www /var/www/html/z-push/debug.txt; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chmod 755 /var/www/html/z-push/debug.txt; fi<br />
else<br />
rm -f /var/www/html/z-push/debug.txt<br />
fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== See further : "Any version" ====<br />
<br />
=== VERSION 2.0.x ===<br />
==== Download the Z-push-package (version 2.0 !!)====<br />
wget http://zarafa-deutschland.de/z-push-download/final/2.0/[z-push-latest version]<br />
<br />
Save in an installdirectory, ex. : root/InstallZPush<br />
<br />
==== Unpack the package for Z-push :====<br />
Go (cd /...) to the installdirectory (if you haven't done this yet) : <br />
<br />
cd /to the installdirectory<br />
<br />
And unpack :<br />
<br />
tar -zxvf z-push-[latest version] -C /usr/share<br />
<br />
==== Change the name of the created z-push-directory in /usr/share to 'z-push' ====<br />
<br />
==== INSTALLSCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/z-push-install =====<br />
<nowiki><br />
#!/bin/sh<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ..."<br />
echo<br />
cat <<HERE1 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases<br />
{<br />
# vim: ft=perl:<br />
<br />
\$haveSSL = (exists \${modSSL}{status} and \${modSSL}{status} eq "enabled") ? 'yes' : 'no';<br />
my \$zwebmailStatus = \$zarafa{'status'} || "disabled";<br />
my \$zwebmailAccessType = \$zarafa{'access'} || "SSL";<br />
<br />
my \$dirs;<br />
\$dirs{zarafa} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webaccess} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webmail} = '/usr/share/zarafa-webaccess';<br />
if (\$imp{'status'} eq 'enabled') {\$dirs{webmail} = ''};<br />
\$dirs{webapp} = '/usr/share/zarafa-webapp';<br />
\$dirs{'Microsoft-Server-ActiveSync'} = '/usr/share/z-push/index.php';<br />
<br />
return " # Zarafa is disabled in this VirtualHost\n"<br />
unless \$zwebmailStatus eq 'enabled';<br />
<br />
foreach \$place ('zarafa','webmail','webaccess','webapp','Microsoft-Server-ActiveSync')<br />
{<br />
if ((\$port eq "80") && (\$haveSSL eq 'yes') && (\$zwebmailAccessType eq 'SSL'))<br />
{<br />
\$OUT .= " RewriteRule ^/\$place(/.*|\\$) https://%{HTTP_HOST}/\$place\\\$1 [L,R]\n";<br />
} else {<br />
if ((\$dirs{\$place}) ne '') {\$OUT .= " Alias /\$place \$dirs{\$place}\n"};<br />
}<br />
} <br />
}<br />
HERE1<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ..."<br />
echo<br />
cat <<HERE2 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias<br />
{<br />
my \$zstatus = \$zarafa{'status'};<br />
<br />
if (defined \$zstatus && \$zstatus eq 'enabled')<br />
{<br />
\$OUT .= qq(<br />
#--------------------------------------------------------------------<br />
# Zarafa specific configuration files.<br />
#--------------------------------------------------------------------<br />
<br />
Alias /zarafa /usr/share/zarafa-webaccess/<br />
<Directory /usr/share/zarafa-webaccess/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
Alias /webapp /usr/share/zarafa-webapp/<br />
<Directory /usr/share/zarafa-webapp/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
<Directory /usr/share/z-push/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php .php3<br />
php_flag magic_quotes_gpc off<br />
php_flag register_globals off<br />
php_flag magic_quotes_runtime off<br />
php_flag short_open_tag on<br />
</Directory><br />
<br />
);<br />
} <br />
else<br />
{<br />
\$OUT .= "# Zarafa Webmail is not configured as it is disabled in the config db";<br />
}<br />
}<br />
HERE2<br />
<br />
######################################<br />
# Configuration of Z-push<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of Z-push"<br />
/bin/echo<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/echo -e "** $FILE already exists, skipping **\n"; else /bin/mkdir $FILE; fi<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/echo -e "** $FILE already exists, skipping **\n"; else /bin/mkdir $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== UPGRADESCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/z-push-update =====<br />
<nowiki><br />
#!/bin/sh<br />
<br />
######################################<br />
# Configuration of Z-push<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of Z-push"<br />
/bin/echo<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/echo -e "** $FILE already exists, skipping **\n"; else /bin/mkdir $FILE; fi<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/echo -e "** $FILE already exists, skipping **\n"; else /bin/mkdir $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== See further : "Any version" ====<br />
<br />
=== ANY VERSION (1.5.x or 2.0.x)===<br />
==== Edit the config.php file in the Z-Push directory to fit your needs. ====<br />
ex. Set your timezone in the config.php file.<br />
<br />
==== Execute z-push-install (see script above !!!!) ====<br />
<br />
/bin/chmod 554 /etc/e-smith/events/actions/z-push-install<br />
<br />
cd /etc/e-smith/events/actions/<br />
<br />
./z-push-install<br />
<br />
== UPGRADING of Z-push ==<br />
=== VERSION 1.5 (1.5.x -> 1.5.x)===<br />
==== Download the Z-push-package (version 1.5 !!)====<br />
<br />
wget http://zarafa-deutschland.de/z-push-download/final/1.5/[z-push-latest version]<br />
<br />
Save in an installdirectory, ex. : root/InstallZPush<br />
<br />
==== Unpack the corresponding package for ZCP and the package for Z-push :====<br />
<br />
Go (cd /...) to the installdirectory (if you haven't done this yet) : <br />
<br />
cd /to the installdirectory<br />
<br />
And unpack :<br />
<br />
tar -zxvf z-push-[latest version] -C /var/www/html<br />
<br />
==== Change the name of the created z-push-directory in /var/www/html to 'z-push'====<br />
==== See further : "Any version" ====<br />
=== VERSION 2.0 (2.0.x -> 2.0.x)===<br />
==== Download the Z-push-package (version 2.0 !!)====<br />
<br />
wget http://zarafa-deutschland.de/z-push-download/final/2.0/[z-push-latest version]<br />
<br />
Save in an installdirectory, ex. : root/InstallZPush<br />
<br />
<br />
==== Unpack the package for Z-push :====<br />
<br />
Go (cd /...) to the installdirectory (if you haven't done this yet) : <br />
<br />
cd /to the installdirectory<br />
<br />
And unpack :<br />
<br />
tar -zxvf z-push-[latest version] -C /usr/share<br />
<br />
==== Change the name of the created z-push-directory in /usr/share to 'z-push'====<br />
==== See further : "Any version" ====<br />
=== VERSION 1.5.x -> 2.0.x ===<br />
<br />
The easiest way to upgrade is to follow the steps for a new installation of version 2.0. The states of Z-Push 1.X are not compatible and there is no upgrade path, but as this version implements a fully automatic resynchronisation of devices it should not affect the users and work without the user interaction<br />
<br />
=== ANY VERSION ===<br />
==== Edit the config.php file in the Z-Push directory to fit your needs. ====<br />
ex. Set your timezone in the config.php file.<br />
<br />
==== Execute z-push-update (see script above !!!!) ====<br />
<br />
/bin/chmod 554 /etc/e-smith/events/actions/z-push-update<br />
<br />
cd /etc/e-smith/events/actions/<br />
<br />
./z-push-update<br />
<br />
== Managing Zarafa-users/companies : ==<br />
=== With Unix-plugin ===<br />
Zarafa-users are created with the creation of a SME-user, but you have to enable delivery to zarafa for these SME-users. <br />
==== Enable maildelivery to zarafa for a user : ====<br />
db accounts setprop [USERNAME] zarafa enabled<br />
/etc/e-smith/events/actions/qmail-update-user<br />
==== Disable maildelivery to zarafa for a user : ====<br />
db accounts setprop [USERNAME] zarafa disabled<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
==== Enable mail delivery to zarafa for ALL users : ====<br />
config setprop zarafa-server GlobalForward enabled<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
==== Other options for managing users ====<br />
zarafa-admin --help<br />
<br />
=== With DB-plugin ===<br />
==== Create company (in a Multi-company-environment) ====<br />
/etc/e-smith/events/actions/zarafa-create-company<br />
<br />
==== Create user ====<br />
/etc/e-smith/events/actions/zarafa-create-user<br />
==== Disable maildelivery to zarafa for a user : ====<br />
db accounts setprop [USERNAME] zarafa disabled<br />
/etc/e-smith/events/actions/qmail-update-user<br />
==== Other options for managing users/companies ====<br />
zarafa-admin --help<br />
<br />
== Usefull commands : ==<br />
<br />
=== Change db-entries (Change default-values in zarafa-config-files) ===<br />
config setprop [zarafa-service] [key] [value]<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
/etc/e-smith/events/actions/zarafa-services restart<br />
<br />
==== Change loglevel to 5 (= max. (default = 2))====<br />
config setprop zarafa-server log_level 5<br />
config setprop zarafa-dagent log_level 5<br />
config setprop zarafa-spooler log_level 5<br />
config setprop zarafa-monitor log_level 5<br />
config setprop zarafa-ical log_level 5<br />
config setprop zarafa-gateway log_level 5<br />
config setprop zarafa-licensed log_level 5<br />
config setprop zarafa-indexer log_level 5<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
/etc/e-smith/events/actions/zarafa-services restart<br />
<br />
==== Change index-interval to 60 minutes (= max. (default = 5))====<br />
config setprop zarafa-indexer index_interval 60<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
/etc/e-smith/events/actions/zarafa-services restart<br />
<br />
==== Setting system-email-address ====<br />
config setprop zarafa-server system_email_address [admin@mydomain.com] <br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
/etc/e-smith/events/actions/zarafa-services restart<br />
<br />
=== Debugging Z-push 1.5.x (not for 2.0.x) ===<br />
==== Disable (debugging is enabled by default in this howto) ====<br />
rm -f /var/www/html/z-push/debug.txt<br />
==== Enable after disabling (debugging is enabled by default in this howto) ====<br />
/bin/touch /var/www/html/z-push/debug.txt<br />
/bin/chown www:www /var/www/html/z-push/debug.txt<br />
/bin/chmod 755 /var/www/html/z-push/debug.txt<br />
<br />
=== View userdetails ===<br />
zarafa-admin --details [user]<br />
<br />
=== Setting/Changing send-emailadres for a user ===<br />
zarafa-admin -u [user] -e [send-emailadres]<br />
<br />
=== Setting/Changing fullname for a user ===<br />
zarafa-admin -u [user] -f "[full name]"<br />
<br />
=== Quota-settings ===<br />
zarafa-admin -u [user] --qo y --qw 1600 --qs 1800 --qh 2000<br />
<br />
=== Give a user administrator-privileges ===<br />
zarafa-admin -u [user] -a y<br />
<br />
== Usefull plugins : ==<br />
=== Password-plugin for webaccess (ONLY FOR DB-PLUGIN) ===<br />
[https://community.zarafa.com/pg/plugins/project/157/developer/dw2412/passwd-plugin Dev-page]<br />
<br />
After installation : in /var/lib/zarafa-webaccess/plugins/passwd/dialogs/pwdchange.php, change this line :<br />
<br />
$passwd_cmd = "/usr/local/bin/zarafa-passwd -u %s -o %s -p %s";<br />
<br />
to this :<br />
<br />
$passwd_cmd = "/usr/bin/zarafa-passwd -u '%s' -o '%s' -p '%s'";<br />
<br />
=== Password-change by users from outsite your network for webaccess/webapp (IF USING THE UNIX PLUGIN) ===<br />
==== Install Usermanager ====<br />
[[UserManager]] : Install smeserver-userpanel and smeserver-userpanels<br />
<br />
==== nano /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/VirtualHosts/28UserManagerProxyPass ====<br />
<nowiki><br />
{<br />
# vim: ft=perl:<br />
$haveSSL = (exists ${modSSL}{status} and ${modSSL}{status} eq "enabled") ? 'yes' : 'no';<br />
$plainTextAccess = ${'httpd-admin'}{PermitPlainTextAccess} || 'no';<br />
$OUT = '';<br />
foreach $place ('user-manager','server-common','user')<br />
{<br />
if (($port eq "80") && ($haveSSL eq 'yes') && ($plainTextAccess ne 'yes'))<br />
{<br />
$OUT .= " RewriteRule ^/$place(/.*|\$) https://%{HTTP_HOST}/$place\$1 [L,R,NC]\n";<br />
} else {<br />
$OUT .= " ProxyPass /$place http://127.0.0.1:${'httpd-admin'}{TCPPort}/$place\n";<br />
$OUT .= " ProxyPassReverse /$place http://127.0.0.1:${'httpd-admin'}{TCPPort}/$place\n";<br />
}<br />
$OUT .= " <Location /$place>\n";<br />
$OUT .= " order deny,allow\n";<br />
$OUT .= " deny from all\n";<br />
$OUT .= " allow from all\n"; <br />
$OUT .= " </Location>\n";<br />
}<br />
}<br />
</nowiki><br />
<br />
==== To save : ====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== Via the Server-Manager : Delegate the userpanel-password to external users ====<br />
Now these external users can change from outsite your network there sme-password : https://www.yourdomain.tld/user<br />
<br />
=== WebApp - OwnCloud attachment plug-in ===<br />
<br />
[https://community.zarafa.com/pg/plugins/project/16024/developer/h44z/webapp-owncloud-attachment-plugin OwnCloud attachment plug-in]<br />
<br />
=== WebApp - Dropbox attachment plug-in===<br />
<br />
[https://community.zarafa.com/pg/blog/read/14505/webapp-the-dropbox-plugin Dropbox plug-in]<br />
<br />
== Webmail : ==<br />
Access with a browser,<br />
<br />
https://server/zarafa<br />
https://server/webaccess<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/webapp (NEW VERSION OF WEBACCESS)<br />
<br />
== Connecting Outlook : ==<br />
<br />
On your Windowsclients, execute zarafaclient.msi (Moved earlier to an installshare in your network - cf. supra)<br />
<br />
Configure Outlook (point it to your zarafaserver with the credentials of a created Zarafa-user (if DB-plugin : create Zarafa-users first))<br />
<br />
== Connecting other clients : ==<br />
=== IMAP/POP3 ===<br />
The default ports for Zarafa are 8000 + default values<br />
*so imap = 8143, imaps = 8993<br />
*so pop3 = 8110, pop3s = 8995<br />
<br />
== Zarafa-documentation : ==<br />
<br />
=== Zarafa Administrator Manual ===<br />
[http://doc.zarafa.com/7.0/Administrator_Manual/en-US/html-single/index.html Zarafa Administrator Manual]<br><br />
[http://doc.zarafa.com/7.0/Release_Notes/en-US/html-single Release notes (changes in the Zarafa-configfiles)]<br><br />
=== Zarafa User Manual ===<br />
[http://doc.zarafa.com/trunk/User_Manual_WebApp/en-US/html/ Usermanual Zarafa-Webapp]<br />
<br />
=== Help for the zarafa-admin-tool ===<br />
zarafa-admin --help<br />
=== man-pages ===<br />
==== services-man-pages ====<br />
man zarafa-server<br />
man zarafa-monitor<br />
man zarafa-dagent<br />
man zarafa-gateway<br />
man zarafa-spooler<br />
man zarafa-ical<br />
man zarafa-indexer<br />
man zarafa-licensed<br />
==== configuation-man-pages ====<br />
man zarafa-server.cfg<br />
man zarafa-monitor.cfg<br />
man zarafa-dagent.cfg<br />
man zarafa-gateway.cfg<br />
man zarafa-spooler.cfg<br />
man zarafa-ical.cfg<br />
man zarafa-indexer.cfg<br />
man zarafa-licensed.cfg<br />
man zarafa-unix.cfg<br />
<br />
[[Category:Howto]]<br />
[[Category:Groupware]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=23458
Zarafa on SME 9
2014-01-26T18:33:40Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|<br />
'''This wiki page is specific to SME9 only.'''<br />
<br />
'''There is a separate wiki page on how to install Zarafa 7.x on SME7 [[Zarafa|Zarafa on SME 7]].'''<br />
<br />
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME8 [[Zarafa_on_SME8|Zarafa on SME 8]].'''<br />
}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta2. It should be ready for production servers when SME9 reaches RC stage.<br />
This contrib will NOT work on SME 7 or SME8, there are unresolved dependencies.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
Now install smeserver-zarafa-unix by performing the following:<br />
yum install smeserver-zarafa-unix --enablerepo=smedev<br />
<br />
NOTE: If you installed the GPL version of Zarafa, you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
After rpm install execute the following:<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
=====To disable global Zarafa for all users=====<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
=====To enable an individual user if Global is disabled=====<br />
db accounts setprop $USERNAME Zarafa enabled<br />
signal-event user-modify $USERNAME<br />
=====To enable the admin account=====<br />
db accounts setprop admin Zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
=====Known working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=====Additional Mobile Synchronization Information=====<br />
<br />
'''SSL Synchronization with Windows Mobile devices'''<br />
<br />
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=23457
Zarafa on SME 9
2014-01-26T18:31:29Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|<br />
'''This wiki page is specific to SME9 only.'''<br />
<br />
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME7 [[Zarafa|Zarafa on SME 7]].'''<br />
<br />
'''There is a separate wiki page with a ''fully automated'' install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa_on_SME8|Zarafa on SME 8]].'''<br />
}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta2. It should be ready for production servers when SME9 reaches RC stage.<br />
This contrib will NOT work on SME 7 or SME8, there are unresolved dependencies.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
Now install smeserver-zarafa-unix by performing the following:<br />
yum install smeserver-zarafa-unix --enablerepo=smedev<br />
<br />
NOTE: If you installed the GPL version of Zarafa, you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
After rpm install execute the following:<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
=====To disable global Zarafa for all users=====<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
=====To enable an individual user if Global is disabled=====<br />
db accounts setprop $USERNAME Zarafa enabled<br />
signal-event user-modify $USERNAME<br />
=====To enable the admin account=====<br />
db accounts setprop admin Zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
=====Known working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=====Additional Mobile Synchronization Information=====<br />
<br />
'''SSL Synchronization with Windows Mobile devices'''<br />
<br />
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa&diff=23456
Zarafa
2014-01-26T18:29:51Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa}}<br />
{{Level|advanced}}<br />
{{Note box|<br />
'''This wiki page is specific to SME7 only.'''<br />
<br />
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME8 [[Zarafa on SME8]].'''<br />
<br />
'''There is a separate wiki page with a ''fully automated'' install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa on SME 9]].'''<br />
}}<br />
<br />
===Maintainers===<br />
Darrell May<br />
<br />
Stephen Noble http://dungog.net/wiki<br />
<br />
=== Version ===<br />
{{#smeversion:smeserver-zarafa}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
<br />
===Installation===<br />
<br />
==== Latest zarafa tested version ====<br />
Information on previous versions of zarafa rpms can be found in the [http://download.zarafa.com/zarafa/release/docs/changelog.en.txt changelog document]<br />
<br />
==== Zarafa rpms installation ====<br />
<br />
http://www.zarafa.com/download-community<br />
<br />
Distribution: Rhel 4 = SME 7 :: Rhel 5 = SME 8<br />
<br />
Select a version, the 3 Outlook license version, or the GPL version. (which doesn't have the zarafa-licensed-*.rpm)<br />
<br />
tar -zxvf zarafa-6.*.tar.gz<br />
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-6*.rpm zarafa-webaccess-*.rpm zarafa-licensed-*.rpm<br />
<br />
This will also install as a dependency: ''sysstat''<br />
{{Note box| You have to enable InnoDB support in MySql in order to get zarafa-server running, for information on how to do so, see [[MySQL#Enable_InnoDB_engine]]}}<br />
<br />
==== smeserver-zarafa ====<br />
<br />
{{Note box| This is an alpha release. Possibly for production servers after testing with per user settings first.<br />
<br />
You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir.<br />
<br />
A minimal amount of disruption can be achieved by enabling per user, that user just enables another IMAP connection in their email client on port 8143, they could then just drag and drop mail between SME to Zarafa mail stores. }}<br />
<br />
Install a fresh SME 7.4 test server and perform the following:<br />
<br />
yum install smeserver-zarafa --enablerepo=smedev<br />
config setprop zarafa-licensed status disabled #GPL version only<br />
<br />
{{Note box|If you installed the GPL version only (without outlook support), you need to create the (empty) file '/var/log/zarafa/licensed.log'. This file is required in all cases. Without this file (and using the GPL non-Outlook version), the Zarafa configuration panel in server manager will not be displayed.}}<br />
<br />
<br />
After rpm install execute the following:<br />
<br />
/etc/e-smith/events/actions/zarafa-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
{{Note box| You will be prompted to select the user plugin you wish to test. We suggest the db method. Note the ldap plugin is currently not supported in the rpm. The unix plugin reads existing SME user details but also includes groups and machine names (messy). The db plugin is pristine however you need to enter all the user details. In both cases the user must exist in SME first as a standard user. A decision on which plugin we will choose for final deployment is still to be determined.}}<br />
<br />
==== Updating ====<br />
Download newer rpms, then<br />
rpm -Uvh zarafa-6*.rpm zarafa-webaccess-*.rpm libvmime-0*.rpm libical-0*.rpm zarafa-licensed-*.rpm<br />
/etc/e-smith/events/actions/zarafa-update<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
===Usage===<br />
====Managing Users====<br />
Enable mail delivery to zarafa for users:<br />
<br />
for all users<br />
config setprop zarafa-server GlobalForward enabled<br />
or for individual users<br />
db accounts setprop $USERNAME zarafa enabled<br />
apply<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
If you chose the db plugin, run:<br />
<br />
/etc/e-smith/events/actions/zarafa-create-user<br />
<br />
or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )<br />
<br />
<br />
====Webmail====<br />
Access with a browser,<br />
<br />
https://server/zarafa<br />
https://server/webaccess<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
<br />
* Outlook 2007 client generates ''Error 0x80070057'' on send and receive if the Zarafa<br />
server is added to an existing profile. Creating a new clean profile solved<br />
the problem.<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
=====Thunderbird=====<br />
It seems that in the latest Thunderbird versions security tightened and Thunderbird will simply reject Self Signed Certificates when you try to connect to a (remote) SME Server on secure ports.<br />
You first must add all the secure services ports to the security exceptions of Thunderbird under:<br />
* tools->options->advanced->certificates->view certificates->Add Exception<br />
and add your server address INLCUDING the specific port number of the service for EACH of the service-ports!<br />
<br />
The format must be:<br />
https://yourserver.com:8993 (for IMAPS)<br />
https://yourserver.com:465 (SMTP)<br />
https://yourserver.com:8089 (Caldav)<br />
etc. etc<br />
<br />
After accepting the self signed certificate for each service-port, you then can add an new email account and the Self Signed Certificate will not be rejected and you normally accept or install it like any other certificate.<br />
<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
==== Calendar CalDAV / iCal ====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>https://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>https://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>https://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>https://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>https://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>https://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>https://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>https://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>https://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>https://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf<br />
<br />
<br />
Download the latest Z-push version (see: http://z-push.sourceforge.net).<br />
wget http://download2.berlios.de/z-push/z-push-1.2.2.tar.gz<br />
<br />
Extract the files:<br />
tar -zxvf z-push-1.2.2.tar.gz -C /var/www/html<br />
<br />
'State'-dir needs to be writable for apache:<br />
chmod 755 /var/www/html/z-push/state<br />
chown www:www /var/www/html/z-push/state<br />
<br />
Expand and restart<br />
expand-template /etc/httpd/conf/httpd.conf<br />
sv restart httpd-e-smith<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=== Extras ===<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/<br />
<br />
----<br />
[[Category: Contrib]]<br />
[[Category: Groupware]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=23455
Zarafa on SME 9
2014-01-26T18:27:36Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|<br />
'''This wiki page is specific to SME9 only.'''<br />
<br />
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME7 [[Zarafa|Zarafa on SME 7]].'''<br />
<br />
'''There is a separate wiki page with a ''fully automated'' install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa_on_SME_8|Zarafa on SME 8]].'''<br />
}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta2. It should be ready for production servers when SME9 reaches RC stage.<br />
This contrib will NOT work on SME 7 or SME8, there are unresolved dependencies.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
Now install smeserver-zarafa-unix by performing the following:<br />
yum install smeserver-zarafa-unix --enablerepo=smedev<br />
<br />
NOTE: If you installed the GPL version of Zarafa, you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
After rpm install execute the following:<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
=====To disable global Zarafa for all users=====<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
=====To enable an individual user if Global is disabled=====<br />
db accounts setprop $USERNAME Zarafa enabled<br />
signal-event user-modify $USERNAME<br />
=====To enable the admin account=====<br />
db accounts setprop admin Zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
=====Known working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=====Additional Mobile Synchronization Information=====<br />
<br />
'''SSL Synchronization with Windows Mobile devices'''<br />
<br />
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME8&diff=23454
Zarafa on SME8
2014-01-26T18:21:51Z
<p>Pfloor: </p>
<hr />
<div>{{Level|Developer}}<br />
{{Note box|<br />
'''This wiki page is specific to SME8 only.'''<br />
<br />
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME7 [[Zarafa|Zarafa on SME 7]].'''<br />
<br />
'''There is a separate wiki page with a ''fully automated'' install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa on SME 9|Zarafa on SME 9]].'''<br />
}}<br />
<br />
<br />
*'''New zarafa-7.0.x- and z-push-install/upgradescripts for SME8'''<br> These new scipts always take the default NEW-config-files from the zarafa.rpms (found in /usr/share/doc/zarafa/example-config/) and make SME-templates of these default config-files ! So, you will always have the newest templated config-files, even after upgrading to a new Zarafa-version with altered config-files !<br> There is even more integration with the SME-perlDB too. (Most of the zarafa-config-keys can be set in the SME-perlDB !).<br> <br />
*You can find a upgrade-path to Z-push 2.0 (tested with Zarafa 7.0.12 and Z-push 2.0.7).<br><br />
*For version 1.3 of the Webapp you need minimum zarafa 7.0.12.<br />
<br />
_____________________<br />
<br />
*Placeholder for [[Zarafa quick install script]]<br />
<br />
<br />
== Maintainer ==<br />
Frederik POLLET : [mailto:frederik.pollet@pollet-ghys.be email]<br />
<br />
== Description ==<br />
*http://www.zarafa.com<br />
*http://z-push.sourceforge.net/soswp/<br />
<br />
Zarafa is a groupware-server which enables the sharing of mail, contacts, appointments, notes and tasks in a web-interface and/or Microsoft Outlook (or even other clients). It supports MAPI, POP3, IMAP, CalDAV/iCal. It can be used as a MS Exchange replacement, even featuring public folders. Connecting Microsoft Outlook with this groupware-server is simple, enabling most of the MS Exchange-functions.<br />
<br />
Z-push is an implementation of Microsoft's ActiveSync protocol which is used 'over-the-air' for multi platform active sync devices, including Windows Mobile and active sync used on Apple's iPhone, Sony Ericsson and Nokia phones. Open source Z-Push enables any PHP-based groupware package to become fully syncable with any ActiveSync-compliant device.<br />
<br />
== Making some decisions before installing : ==<br />
<br />
Zarafa can be configured with 3 different 'user-backends' :<br />
*database (db)<br />
*unix-users<br />
*LDAP/AD (not implemented in this howto)<br />
<br />
Using the '''db-plugin''' in the Zarafa-configuration, let you make your zarafa-users in the MySQL-zarafadatabase, with a separate user-password for every Zarafa-user and a store. So, you make your separated Zarafa-users and the stores for these Zarafa-users one by one in the Zarafa-MySQL-database with the '''zarafa-admin'''-tool and sripts in this howto. There is no syncronisation between the SME-user-passwords and the Zarafa-user-passwords. You can only enable maildelivery for a SME/unix-user to a Zarafa-user <u>with the same logon-name</u>.<br><br />
<br />
When using the '''unix-plugin''' in the Zarafa-configuration, Zarafa makes a store for every SME/unix-user on your system, except for those who are excluded by the template used in this howto. Zarafa uses the passwords of the SME/unix-users. There are no separated Zarafa-users and no separated passwords. You can enable maildelivery for a SME/unix-user to Zarafa. Since the unix files do not contain enough information for Zarafa, there are some properties of a user that will be stored in the MySQL-zarafadatabase. These properties are the email address, overriding quota settings, and administrator settings. The '''zarafa-admin'''-tool has to be used to update these user properties. All other user-properties are done using the normal unix tools. '''The unix-plugin seems to be your best choice if all your SME-users will use Zarafa Webaccess/Microsoft Outlook, and you don't need a multicompany-environment'''.<br><br />
<br />
[http://doc.zarafa.com/7.0/Administrator_Manual/en-US/html-single/index.html#_user_authentication MORE INFORMATION]<br />
<br />
In a multicompany-evironment every company has his own Global Adressbook and public folders.<br />
{{Warning box|A multicompany-evironment is only possible with the DB-plugin.<br>}}<br />
{{Warning box|IMPORTANT : If you want to have a multicompany-environment, <u>format of the SME/unix-username and the ZARAFA-username has to be [username].[companyname]</u> !!!<br>}}<br />
<br />
== INSTALLATION of VERSION 7.0.x ==<br />
=== Search latest php53-mapi.rpm ===<br />
<br />
SME8 uses PHP5.3<br><br />
Unfortunately, PHP 5.1 and PHP 5.3 are ABI incompatible, that means that PHP modules that were compiled for PHP 5.1 (like the php-mapi.rpm compiled in the Zarafa-rpms for RHEL 5) can not be run using PHP 5.3 :<br><br />
<br />
https://community.zarafa.com/pg/blog/read/1837/support-for-php-53-in-rhel-5-via-new-php53mapi-rpm-package<br />
<br />
So, search on the EPEL-repositories <u>'''the latest''' php53-mapi-package</u>.<br />
<br />
https://admin.fedoraproject.org/updates/search/php53-mapi?<br />
<br />
=== Set the epel-repository (incl. epel-testing) :===<br />
<br />
/sbin/e-smith/db yum_repositories set epel repository \<br />
Name 'Epel - EL5' \<br />
BaseUrl 'http://download.fedoraproject.org/pub/epel/5/$basearch' \<br />
MirrorList 'http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch' \<br />
EnableGroups no \<br />
GPGCheck yes \<br />
GPGKey http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL \<br />
Visible no \<br />
status disabled <br />
<br />
/sbin/e-smith/db yum_repositories set epel-testing repository \<br />
Name 'Epel-testing - EL5' \<br />
BaseUrl 'http://download.fedoraproject.org/pub/epel/testing/5/$basearch' \<br />
MirrorList 'http://mirrors.fedoraproject.org/mirrorlist?repo=testing-epel5&arch=$basearch' \<br />
EnableGroups no \<br />
GPGCheck yes \<br />
GPGKey http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL \<br />
Visible no \<br />
status disabled <br />
<br />
signal-event yum-modify<br />
<br />
=== Download via the Zarafawebsite the package for ZCP <u>''corresponding'' with the php53-mapi.rpm (cf. version above !!)</u> ===<br />
<br />
Make an installdirectory (ex. : /root/InstallZarafa)<br />
<br />
mkdir -p /root/InstallZarafa<br />
<br />
Go (cd /...) to the installdirectory (ex. : /root/InstallZarafa) : <br />
<br />
cd /to the installdirectory<br />
<br />
ex.: <br />
<br />
cd /root/InstallZarafa<br />
<br />
wget http://download.zarafa.com/community/final/7.0/[version]/zcp-[version]-rhel-5-[cpu-arch]-free.tar.gz<br />
<br />
The 'free'-version has the ability to connect with Microsoft Outlook (default 3 users for free, buy zarafa-CAL's if you want more).<br />
<br />
=== Unpack the corresponding package for ZCP :===<br />
<br />
tar -zxvf zcp-*<br />
<br />
=== Remove the devel packages ===<br />
Go (cd ./zcp-...) to the created subdirectory (zcp-...) :<br />
<br />
cd ./zcp- ... <br />
rm -f *-dev*.rpm<br />
<br />
Move the windows-directory to an installshare in your network<br />
<br />
=== Download the latest webapp.rpm too in the same subdirectory :===<br />
<br />
wget http://download.zarafa.com/community/final/WebApp/[version]/rhel/[zarafa-webapp-version.noarch.rpm]<br />
<br />
=== Install all rpm's in the unpacked package of ZCP and the webapp.rpm too :===<br />
<br />
yum localinstall *.rpm<br />
<br />
All packages have dependencies that cannot be resolved if you install only part of the rpm's.<br />
<br />
=== Remove the default php-mapi.rpm ===<br />
<br />
We have to remove the installation of the default php-mapi (because it's not built for php 5.3).<br />
<br />
rpm -e php-mapi --nodeps<br />
<br />
=== Install the php53-mapi.rpm ===<br />
-If you downloaded the rpm :<br />
<br />
rpm -Uvh --force php53-mapi<br />
<br />
-If you did set the EPEL-repository :<br />
<br />
yum install php53-mapi --enablerepo=epel --enablerepo=epel-testing<br />
<br />
=== Make install/update-actions ===<br />
==== INSTALLSCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/zarafa-install =====<br />
<br />
<nowiki><br />
#!/usr/bin/env bash<br />
clear<br />
<br />
if [ `whoami` != "root" ]; then<br />
echo "This installation must be run as user root."<br />
echo "Become root, and run this script again."<br />
echo<br />
exit 1<br />
fi<br />
<br />
##########################################<br />
# Creating some Zarafa-actions<br />
##########################################<br />
<br />
#<br />
#--- zarafa-expand-templates ---<br />
#<br />
echo<br />
echo "Creating zarafa-expand-templates-action ..."<br />
echo<br />
cat <<HERE1 > /etc/e-smith/events/actions/zarafa-expand-templates<br />
#!/bin/sh<br />
/sbin/e-smith/expand-template /etc/zarafa/gateway.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/ical.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/server.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/unix.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/monitor.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/indexer.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/spooler.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/dagent.cfg<br />
/sbin/e-smith/expand-template /etc/zarafa/licensed.cfg<br />
/etc/e-smith/events/actions/qmail-update-user<br />
HERE1<br />
<br />
<br />
#<br />
#--- zarafa-services ---<br />
#<br />
echo<br />
echo "Creating zarafa-services-action ..."<br />
echo<br />
cat <<HERE2 > /etc/e-smith/events/actions/zarafa-services<br />
#!/bin/sh<br />
FILE=/etc/rc.d/init.d/zarafa-licensed<br />
if [ "\$1" == start ]; then<br />
/etc/rc.d/init.d/zarafa-dagent start<br />
/etc/rc.d/init.d/zarafa-gateway start<br />
/etc/rc.d/init.d/zarafa-ical start<br />
if [ -a \$FILE ]; then \$FILE start; fi<br />
/etc/rc.d/init.d/zarafa-monitor start<br />
/etc/rc.d/init.d/zarafa-spooler start<br />
/etc/rc.d/init.d/zarafa-indexer start<br />
/etc/rc.d/init.d/zarafa-server start<br />
exit 0<br />
fi<br />
if [ "\$1" == stop ]; then<br />
/etc/rc.d/init.d/zarafa-dagent stop<br />
/etc/rc.d/init.d/zarafa-gateway stop<br />
/etc/rc.d/init.d/zarafa-ical stop<br />
if [ -a \$FILE ]; then \$FILE stop; fi<br />
/etc/rc.d/init.d/zarafa-indexer stop<br />
/etc/rc.d/init.d/zarafa-spooler stop<br />
/etc/rc.d/init.d/zarafa-server stop<br />
/etc/rc.d/init.d/zarafa-monitor stop <br />
exit 0<br />
fi<br />
if [ "\$1" == restart ]; then<br />
/etc/rc.d/init.d/zarafa-dagent stop<br />
/etc/rc.d/init.d/zarafa-gateway stop<br />
/etc/rc.d/init.d/zarafa-ical stop<br />
if [ -a \$FILE ]; then \$FILE stop; fi<br />
/etc/rc.d/init.d/zarafa-monitor stop<br />
/etc/rc.d/init.d/zarafa-indexer stop<br />
/etc/rc.d/init.d/zarafa-spooler stop<br />
/etc/rc.d/init.d/zarafa-server stop<br />
/etc/rc.d/init.d/zarafa-dagent start<br />
/etc/rc.d/init.d/zarafa-gateway start<br />
/etc/rc.d/init.d/zarafa-ical start<br />
if [ -a \$FILE ]; then \$FILE start; fi<br />
/etc/rc.d/init.d/zarafa-monitor start<br />
/etc/rc.d/init.d/zarafa-server start<br />
/etc/rc.d/init.d/zarafa-spooler start<br />
/etc/rc.d/init.d/zarafa-indexer start<br />
exit 0<br />
fi<br />
if [ "\$1" == enabled ]; then<br />
config setprop zarafa-gateway status enabled<br />
config setprop zarafa-ical status enabled<br />
if [ -a \$FILE ]; then config setprop zarafa-licensed status enabled; fi<br />
config setprop zarafa-monitor status enabled<br />
config setprop zarafa-server status enabled<br />
config setprop zarafa-spooler status enabled<br />
config setprop zarafa-indexer status enabled<br />
config setprop zarafa-dagent status enabled<br />
exit 0<br />
fi<br />
if [ "\$1" == disabled ]; then<br />
config setprop zarafa-gateway status disabled<br />
config setprop zarafa-ical status disabled<br />
if [ -a \$FILE ]; then config setprop zarafa-licensed status disabled; fi<br />
config setprop zarafa-monitor status disabled<br />
config setprop zarafa-server status disabled<br />
config setprop zarafa-spooler status disabled<br />
config setprop zarafa-indexer status disabled<br />
config setprop zarafa-dagent status disabled<br />
exit 0<br />
fi<br />
echo "Usage: start|stop|restart|enabled|disabled"<br />
exit 0<br />
HERE2<br />
<br />
<br />
#<br />
#--- zarafa-create-user-action ---<br />
#<br />
echo<br />
echo "Creating zarafa-create-user-action ..."<br />
echo<br />
cat <<HERE3 > /etc/e-smith/events/actions/zarafa-create-user<br />
#!/bin/sh<br />
clear<br />
/bin/echo "Enter the username of the ZARAFA-user"<br />
/bin/echo "If you have a multicompany-setup, format of the SME-username and the ZARAFA-username"<br />
/bin/echo "has to be [username].[companyname] !!!"<br />
read USERNAME<br />
/bin/echo "Enter password:"<br />
read PASSWORD<br />
/bin/echo "Enter e-mail address:"<br />
read EMAIL<br />
/bin/echo "Enter full name:"<br />
read FULLNAME<br />
/bin/echo "Executing..."<br />
/usr/bin/zarafa-admin -c "\$USERNAME" -p "\$PASSWORD" -e "\$EMAIL" -f "\$FULLNAME"<br />
/usr/bin/zarafa-admin -l<br />
/sbin/e-smith/db accounts setprop \$USERNAME zarafa enabled <br />
/etc/e-smith/events/actions/qmail-update-user<br />
HERE3<br />
<br />
<br />
#<br />
#--- zarafa-create-company-action ---<br />
#<br />
echo<br />
echo "Creating zarafa-create-company-action ..."<br />
echo<br />
cat <<HERE4 > /etc/e-smith/events/actions/zarafa-create-company<br />
#!/bin/sh<br />
clear<br />
/bin/echo "Enter the companyname :"<br />
read COMPANYNAME<br />
/bin/echo "Executing..."<br />
/usr/bin/zarafa-admin --create-company "\$COMPANYNAME"<br />
HERE4<br />
<br />
<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-expand-templates<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-services<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-create-user<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-create-company<br />
<br />
#<br />
#--- zarafa-configuration-helper-action ---<br />
#<br />
echo<br />
echo "Creating zarafa-configuration-helper-action ..."<br />
echo<br />
cat <<HERE5 > /etc/e-smith/events/actions/helpers.inc<br />
# -*- Mode: sh -*-<br />
replace() {<br />
file=\$1<br />
option=\$2<br />
value=\$3<br />
<br />
# escape &-signs, and % for sed<br />
value=\`echo \$value | sed -e 's/\&/\\\\\&/g' -e 's/\%/\\\\\%/g'\`<br />
sed -i -e "s%\([[:space:]]*\$option[[:space:]]*=[[:space:]]*\).*%\1\$value%" \$file<br />
<br />
}<br />
HERE5<br />
<br />
. /etc/e-smith/events/actions/helpers.inc<br />
<br />
##########################################<br />
# Creating zarafa-db-creation-templates<br />
##########################################<br />
<br />
#<br />
#--- /etc/e-smith/db/configuration/migrate/80zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/db/configuration/migrate/80zarafa ..."<br />
echo<br />
cat <<HERE6 > /etc/e-smith/db/configuration/migrate/80zarafa<br />
{<br />
use MIME::Base64 qw(encode_base64);<br />
<br />
my \$rec = \$DB->get('zarafa-server') || \$DB->new_record('zarafa-server', {type => 'service'});<br />
<br />
my \$pw = \$rec->prop('DbPassword');<br />
return "" if \$pw;<br />
<br />
\$rec->set_prop('DbPassword', sprintf("%15.0f", int( (1000000000000000) * rand() )));<br />
}<br />
HERE6<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/e-smith/sql/init/80zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/e-smith/sql/init/80zarafa ..."<br />
echo<br />
cat <<HERE7 > /etc/e-smith/templates/etc/e-smith/sql/init/80zarafa<br />
{<br />
my \$db = \${'zarafa-server'}{DbName} || 'zarafa';<br />
my \$user = \${'zarafa-server'}{DbUser} || 'zarafa';<br />
my \$pass = \${'zarafa-server'}{DbPassword} || 'changeme';<br />
\$OUT .= <<END<br />
#! /bin/sh<br />
if [ -d /var/lib/mysql/\$db ]; then<br />
exit<br />
fi<br />
/usr/bin/mysql <<EOF<br />
CREATE DATABASE \$db DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
use \$db;<br />
<br />
use mysql;<br />
GRANT ALL PRIVILEGES ON \$db.* TO \$user\@localhost<br />
IDENTIFIED BY '\$pass';<br />
flush privileges;<br />
EOF<br />
END<br />
}<br />
HERE7<br />
<br />
#<br />
#--- /etc/e-smith/templates.metadata/etc/e-smith/sql/init/80zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates.metadata/etc/e-smith/sql/init/80zarafa ..."<br />
echo<br />
cat <<HERE8 > /etc/e-smith/templates.metadata/etc/e-smith/sql/init/80zarafa<br />
PERMS=0750<br />
HERE8<br />
<br />
##########################################<br />
# Creating SME-HTTPD-templates<br />
##########################################<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ..."<br />
echo<br />
cat <<HERE9 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases<br />
{<br />
# vim: ft=perl:<br />
<br />
\$haveSSL = (exists \${modSSL}{status} and \${modSSL}{status} eq "enabled") ? 'yes' : 'no';<br />
my \$zwebmailStatus = \$zarafa{'status'} || "disabled";<br />
my \$zwebmailAccessType = \$zarafa{'access'} || "SSL";<br />
<br />
my \$dirs;<br />
\$dirs{zarafa} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webaccess} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webmail} = '/usr/share/zarafa-webaccess';<br />
if (\$imp{'status'} eq 'enabled') {\$dirs{webmail} = ''};<br />
\$dirs{webapp} = '/usr/share/zarafa-webapp';<br />
<br />
return " # Zarafa is disabled in this VirtualHost\n"<br />
unless \$zwebmailStatus eq 'enabled';<br />
<br />
foreach \$place ('zarafa','webmail','webaccess','webapp')<br />
{<br />
if ((\$port eq "80") && (\$haveSSL eq 'yes') && (\$zwebmailAccessType eq 'SSL'))<br />
{<br />
\$OUT .= " RewriteRule ^/\$place(/.*|\\$) https://%{HTTP_HOST}/\$place\\\$1 [L,R]\n";<br />
} else {<br />
if ((\$dirs{\$place}) ne '') {\$OUT .= " Alias /\$place \$dirs{\$place}\n"};<br />
}<br />
} <br />
}<br />
HERE9<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ..."<br />
echo<br />
cat <<HERE10 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias<br />
{<br />
my \$zstatus = \$zarafa{'status'};<br />
<br />
if (defined \$zstatus && \$zstatus eq 'enabled')<br />
{<br />
\$OUT .= qq(<br />
#--------------------------------------------------------------------<br />
# Zarafa specific configuration files.<br />
#--------------------------------------------------------------------<br />
<br />
Alias /zarafa /usr/share/zarafa-webaccess/<br />
<Directory /usr/share/zarafa-webaccess/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
Alias /webapp /usr/share/zarafa-webapp/<br />
<Directory /usr/share/zarafa-webapp/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
);<br />
} <br />
else<br />
{<br />
\$OUT .= "# Zarafa Webmail is not configured as it is disabled in the config db";<br />
}<br />
}<br />
HERE10<br />
<br />
##########################################<br />
# Creating SME-QMAIL-user-templates<br />
##########################################<br />
<br />
#<br />
#--- /etc/e-smith/templates-user/.qmail/80Zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates-user/.qmail/80Zarafa ..."<br />
echo<br />
cat <<HERE11 > /etc/e-smith/templates-user/.qmail/80Zarafa<br />
{<br />
my \$zarafa = \$user->prop('zarafa') || 'disabled';<br />
my \$zarafa2 = \${'zarafa-server'}{GlobalForward} || 'disabled';<br />
<br />
if (\$zarafa eq 'enabled' || \$zarafa2 eq 'enabled')<br />
{ return "| /usr/bin/zarafa-dagent -q \$USERNAME ; if [ \\$\\? -ne 0 ] ; then exit -1; else exit 99; fi;"<br />
}<br />
}<br />
HERE11<br />
<br />
#<br />
#--- /etc/e-smith/templates-user/.qmail-junkmail/01Zarafa ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates-user/.qmail-junkmail/01Zarafa ..."<br />
echo<br />
cat <<HERE12 > /etc/e-smith/templates-user/.qmail-junkmail/01Zarafa<br />
{<br />
# vim: ft=perl:<br />
die "USERNAME not set." unless defined (\$USERNAME);<br />
<br />
use esmith::AccountsDB;<br />
\$adb = esmith::AccountsDB->open_ro or die "Couldn't open AccountsDB";<br />
<br />
\$user = \$adb->get(\$USERNAME) or die "No user \$USERNAME in AccountsDB";<br />
<br />
my \$zarafa = \$user->prop('zarafa') || 'disabled';<br />
my \$zarafa2 = \${'zarafa-server'}{GlobalForward} || 'disabled';<br />
return "| /usr/bin/zarafa-dagent -qj \$USERNAME ; if [ \\$\\? -ne 0 ] ; then exit -1; else exit 99; fi;"<br />
if (\$zarafa eq 'enabled' || \$zarafa2 eq 'enabled');<br />
}<br />
HERE12<br />
<br />
<br />
##########################################<br />
# Creating Zarafa-configuration-templates<br />
##########################################<br />
<br />
#<br />
#--- unix config ---<br />
#<br />
echo<br />
echo "Creating zarafa-unix-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/unix.cfg<br />
cat <<HERE13 > /etc/e-smith/templates/etc/zarafa/unix.cfg/unix.cfg<br />
{<br />
use esmith::AccountsDB<br />
}<br />
##############################################################<br />
# UNIX USER PLUGIN SETTINGS<br />
#<br />
# Any of these directives that are required, are only required if the<br />
# userplugin parameter is set to unix.<br />
<br />
# Charset used in /etc/passwd for the fullname of a user. Normally this<br />
# is us-ascii, but this can differ according to your setup.<br />
# The charset specified here must be supported by your iconv(1)<br />
# setup. See iconv -l for all charsets.<br />
fullname_charset = iso-8859-15<br />
<br />
# Default email domain for constructing new users<br />
# Required, no default<br />
default_domain = { \${'zarafa-server'}{DomainName} || \$DomainName; }<br />
<br />
# The lowest user id that is considered a regular user<br />
# Optional, default = 1000<br />
min_user_uid = 101<br />
<br />
# The highest user id that is considered a regular user<br />
# Optional, default = 10000<br />
max_user_uid = 10000<br />
<br />
# A list of user ids that are not considered to be regular users<br />
# Optional, default = empty<br />
# except_user_uids =<br />
except_user_uids = {<br />
\$accounts = esmith::AccountsDB->open_ro or die "Could not open AccountsDB";<br />
{<br />
while ((\$name, \$passwd, \$uid, \$gid, \$quota,<br />
\$comment, \$gcos, \$dir, \$shell) = getpwent())<br />
{<br />
\$user = \$accounts->get(\$name);<br />
<br />
\$OUT .= "\$uid "<br />
unless \$uid <= 101 or (defined \$user and \$user->prop('type') eq "user");<br />
}<br />
}<br />
}<br />
<br />
# The lowest group id that is considered a regular group<br />
# Optional, default = 1000<br />
min_group_gid = 5000<br />
<br />
# The highest group id that is considered a regular group<br />
# Optional, default = 10000<br />
max_group_gid = 10000<br />
<br />
# A list of group ids that are not considered to be regular groups<br />
# Optional, default = empty<br />
# except_group_gids =<br />
except_group_gids = {<br />
setpwent();<br />
while ((\$name, \$passwd, \$uid, \$gid, \$quota,<br />
\$comment, \$gcos, \$dir, \$shell) = getpwent())<br />
{<br />
\$group = \$accounts->get(\$name);<br />
<br />
\$OUT .= "\$gid "<br />
unless \$gid < 5000 or (defined \$group and \$group->prop('type') eq "group");<br />
}<br />
endpwent();<br />
}<br />
<br />
# Create a user as non-active when it has this unix shell<br />
non_login_shell = /bin/false<br />
HERE13<br />
<br />
<br />
#<br />
#--- sysconfig config ---<br />
#<br />
echo<br />
echo "Creating zarafa-sysconfig-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/sysconfig/zarafa<br />
cat /etc/sysconfig/zarafa | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa<br />
replace /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa ZARAFA_LOCALE '"{ ${'\''zarafa'\''}{language} || '\''en_US.UTF-8'\'' ; }"'<br />
replace /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa ZARAFA_USERSCRIPT_LOCALE '"{ ${'\''zarafa'\''}{language} || '\''en_US.UTF-8'\'' ; }"'<br />
<br />
<br />
#<br />
#--- licensed config ---<br />
#<br />
echo<br />
echo "Creating zarafa-licensed-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/licensed.cfg<br />
cat /usr/share/doc/zarafa-licensed/example-config/licensed.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_method '{ ${'\''zarafa-licensed'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_level '{ ${'\''zarafa-licensed'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_timestamp '{ ${'\''zarafa-licensed'\''}{log_timestamp} || '\''1'\''; }'<br />
<br />
#<br />
#--- server config ---<br />
#<br />
echo<br />
echo "Creating zarafa-server-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/server.cfg<br />
cat /usr/share/doc/zarafa/example-config/server.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_tcp_enabled '{ ${'\''zarafa-server'\''}{server_tcp_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_tcp_port '{ ${'\''zarafa-server'\''}{TCPPort} || '\''236'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_pipe_enabled '{ ${'\''zarafa-server'\''}{server_pipe_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_name '{ ${'\''zarafa-server'\''}{server_name} || '\''Zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg database_engine '{ ${'\''zarafa-server'\''}{database_engine} || '\''mysql'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg allow_local_users '{ ${'\''zarafa-server'\''}{allow_local_users} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg local_admin_users '{ ${'\''zarafa-server'\''}{local_admin_users} || '\''root'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg system_email_address '{ ${'\''zarafa-server'\''}{system_email_address} || '\''postmaster@localhost'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg session_timeout '{ ${'\''zarafa-server'\''}{session_timeout} || '\''300'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg license_timeout '{ ${'\''zarafa-server'\''}{license_timeout} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_method '{ ${'\''zarafa-server'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_level '{ ${'\''zarafa-server'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_timestamp '{ ${'\''zarafa-server'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_enabled '{ ${'\''zarafa-server'\''}{audit_log_enabled} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_level '{ ${'\''zarafa-server'\''}{audit_log_level} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_timestamp '{ ${'\''zarafa-server'\''}{audit_log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_host '{ ${'\''zarafa-server'\''}{mysql_host} || '\''localhost'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_port '{ ${'\''zarafa-server'\''}{mysql_port} || '\''3306'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_user '{ ${'\''zarafa-server'\''}{DbUser} || '\''zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_password '{ ${'\''zarafa-server'\''}{DbPassword}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_database '{ ${'\''zarafa-server'\''}{DbName} || '\''zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_storage '{ ${'\''zarafa-server'\''}{attachment_storage} || '\''files'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_path '/home/e-smith/files/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_compression '{ ${'\''zarafa-server'\''}{attachment_compression} || '\''6'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_enabled '{ ${'\''zarafa-ssl'\''}{server_ssl_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_port '{ ${'\''zarafa-ssl'\''}{TCPPort} || '\''237'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_key_file '/home/e-smith/ssl.pem/{$SystemName}.{$DomainName}.pem'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_key_pass '{ ${'\''zarafa-server'\''}{DbPassword}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_ca_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_ca_path '/home/e-smith/ssl.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sslkeys_path '/home/e-smith/ssl.pem'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg threads '{ ${'\''zarafa-server'\''}{threads} || '\''8'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg watchdog_frequency '{ ${'\''zarafa-server'\''}{watchdog_frequency} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg watchdog_max_age '{ ${'\''zarafa-server'\''}{watchdog_max_age} || '\''500'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_max_keep_alive_requests '{ ${'\''zarafa-server'\''}{server_max_keep_alive_requests} || '\''100'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_recv_timeout '{ ${'\''zarafa-server'\''}{server_recv_timeout} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_read_timeout '{ ${'\''zarafa-server'\''}{server_read_timeout} || '\''60'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_send_timeout '{ ${'\''zarafa-server'\''}{server_send_timeout} || '\''60'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg softdelete_lifetime '{ ${'\''zarafa-server'\''}{softdelete_lifetime} || '\''30'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_lifetime '{ ${'\''zarafa-server'\''}{sync_lifetime} || '\''365'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_log_all_changes '{ ${'\''zarafa-server'\''}{sync_log_all_changes} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_sso '{ ${'\''zarafa-server'\''}{enable_sso} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_gab '{ ${'\''zarafa-server'\''}{enable_gab} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg auth_method '{ ${'\''zarafa-server'\''}{auth_method} || '\''plugin'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg pam_service '{ ${'\''zarafa-server'\''}{pam_service} || '\''passwd'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_cell_size '{ ${'\''zarafa-server'\''}{cache_cell_size} || '\''268435456'\''; }' <br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_object_size '{ ${'\''zarafa-server'\''}{cache_object_size} || '\''5242880'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_indexedobject_size '{ ${'\''zarafa-server'\''}{cache_indexedobject_size} || '\''16777216'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_quota_size '{ ${'\''zarafa-server'\''}{cache_quota_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_quota_lifetime '{ ${'\''zarafa-server'\''}{cache_quota_lifetime} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_acl_size '{ ${'\''zarafa-server'\''}{cache_acl_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_store_size '{ ${'\''zarafa-server'\''}{cache_store_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_user_size '{ ${'\''zarafa-server'\''}{cache_user_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_userdetails_size '{ ${'\''zarafa-server'\''}{cache_userdetails_size} || '\''26214400'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_userdetails_lifetime '{ ${'\''zarafa-server'\''}{cache_userdetails_lifetime} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_server_size '{ ${'\''zarafa-server'\''}{cache_server_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_server_lifetime '{ ${'\''zarafa-server'\''}{cache_server_lifetime} || '\''30'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_warn '{ ${'\''zarafa-server'\''}{quota_warn} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_soft '{ ${'\''zarafa-server'\''}{quota_soft} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_hard '{ ${'\''zarafa-server'\''}{quota_hard} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg companyquota_warn '{ ${'\''zarafa-server'\''}{companyquota_warn} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_plugin '{ ${'\''zarafa-server'\''}{user_plugin} || '\''db'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_plugin_config '{ ${'\''zarafa-server'\''}{user_plugin_config}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_safe_mode '{ ${'\''zarafa-server'\''}{user_safe_mode} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg thread_stacksize '{ ${'\''zarafa-server'\''}{thread_stacksize} || '\''512'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_hosted_zarafa '{ ${'\''zarafa-server'\''}{enable_hosted_zarafa} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_distributed_zarafa '{ ${'\''zarafa-server'\''}{enable_distributed_zarafa} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg storename_format '{ ${'\''zarafa-server'\''}{storename_format} || '\''%f'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg loginname_format '{ ${'\''zarafa-server'\''}{loginname_format} || '\''%u'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_enabled '{ ${'\''zarafa-server'\''}{client_update_enabled} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_path '{ ${'\''zarafa-server'\''}{client_update_path} || '\''/var/lib/zarafa/client'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_log_level '{ ${'\''zarafa-server'\''}{client_update_log_level} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg hide_everyone '{ ${'\''zarafa-server'\''}{hide_everyone} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg hide_system '{ ${'\''zarafa-server'\''}{hide_system} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_enabled '{ ${'\''zarafa-server'\''}{index_services_enabled} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_search_timeout '{ ${'\''zarafa-server'\''}{index_services_search_timeout} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_prefix_chars '{ ${'\''zarafa-server'\''}{index_services_prefix_chars} || '\''3'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_enhanced_ics '{ ${'\''zarafa-server'\''}{enable_enhanced_ics} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_gab_realtime '{ ${'\''zarafa-server'\''}{sync_gab_realtime} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg disabled_features '{ ${'\''zarafa-server'\''}{disabled_features}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg max_deferred_records '{ ${'\''zarafa-server'\''}{max_deferred_records} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg max_deferred_records_folder '{ ${'\''zarafa-server'\''}{max_deferred_records_folder} || '\''20'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg coredump_enabled '{ ${'\''zarafa-server'\''}{coredump_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_enable_v2 '{ ${'\''zarafa-server'\''}{server_ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- dagent config ---<br />
#<br />
echo<br />
echo "Creating zarafa-dagent-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/dagent.cfg<br />
cat /usr/share/doc/zarafa-dagent/example-config/dagent.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_method '{ ${'\''zarafa-dagent'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_level '{ ${'\''zarafa-dagent'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_timestamp '{ ${'\''zarafa-dagent'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_raw_message '{ ${'\''zarafa-dagent'\''}{log_raw_message} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg lmtp_port '{ ${'\''zarafa-dagent'\''}{lmtp_port} || '\''2003'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg lmtp_max_threads '{ ${'\''zarafa-dagent'\''}{lmtp_max_threads} || '\''20'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg process_model '{ ${'\''zarafa-dagent'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg spam_header_name '{ ${'\''zarafa-dagent'\''}{spam_header_name} || '\''X-Spam-Status'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg spam_header_value '{ ${'\''zarafa-dagent'\''}{spam_header_value} || '\''Yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg archive_on_delivery '{ ${'\''zarafa-dagent'\''}{archive_on_delivery} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg set_rule_headers '{ ${'\''zarafa-dagent'\''}{set_rule_headers} || '\''yes'\''; }'<br />
<br />
<br />
#<br />
#--- spooler config ---<br />
#<br />
echo<br />
echo "Creating zarafa-spooler-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/spooler.cfg<br />
cat /usr/share/doc/zarafa-spooler/example-config/spooler.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg smtp_port '{ ${'\''zarafa-spooler'\''}{smtp_port} || '\''25'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_method '{ ${'\''zarafa-spooler'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_level '{ ${'\''zarafa-spooler'\''}{log_level} || '\''3'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_timestamp '{ ${'\''zarafa-spooler'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg max_threads '{ ${'\''zarafa-spooler'\''}{max_threads} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg fax_domain '{ ${'\''zarafa-spooler'\''}{fax_domain} || '\''fax.local'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg fax_international '{ ${'\''zarafa-spooler'\''}{fax_international} || '\''00'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_delegates '{ ${'\''zarafa-spooler'\''}{always_send_delegates} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_redirect_spoofing '{ ${'\''zarafa-spooler'\''}{allow_redirect_spoofing} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg copy_delegate_mails '{ ${'\''zarafa-spooler'\''}{copy_delegate_mails} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_delegate_meeting_request '{ ${'\''zarafa-spooler'\''}{allow_delegate_meeting_request} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_send_to_everyone '{ ${'\''zarafa-spooler'\''}{allow_send_to_everyone} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_tnef '{ ${'\''zarafa-spooler'\''}{always_send_tnef} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_utf8 '{ ${'\''zarafa-spooler'\''}{always_send_utf8} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg charset_upgrade '{ ${'\''zarafa-spooler'\''}{charset_upgrade} || '\''windows-1252'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg expand_groups '{ ${'\''zarafa-spooler'\''}{expand_groups} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg archive_on_send '{ ${'\''zarafa-spooler'\''}{archive_on_send} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- monitor config ---<br />
#<br />
echo<br />
echo "Creating zarafa-monitor-configuration-template ..."<br />
echo "The monitor program sends quota warning mails to users who are over quota."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/monitor.cfg<br />
cat /usr/share/doc/zarafa-monitor/example-config/monitor.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_method '{ ${'\''zarafa-monitor'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_level '{ ${'\''zarafa-monitor'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_timestamp '{ ${'\''zarafa-monitor'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg quota_check_interval '{ ${'\''zarafa-monitor'\''}{quota_check_interval} || '\''15'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg mailquota_resend_interval '{ ${'\''zarafa-monitor'\''}{mailquota_resend_interval} || '\''1'\''; }'<br />
<br />
<br />
#<br />
#--- gateway config ---<br />
#<br />
echo<br />
echo "Creating zarafa-gateway-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/gateway.cfg<br />
cat /usr/share/doc/zarafa-gateway/example-config/gateway.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg server_socket 'http://localhost:{${'\''zarafa-server'\''}{TCPPort}||'\''236'\'';}/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3_enable '{ if (${'\''zarafa-pop3'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3_port '{ ${'\''zarafa-pop3'\''}{TCPPort} || '\''8110'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3s_enable '{ if (${'\''zarafa-pop3s'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3s_port '{ ${'\''zarafa-pop3s'\''}{TCPPort} || '\''8995'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_enable '{ if (${'\''zarafa-imap'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_port '{ ${'\''zarafa-imap'\''}{TCPPort} || '\''8143'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imaps_enable '{ if (${'\''zarafa-imaps'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imaps_port '{ ${'\''zarafa-imaps'\''}{TCPPort} || '\''8993'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_only_mailfolders '{ ${'\''zarafa-imap'\''}{imap_only_mailfolders} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_public_folders '{ ${'\''zarafa-imap'\''}{imap_public_folders} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_capability_idle '{ ${'\''zarafa-imap'\''}{imap_capability_idle} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_max_messagesize '{ ${'\''zarafa-imap'\''}{imap_max_messagesize} || '\''134217728'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_generate_utf8 '{ ${'\''zarafa-imap'\''}{imap_generate_utf8} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_expunge_on_delete '{ ${'\''zarafa-imap'\''}{imap_expunge_on_delete} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_store_rfc822 '{ ${'\''zarafa-imap'\''}{imap_store_rfc822} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_private_key_file '/home/e-smith/ssl.key/{$SystemName}.{$DomainName}.key'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_certificate_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_verify_client '{ ${'\''zarafa-gateway'\''}{ssl_verify_client} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg process_model '{ ${'\''zarafa-gateway'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_method '{ ${'\''zarafa-gateway'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_level '{ ${'\''zarafa-gateway'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_timestamp '{ ${'\''zarafa-gateway'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_enable_v2 '{ ${'\''zarafa-gateway'\''}{ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- ical config ---<br />
#<br />
echo<br />
echo "Creating zarafa-ical-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/ical.cfg<br />
cat /usr/share/doc/zarafa-ical/example-config/ical.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ical_enable '{ if (${'\''zarafa-ical'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ical_port '{ ${'\''zarafa-ical'\''}{TCPPort} || '\''8088'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg icals_enable '{ if (${'\''zarafa-icals'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg icals_port '{ ${'\''zarafa-icals'\''}{TCPPort} || '\''8089'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg server_socket 'http://localhost:{${'\''zarafa-server'\''}{TCPPort}||'\''236'\'';}/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg process_model '{ ${'\''zarafa-ical'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_method '{ ${'\''zarafa-ical'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_level '{ ${'\''zarafa-ical'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_timestamp '{ ${'\''zarafa-ical'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_private_key_file '/home/e-smith/ssl.key/{$SystemName}.{$DomainName}.key'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_certificate_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_verify_client '{ ${'\''zarafa-ical'\''}{ssl_verify_client} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg server_timezone '{$TimeZone}'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg default_charset '{ ${'\''zarafa-ical'\''}{default_charset} || '\''utf-8'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg enable_ical_get '{ ${'\''zarafa-ical'\''}{enable_ical_get} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_enable_v2 '{ ${'\''zarafa-ical'\''}{ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- indexer config ---<br />
#<br />
echo<br />
echo "Creating zarafa-indexer-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/indexer.cfg<br />
cat /usr/share/doc/zarafa-indexer/example-config/indexer.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg cleanup_lockfiles '{ ${'\''zarafa-indexer'\''}{cleanup_lockfiles} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg limit_results '{ ${'\''zarafa-indexer'\''}{limit_results} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_method '{ ${'\''zarafa-indexer'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_level '{ ${'\''zarafa-indexer'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_timestamp '{ ${'\''zarafa-indexer'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_interval '{ ${'\''zarafa-indexer'\''}{index_interval} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_threads '{ ${'\''zarafa-indexer'\''}{index_threads} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_field_length '{ ${'\''zarafa-indexer'\''}{index_max_field_length} || '\''10000'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_merge_factor '{ ${'\''zarafa-indexer'\''}{index_merge_factor} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_buffered_docs '{ ${'\''zarafa-indexer'\''}{index_max_buffered_docs} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_min_merge_docs '{ ${'\''zarafa-indexer'\''}{index_min_merge_docs} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_merge_docs '{ ${'\''zarafa-indexer'\''}{index_max_merge_docs} || '\''2147483647'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_term_interval '{ ${'\''zarafa-indexer'\''}{index_term_interval} || '\''128'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_cache_timeout '{ ${'\''zarafa-indexer'\''}{index_cache_timeout} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachments '{ ${'\''zarafa-indexer'\''}{index_attachments} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_max_size '{ ${'\''zarafa-indexer'\''}{index_attachment_max_size} || '\''5120'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_parser_max_memory '{ ${'\''zarafa-indexer'\''}{index_attachment_parser_max_memory} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_parser_max_cputime '{ ${'\''zarafa-indexer'\''}{index_attachment_parser_max_cputime} || '\''0'\''; }'<br />
<br />
<br />
######################################<br />
# Configuring SME-events : Templates to expand<br />
######################################<br />
<br />
/bin/echo <br />
/bin/echo "Configuring SME-events : Templates2expand"<br />
/bin/echo <br />
mkdir -p /etc/e-smith/events/email-update/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/gateway.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/ical.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/server.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/unix.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/spooler.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/licensed.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/monitor.cfg<br />
touch /etc/e-smith/events/email-update/templates2expand/etc/zarafa/dagent.cfg<br />
<br />
mkdir -p /etc/e-smith/events/group-create/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/group-create/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/group-delete/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/group-delete/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/group-modify/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/group-modify/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/user-create/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/user-create/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/user-delete/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/user-delete/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/user-modify/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/user-modify/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/ibay-create/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/ibay-create/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/machine-account-create/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/machine-account-create/templates2expand/etc/zarafa/unix.cfg<br />
<br />
mkdir -p /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/e-smith/sql/init/80zarafa<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/gateway.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/ical.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/server.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/unix.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/spooler.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/licensed.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/monitor.cfg<br />
touch /etc/e-smith/events/post-upgrade/templates2expand/etc/zarafa/dagent.cfg<br />
<br />
<br />
######################################<br />
# Configuring SME-events : Services to adjust<br />
######################################<br />
<br />
/bin/echo <br />
/bin/echo "Configuring SME-events : Services2adjust"<br />
/bin/echo <br />
mkdir -p /etc/e-smith/events/machine-account-create/services2adjust<br />
ln -s reload /etc/e-smith/events/group-create/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/group-delete/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/group-modify/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/user-create/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/user-delete/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/user-modify/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/ibay-create/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/machine-account-create/services2adjust/zarafa-server<br />
ln -s reload /etc/e-smith/events/timezone-update/services2adjust/zarafa-server<br />
<br />
<br />
######################################<br />
# Setting up SME-db-entries<br />
######################################<br />
<br />
/bin/echo <br />
/bin/echo "Enter the language of your choice for your zarafa-mailboxes and public store(s)."<br />
/bin/echo "Values: en_US.UTF-8, en_GB.UTF-8, nl_NL.UTF-8, fr_FR.UTF-8, de_DE.UTF-8, ..."<br />
/bin/echo <br />
read ZARAFALANGUAGE<br />
/sbin/e-smith/config set zarafa service status enabled language $ZARAFALANGUAGE<br />
/sbin/e-smith/expand-template /etc/sysconfig/zarafa<br />
<br />
/bin/echo <br />
/bin/echo "Initialize-default-databases"<br />
/bin/echo <br />
/etc/e-smith/events/actions/initialize-default-databases<br />
<br />
/bin/echo <br />
/bin/echo "Setting up db-entries for Zarafa"<br />
/bin/echo <br />
/sbin/e-smith/db configuration setprop mysqld InnoDB enabled<br />
/sbin/e-smith/db configuration setprop smtpd tnef2mime disabled<br />
/sbin/e-smith/db configuration setprop zarafa-server access private status enabled TCPPort 236 index_services_enabled yes<br />
/bin/echo <br />
/bin/echo "Enter your user plugin."<br />
/bin/echo "Values: unix or db (ldap is not supported, multicompany-support only with db-plugin)."<br />
/bin/echo <br />
read USERPLUGIN<br />
/sbin/e-smith/db configuration setprop zarafa-server user_plugin $USERPLUGIN<br />
<br />
if [ "$USERPLUGIN" == unix ]; then<br />
/sbin/e-smith/db configuration setprop zarafa-server user_plugin_config /etc/zarafa/unix.cfg<br />
fi<br />
<br />
if [ "$USERPLUGIN" == db ]; then<br />
/bin/echo<br />
/bin/echo "Do you want to set up a multicompany-environment ?"<br />
/bin/echo "Values: yes or no."<br />
/bin/echo<br />
read MULTICOMPANY<br />
/sbin/e-smith/db configuration setprop zarafa-server Multicompany $MULTICOMPANY<br />
/sbin/e-smith/db configuration delprop zarafa-server user_plugin_config<br />
if [ "$MULTICOMPANY" == yes ]; then<br />
/sbin/e-smith/db configuration setprop zarafa-server enable_hosted_zarafa true<br />
/sbin/e-smith/db configuration setprop zarafa-server loginname_format %u.%c<br />
else<br />
/sbin/e-smith/db configuration setprop zarafa-server enable_hosted_zarafa false<br />
/sbin/e-smith/db configuration setprop zarafa-server loginname_format %u<br />
fi<br />
fi<br />
<br />
/sbin/e-smith/db configuration setprop zarafa access SSL<br />
/sbin/e-smith/db configuration set zarafa-ical service access private status enabled TCPPort 8088<br />
/sbin/e-smith/db configuration set zarafa-icals service access public status enabled TCPPort 8089<br />
/sbin/e-smith/db configuration set zarafa-imap service access private status enabled TCPPort 8143<br />
/sbin/e-smith/db configuration set zarafa-imaps service access public status enabled TCPPort 8993<br />
/sbin/e-smith/db configuration set zarafa-pop3 service access private status enabled TCPPort 8110<br />
/sbin/e-smith/db configuration set zarafa-pop3s service access public status enabled TCPPort 8995<br />
/sbin/e-smith/db configuration set zarafa-ssl service access public status enabled TCPPort 237<br />
/sbin/e-smith/db configuration set zarafa-gateway service status enabled<br />
/sbin/e-smith/db configuration set zarafa-spooler service status enabled<br />
/sbin/e-smith/db configuration set zarafa-monitor service status enabled<br />
/sbin/e-smith/db configuration set zarafa-indexer service status enabled<br />
/sbin/e-smith/db configuration set zarafa-licensed service status enabled<br />
/sbin/e-smith/db configuration set zarafa-dagent service status enabled<br />
<br />
<br />
######################################<br />
# Setting up the Zarafa-db<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Expanding the my.cnf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/my.cnf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting mysqld"<br />
/bin/echo<br />
/usr/bin/sv t /service/mysqld<br />
<br />
/bin/echo<br />
/bin/echo "Signal-event remoteaccess-update"<br />
/bin/echo<br />
/sbin/e-smith/signal-event remoteaccess-update<br />
<br />
/bin/echo<br />
/bin/echo "Creating the Zarafa-database"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/e-smith/sql/init/80zarafa<br />
/etc/rc.d/init.d/mysql.init start<br />
<br />
<br />
######################################<br />
# Expanding the Zarafa-configuration-templates<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Expanding the Zarafa-configuration-templates"<br />
/bin/echo<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
<br />
<br />
######################################<br />
# Configuration of the Webaccess<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of the Webaccess"<br />
/bin/echo<br />
/bin/chown -R www:www /var/lib/zarafa-webaccess/tmp<br />
/bin/chown -R www:www /var/lib/zarafa-webapp/tmp<br />
FILE=/etc/httpd/conf.d/zarafa-webaccess.conf; if [ -a $FILE ]; then /bin/rm -f $FILE; fi<br />
FILE=/etc/httpd/conf.d/zarafa-webapp.conf; if [ -a $FILE ]; then /bin/rm -f $FILE; fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
<br />
######################################<br />
# Setting up more symbolic links<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Setting up more symbolic links"<br />
/bin/echo<br />
if [ `getconf LONG_BIT` = "64" ]; then<br />
ln -s /usr/lib64/zarafa /usr/lib/zarafa<br />
ln -s /lib64/libcrypto.so.0.9.8e /usr/lib/libcrypto.so.0.9.8<br />
ln -s /lib64/libssl.so.0.9.8e /usr/lib/libssl.so.0.9.8 <br />
else<br />
ln -s /lib/libcrypto.so.0.9.8e /usr/lib/libcrypto.so.0.9.8<br />
ln -s /lib/libssl.so.0.9.8e /usr/lib/libssl.so.0.9.8<br />
fi<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-dagent<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-gateway<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-indexer<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-licensed<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-monitor<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-spooler<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-ical<br />
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-server<br />
<br />
<br />
#######################################<br />
# Installing a license-key<br />
#######################################<br />
<br />
/bin/echo <br />
/bin/echo "Installing a license-key"<br />
/bin/echo <br />
if [ -x /usr/bin/zarafa-licensed ]; then<br />
if [ ! -f /etc/zarafa/license/base ]; then<br />
mkdir -p /etc/zarafa/license<br />
SERIAL="0"<br />
while [ ${#SERIAL} -ne 25 -a ${#SERIAL} -ne 0 ]; do<br />
if [ -n "$SERIAL" ]; then<br />
echo "Serial number must be 25 characters or empty"<br />
fi<br />
echo -ne "Server serial number (leave empty for none) []\t\t: "<br />
read SERIAL<br />
done<br />
SERIAL=`echo $SERIAL | tr [a-z] [A-Z]`<br />
echo $SERIAL > /etc/zarafa/license/base<br />
echo<br />
echo "The correctness of the serial will be checked when the Zarafa-server starts."<br />
echo<br />
fi<br />
fi<br />
<br />
<br />
#######################################<br />
# Starting Zarafa<br />
#######################################<br />
<br />
/bin/echo <br />
/bin/echo "Starting Zarafa-services"<br />
/bin/echo <br />
/etc/e-smith/events/actions/zarafa-services start<br />
<br />
/bin/echo<br />
/bin/echo "Setting permissions on files"<br />
/bin/echo<br />
FILE=/var/log/zarafa/dagent.log; if [ -a $FILE ]; then /bin/chmod 666 $FILE; fi<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-update<br />
<br />
<br />
#######################################<br />
# Creating public store(s)<br />
#######################################<br />
<br />
if [ "$USERPLUGIN" == unix ]; then<br />
/bin/echo<br />
/bin/echo "creating Public store"<br />
/bin/echo<br />
/usr/bin/zarafa-admin --utf8 -s<br />
fi<br />
<br />
if [ "$USERPLUGIN" == db ]; then<br />
if [ "$MULTICOMPANY" == no ]; then<br />
/bin/echo<br />
/bin/echo "creating Public store"<br />
/bin/echo<br />
/usr/bin/zarafa-admin --utf8 -s<br />
fi<br />
fi<br />
<br />
if [ "$USERPLUGIN" == db ]; then<br />
if [ "$MULTICOMPANY" == yes ]; then<br />
/bin/echo<br />
/bin/echo "Make your first company. Enter your first companyname :"<br />
/bin/echo<br />
read COMPANYNAME<br />
/usr/bin/zarafa-admin --create-company "$COMPANYNAME"<br />
/bin/echo<br />
/bin/echo "!!! REMEMBER !!! : for a multicompany-environment the username-format of the SME-user and the ZARAFA-user,"<br />
/bin/echo "has to be : [username].[companyname] !!!"<br />
/bin/echo<br />
fi<br />
fi<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== UPGRADESCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/zarafa-update =====<br />
<br />
<nowiki><br />
#!/bin/sh<br />
<br />
/bin/echo "Stopping the Zarafa-services"<br />
/etc/e-smith/events/actions/zarafa-services stop<br />
<br />
#<br />
#--- zarafa-configuration-helper-action ---<br />
#<br />
echo<br />
echo "Creating zarafa-configuration-helper-action ..."<br />
echo<br />
cat <<HERE1 > /etc/e-smith/events/actions/helpers.inc<br />
# -*- Mode: sh -*-<br />
replace() {<br />
file=\$1<br />
option=\$2<br />
value=\$3<br />
<br />
# escape &-signs, and % for sed<br />
value=\`echo \$value | sed -e 's/\&/\\\\\&/g' -e 's/\%/\\\\\%/g'\`<br />
sed -i -e "s%\([[:space:]]*\$option[[:space:]]*=[[:space:]]*\).*%\1\$value%" \$file<br />
<br />
}<br />
HERE1<br />
<br />
. /etc/e-smith/events/actions/helpers.inc<br />
<br />
#<br />
#--- sysconfig config ---<br />
#<br />
echo<br />
echo "Creating zarafa-sysconfig-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/sysconfig/zarafa<br />
cat /etc/sysconfig/zarafa | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa<br />
replace /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa ZARAFA_LOCALE '"{ ${'\''zarafa'\''}{language} || '\''en_US.UTF-8'\'' ; }"'<br />
replace /etc/e-smith/templates/etc/sysconfig/zarafa/zarafa ZARAFA_USERSCRIPT_LOCALE '"{ ${'\''zarafa'\''}{language} || '\''en_US.UTF-8'\'' ; }"'<br />
<br />
<br />
#<br />
#--- licensed config ---<br />
#<br />
echo<br />
echo "Creating zarafa-licensed-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/licensed.cfg<br />
cat /usr/share/doc/zarafa-licensed/example-config/licensed.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_method '{ ${'\''zarafa-licensed'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_level '{ ${'\''zarafa-licensed'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/licensed.cfg/licensed.cfg log_timestamp '{ ${'\''zarafa-licensed'\''}{log_timestamp} || '\''1'\''; }'<br />
<br />
#<br />
#--- server config ---<br />
#<br />
echo<br />
echo "Creating zarafa-server-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/server.cfg<br />
cat /usr/share/doc/zarafa/example-config/server.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_tcp_enabled '{ ${'\''zarafa-server'\''}{server_tcp_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_tcp_port '{ ${'\''zarafa-server'\''}{TCPPort} || '\''236'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_pipe_enabled '{ ${'\''zarafa-server'\''}{server_pipe_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_name '{ ${'\''zarafa-server'\''}{server_name} || '\''Zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg database_engine '{ ${'\''zarafa-server'\''}{database_engine} || '\''mysql'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg allow_local_users '{ ${'\''zarafa-server'\''}{allow_local_users} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg local_admin_users '{ ${'\''zarafa-server'\''}{local_admin_users} || '\''root'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg system_email_address '{ ${'\''zarafa-server'\''}{system_email_address} || '\''postmaster@localhost'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg session_timeout '{ ${'\''zarafa-server'\''}{session_timeout} || '\''300'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg license_timeout '{ ${'\''zarafa-server'\''}{license_timeout} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_method '{ ${'\''zarafa-server'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_level '{ ${'\''zarafa-server'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg log_timestamp '{ ${'\''zarafa-server'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_enabled '{ ${'\''zarafa-server'\''}{audit_log_enabled} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_level '{ ${'\''zarafa-server'\''}{audit_log_level} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg audit_log_timestamp '{ ${'\''zarafa-server'\''}{audit_log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_host '{ ${'\''zarafa-server'\''}{mysql_host} || '\''localhost'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_port '{ ${'\''zarafa-server'\''}{mysql_port} || '\''3306'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_user '{ ${'\''zarafa-server'\''}{DbUser} || '\''zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_password '{ ${'\''zarafa-server'\''}{DbPassword}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg mysql_database '{ ${'\''zarafa-server'\''}{DbName} || '\''zarafa'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_storage '{ ${'\''zarafa-server'\''}{attachment_storage} || '\''files'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_path '/home/e-smith/files/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg attachment_compression '{ ${'\''zarafa-server'\''}{attachment_compression} || '\''6'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_enabled '{ ${'\''zarafa-ssl'\''}{server_ssl_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_port '{ ${'\''zarafa-ssl'\''}{TCPPort} || '\''237'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_key_file '/home/e-smith/ssl.pem/{$SystemName}.{$DomainName}.pem'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_key_pass '{ ${'\''zarafa-server'\''}{DbPassword}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_ca_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_ca_path '/home/e-smith/ssl.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sslkeys_path '/home/e-smith/ssl.pem'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg threads '{ ${'\''zarafa-server'\''}{threads} || '\''8'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg watchdog_frequency '{ ${'\''zarafa-server'\''}{watchdog_frequency} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg watchdog_max_age '{ ${'\''zarafa-server'\''}{watchdog_max_age} || '\''500'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_max_keep_alive_requests '{ ${'\''zarafa-server'\''}{server_max_keep_alive_requests} || '\''100'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_recv_timeout '{ ${'\''zarafa-server'\''}{server_recv_timeout} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_read_timeout '{ ${'\''zarafa-server'\''}{server_read_timeout} || '\''60'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_send_timeout '{ ${'\''zarafa-server'\''}{server_send_timeout} || '\''60'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg softdelete_lifetime '{ ${'\''zarafa-server'\''}{softdelete_lifetime} || '\''30'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_lifetime '{ ${'\''zarafa-server'\''}{sync_lifetime} || '\''365'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_log_all_changes '{ ${'\''zarafa-server'\''}{sync_log_all_changes} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_sso '{ ${'\''zarafa-server'\''}{enable_sso} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_gab '{ ${'\''zarafa-server'\''}{enable_gab} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg auth_method '{ ${'\''zarafa-server'\''}{auth_method} || '\''plugin'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg pam_service '{ ${'\''zarafa-server'\''}{pam_service} || '\''passwd'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_cell_size '{ ${'\''zarafa-server'\''}{cache_cell_size} || '\''268435456'\''; }' <br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_object_size '{ ${'\''zarafa-server'\''}{cache_object_size} || '\''5242880'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_indexedobject_size '{ ${'\''zarafa-server'\''}{cache_indexedobject_size} || '\''16777216'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_quota_size '{ ${'\''zarafa-server'\''}{cache_quota_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_quota_lifetime '{ ${'\''zarafa-server'\''}{cache_quota_lifetime} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_acl_size '{ ${'\''zarafa-server'\''}{cache_acl_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_store_size '{ ${'\''zarafa-server'\''}{cache_store_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_user_size '{ ${'\''zarafa-server'\''}{cache_user_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_userdetails_size '{ ${'\''zarafa-server'\''}{cache_userdetails_size} || '\''26214400'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_userdetails_lifetime '{ ${'\''zarafa-server'\''}{cache_userdetails_lifetime} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_server_size '{ ${'\''zarafa-server'\''}{cache_server_size} || '\''1048576'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg cache_server_lifetime '{ ${'\''zarafa-server'\''}{cache_server_lifetime} || '\''30'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_warn '{ ${'\''zarafa-server'\''}{quota_warn} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_soft '{ ${'\''zarafa-server'\''}{quota_soft} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg quota_hard '{ ${'\''zarafa-server'\''}{quota_hard} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg companyquota_warn '{ ${'\''zarafa-server'\''}{companyquota_warn} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_plugin '{ ${'\''zarafa-server'\''}{user_plugin} || '\''db'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_plugin_config '{ ${'\''zarafa-server'\''}{user_plugin_config}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg user_safe_mode '{ ${'\''zarafa-server'\''}{user_safe_mode} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg thread_stacksize '{ ${'\''zarafa-server'\''}{thread_stacksize} || '\''512'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_hosted_zarafa '{ ${'\''zarafa-server'\''}{enable_hosted_zarafa} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_distributed_zarafa '{ ${'\''zarafa-server'\''}{enable_distributed_zarafa} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg storename_format '{ ${'\''zarafa-server'\''}{storename_format} || '\''%f'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg loginname_format '{ ${'\''zarafa-server'\''}{loginname_format} || '\''%u'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_enabled '{ ${'\''zarafa-server'\''}{client_update_enabled} || '\''false'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_path '{ ${'\''zarafa-server'\''}{client_update_path} || '\''/var/lib/zarafa/client'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg client_update_log_level '{ ${'\''zarafa-server'\''}{client_update_log_level} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg hide_everyone '{ ${'\''zarafa-server'\''}{hide_everyone} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg hide_system '{ ${'\''zarafa-server'\''}{hide_system} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_enabled '{ ${'\''zarafa-server'\''}{index_services_enabled} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_search_timeout '{ ${'\''zarafa-server'\''}{index_services_search_timeout} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg index_services_prefix_chars '{ ${'\''zarafa-server'\''}{index_services_prefix_chars} || '\''3'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg enable_enhanced_ics '{ ${'\''zarafa-server'\''}{enable_enhanced_ics} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg sync_gab_realtime '{ ${'\''zarafa-server'\''}{sync_gab_realtime} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg disabled_features '{ ${'\''zarafa-server'\''}{disabled_features}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg max_deferred_records '{ ${'\''zarafa-server'\''}{max_deferred_records} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg max_deferred_records_folder '{ ${'\''zarafa-server'\''}{max_deferred_records_folder} || '\''20'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg coredump_enabled '{ ${'\''zarafa-server'\''}{coredump_enabled} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/server.cfg/server.cfg server_ssl_enable_v2 '{ ${'\''zarafa-server'\''}{server_ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- dagent config ---<br />
#<br />
echo<br />
echo "Creating zarafa-dagent-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/dagent.cfg<br />
cat /usr/share/doc/zarafa-dagent/example-config/dagent.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_method '{ ${'\''zarafa-dagent'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_level '{ ${'\''zarafa-dagent'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_timestamp '{ ${'\''zarafa-dagent'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg log_raw_message '{ ${'\''zarafa-dagent'\''}{log_raw_message} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg lmtp_port '{ ${'\''zarafa-dagent'\''}{lmtp_port} || '\''2003'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg lmtp_max_threads '{ ${'\''zarafa-dagent'\''}{lmtp_max_threads} || '\''20'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg process_model '{ ${'\''zarafa-dagent'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg spam_header_name '{ ${'\''zarafa-dagent'\''}{spam_header_name} || '\''X-Spam-Status'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg spam_header_value '{ ${'\''zarafa-dagent'\''}{spam_header_value} || '\''Yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg archive_on_delivery '{ ${'\''zarafa-dagent'\''}{archive_on_delivery} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/dagent.cfg/dagent.cfg set_rule_headers '{ ${'\''zarafa-dagent'\''}{set_rule_headers} || '\''yes'\''; }'<br />
<br />
<br />
#<br />
#--- spooler config ---<br />
#<br />
echo<br />
echo "Creating zarafa-spooler-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/spooler.cfg<br />
cat /usr/share/doc/zarafa-spooler/example-config/spooler.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg smtp_port '{ ${'\''zarafa-spooler'\''}{smtp_port} || '\''25'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_method '{ ${'\''zarafa-spooler'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_level '{ ${'\''zarafa-spooler'\''}{log_level} || '\''3'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg log_timestamp '{ ${'\''zarafa-spooler'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg max_threads '{ ${'\''zarafa-spooler'\''}{max_threads} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg fax_domain '{ ${'\''zarafa-spooler'\''}{fax_domain} || '\''fax.local'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg fax_international '{ ${'\''zarafa-spooler'\''}{fax_international} || '\''00'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_delegates '{ ${'\''zarafa-spooler'\''}{always_send_delegates} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_redirect_spoofing '{ ${'\''zarafa-spooler'\''}{allow_redirect_spoofing} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg copy_delegate_mails '{ ${'\''zarafa-spooler'\''}{copy_delegate_mails} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_delegate_meeting_request '{ ${'\''zarafa-spooler'\''}{allow_delegate_meeting_request} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg allow_send_to_everyone '{ ${'\''zarafa-spooler'\''}{allow_send_to_everyone} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_tnef '{ ${'\''zarafa-spooler'\''}{always_send_tnef} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg always_send_utf8 '{ ${'\''zarafa-spooler'\''}{always_send_utf8} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg charset_upgrade '{ ${'\''zarafa-spooler'\''}{charset_upgrade} || '\''windows-1252'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg expand_groups '{ ${'\''zarafa-spooler'\''}{expand_groups} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/spooler.cfg/spooler.cfg archive_on_send '{ ${'\''zarafa-spooler'\''}{archive_on_send} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- monitor config ---<br />
#<br />
echo<br />
echo "Creating zarafa-monitor-configuration-template ..."<br />
echo "The monitor program sends quota warning mails to users who are over quota."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/monitor.cfg<br />
cat /usr/share/doc/zarafa-monitor/example-config/monitor.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_method '{ ${'\''zarafa-monitor'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_level '{ ${'\''zarafa-monitor'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg log_timestamp '{ ${'\''zarafa-monitor'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg quota_check_interval '{ ${'\''zarafa-monitor'\''}{quota_check_interval} || '\''15'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/monitor.cfg/monitor.cfg mailquota_resend_interval '{ ${'\''zarafa-monitor'\''}{mailquota_resend_interval} || '\''1'\''; }'<br />
<br />
<br />
#<br />
#--- gateway config ---<br />
#<br />
echo<br />
echo "Creating zarafa-gateway-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/gateway.cfg<br />
cat /usr/share/doc/zarafa-gateway/example-config/gateway.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg server_socket 'http://localhost:{${'\''zarafa-server'\''}{TCPPort}||'\''236'\'';}/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3_enable '{ if (${'\''zarafa-pop3'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3_port '{ ${'\''zarafa-pop3'\''}{TCPPort} || '\''8110'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3s_enable '{ if (${'\''zarafa-pop3s'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg pop3s_port '{ ${'\''zarafa-pop3s'\''}{TCPPort} || '\''8995'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_enable '{ if (${'\''zarafa-imap'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_port '{ ${'\''zarafa-imap'\''}{TCPPort} || '\''8143'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imaps_enable '{ if (${'\''zarafa-imaps'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imaps_port '{ ${'\''zarafa-imaps'\''}{TCPPort} || '\''8993'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_only_mailfolders '{ ${'\''zarafa-imap'\''}{imap_only_mailfolders} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_public_folders '{ ${'\''zarafa-imap'\''}{imap_public_folders} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_capability_idle '{ ${'\''zarafa-imap'\''}{imap_capability_idle} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_max_messagesize '{ ${'\''zarafa-imap'\''}{imap_max_messagesize} || '\''134217728'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_generate_utf8 '{ ${'\''zarafa-imap'\''}{imap_generate_utf8} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_expunge_on_delete '{ ${'\''zarafa-imap'\''}{imap_expunge_on_delete} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg imap_store_rfc822 '{ ${'\''zarafa-imap'\''}{imap_store_rfc822} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_private_key_file '/home/e-smith/ssl.key/{$SystemName}.{$DomainName}.key'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_certificate_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_verify_client '{ ${'\''zarafa-gateway'\''}{ssl_verify_client} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg process_model '{ ${'\''zarafa-gateway'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_method '{ ${'\''zarafa-gateway'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_level '{ ${'\''zarafa-gateway'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg log_timestamp '{ ${'\''zarafa-gateway'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/gateway.cfg/gateway.cfg ssl_enable_v2 '{ ${'\''zarafa-gateway'\''}{ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- ical config ---<br />
#<br />
echo<br />
echo "Creating zarafa-ical-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/ical.cfg<br />
cat /usr/share/doc/zarafa-ical/example-config/ical.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ical_enable '{ if (${'\''zarafa-ical'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ical_port '{ ${'\''zarafa-ical'\''}{TCPPort} || '\''8088'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg icals_enable '{ if (${'\''zarafa-icals'\''}{status} eq '\''enabled'\'') {'\''yes'\''} else {'\''no'\''}; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg icals_port '{ ${'\''zarafa-icals'\''}{TCPPort} || '\''8089'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg server_socket 'http://localhost:{${'\''zarafa-server'\''}{TCPPort}||'\''236'\'';}/zarafa'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg process_model '{ ${'\''zarafa-ical'\''}{process_model} || '\''fork'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_method '{ ${'\''zarafa-ical'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_level '{ ${'\''zarafa-ical'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg log_timestamp '{ ${'\''zarafa-ical'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_private_key_file '/home/e-smith/ssl.key/{$SystemName}.{$DomainName}.key'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_certificate_file '/home/e-smith/ssl.crt/{$SystemName}.{$DomainName}.crt'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_verify_client '{ ${'\''zarafa-ical'\''}{ssl_verify_client} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg server_timezone '{$TimeZone}'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg default_charset '{ ${'\''zarafa-ical'\''}{default_charset} || '\''utf-8'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg enable_ical_get '{ ${'\''zarafa-ical'\''}{enable_ical_get} || '\''yes'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/ical.cfg/ical.cfg ssl_enable_v2 '{ ${'\''zarafa-ical'\''}{ssl_enable_v2} || '\''no'\''; }'<br />
<br />
<br />
#<br />
#--- indexer config ---<br />
#<br />
echo<br />
echo "Creating zarafa-indexer-configuration-template ..."<br />
echo<br />
mkdir -p /etc/e-smith/templates/etc/zarafa/indexer.cfg<br />
cat /usr/share/doc/zarafa-indexer/example-config/indexer.cfg | sed -e 's/\r$//g' > /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg cleanup_lockfiles '{ ${'\''zarafa-indexer'\''}{cleanup_lockfiles} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg limit_results '{ ${'\''zarafa-indexer'\''}{limit_results} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_method '{ ${'\''zarafa-indexer'\''}{log_method} || '\''file'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_level '{ ${'\''zarafa-indexer'\''}{log_level} || '\''2'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg log_timestamp '{ ${'\''zarafa-indexer'\''}{log_timestamp} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_interval '{ ${'\''zarafa-indexer'\''}{index_interval} || '\''5'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_threads '{ ${'\''zarafa-indexer'\''}{index_threads} || '\''1'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_field_length '{ ${'\''zarafa-indexer'\''}{index_max_field_length} || '\''10000'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_merge_factor '{ ${'\''zarafa-indexer'\''}{index_merge_factor} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_buffered_docs '{ ${'\''zarafa-indexer'\''}{index_max_buffered_docs} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_min_merge_docs '{ ${'\''zarafa-indexer'\''}{index_min_merge_docs} || '\''10'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_max_merge_docs '{ ${'\''zarafa-indexer'\''}{index_max_merge_docs} || '\''2147483647'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_term_interval '{ ${'\''zarafa-indexer'\''}{index_term_interval} || '\''128'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_cache_timeout '{ ${'\''zarafa-indexer'\''}{index_cache_timeout} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachments '{ ${'\''zarafa-indexer'\''}{index_attachments} || '\''no'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_max_size '{ ${'\''zarafa-indexer'\''}{index_attachment_max_size} || '\''5120'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_parser_max_memory '{ ${'\''zarafa-indexer'\''}{index_attachment_parser_max_memory} || '\''0'\''; }'<br />
replace /etc/e-smith/templates/etc/zarafa/indexer.cfg/indexer.cfg index_attachment_parser_max_cputime '{ ${'\''zarafa-indexer'\''}{index_attachment_parser_max_cputime} || '\''0'\''; }'<br />
<br />
<br />
/bin/echo "webaccess config"<br />
/bin/chown -R www:www /var/lib/zarafa-webaccess/tmp<br />
/bin/chown -R www:www /var/lib/zarafa-webapp/tmp<br />
FILE=/etc/httpd/conf.d/zarafa-webaccess.conf; if [ -a $FILE ]; then /bin/rm -f $FILE; fi<br />
FILE=/etc/httpd/conf.d/zarafa-webapp.conf; if [ -a $FILE ]; then /bin/rm -f $FILE; fi<br />
<br />
<br />
/bin/echo "Expanding Zarafa-templates"<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
<br />
/bin/echo "Expanding http.conf-template"<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo "Restarting httpd"<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
/bin/echo "Starting Zarafa-services"<br />
/etc/e-smith/events/actions/zarafa-services start<br />
<br />
/bin/echo "Setting permissions on files"<br />
FILE=/var/log/zarafa/dagent.log; if [ -a $FILE ]; then /bin/chmod 666 $FILE; fi<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
=== Execute zarafa-install (see installscript above for 7.0.x !!!!) ===<br />
<br />
/bin/chmod 554 /etc/e-smith/events/actions/zarafa-install<br />
<br />
cd /etc/e-smith/events/actions/<br />
<br />
./zarafa-install<br />
<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
== UPGRADING of Zarafa ==<br />
<br />
=== VERSION 7.0.x (7.0.x -> 7.0.x) ===<br />
==== Download via the Zarafawebsite the package for ZCP corresponding with the newest php53-mapi.rpm (cf. version above) ====<br />
<br />
Go (cd /...) to the installdirectory (ex. : /root/InstallZarafa) : <br />
<br />
cd /to the installdirectory<br />
<br />
ex.: <br />
<br />
cd /root/InstallZarafa<br />
<br />
wget http://download.zarafa.com/community/final/7.0/[version]/zcp-[version]-rhel-5-[cpu-arch]-free.tar.gz<br />
<br />
==== Unpack the corresponding package for ZCP :====<br />
<br />
tar -zxvf zcp-*<br />
<br />
==== Remove the devel packages ====<br />
<br />
Go (cd ./zcp-...) to the created subdirectory (zcp-...) :<br />
<br />
cd ./zcp- ... <br />
rm -f *-dev*.rpm<br />
<br />
Move the windows-directory to an installshare in your network<br />
<br />
==== Download the latest webapp.rpm too in the same subdirectory :====<br />
<br />
wget http://download.zarafa.com/community/final/WebApp/[version]/rhel/[zarafa-webapp-version.noarch.rpm]<br />
<br />
==== !!! Remove the existing php53-mapi.rpm first : !!! ====<br />
<br />
rpm -e php53-mapi --nodeps<br />
<br />
==== Install all rpm's in the unpacked package of ZCP and the webapp.rpm too :====<br />
<br />
yum localinstall *.rpm<br />
<br />
All packages have dependencies that cannot be resolved if you install only part of the rpm's.<br />
<br />
If you only want to upgrade one package (ex. the Webapp) :<br />
<br />
cd /to the new Webapp.rpm<br />
rpm -Uvh --force zarafa-webapp-[version].noarch<br />
<br />
==== Remove the default php-mapi.rpm ====<br />
<br />
We have to remove the installation of the default php-mapi (because it's not built for php 5.3).<br />
<br />
rpm -e php-mapi --nodeps<br />
<br />
==== Install the NEW php53-mapi.rpm ====<br />
-If you downloaded the rpm :<br />
<br />
rpm -Uvh --force php53-mapi<br />
<br />
-If you did set the EPEL-repository :<br />
<br />
yum install php53-mapi --enablerepo=epel --enablerepo=epel-testing<br />
<br />
==== Execute zarafa-update (see upgradescript above for 7.0.x !!!!) ====<br />
<br />
cd /etc/e-smith/events/actions/<br />
<br />
./zarafa-update<br />
<br />
OPTIONAL : Search in the Zarafa-releasenotes for new keys/options in the config-files and adjust the values of these new keys/options in the zarafa-config-templates :<br />
<br />
http://doc.zarafa.com/7.0/Release_Notes/en-US/html-single/<br />
<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
== INSTALLATION of Z-push (1.5.x or 2.0.x) ==<br />
<br />
* You can test if z-push is installed and functioning by going to http://[your-server-ip]/Microsoft-Server-ActiveSync You should be presented with a login request, and if you cancel, you will see Z-Push info. If you see both, z-push is working just fine.<br />
* If you experience (all of a sudden) z-push issues with your smartphone, please increase the PHP memory limit as descibed [http://wiki.contribs.org/Useful_Commands#Memory_Limit here]<br />
* Please note that z-push version 2.1 works with the below 2.0.x instructions, but you need to install php-posix<br />
yum install php-posix<br />
<br />
=== VERSION 1.5.x ===<br />
==== Download the Z-push-package (version 1.5 !!)====<br />
<br />
wget http://zarafa-deutschland.de/z-push-download/final/1.5/[z-push-latest version]<br />
<br />
Save in an installdirectory, ex. : root/InstallZPush<br />
<br />
==== Unpack the package for Z-push :====<br />
<br />
Go (cd /...) to the installdirectory (if you haven't done this yet) : <br />
<br />
cd /to the installdirectory<br />
<br />
And unpack :<br />
<br />
tar -zxvf z-push-[latest version] -C /var/www/html<br />
<br />
==== Change the name of the created z-push-directory in /var/www/html to 'z-push'====<br />
<br />
==== INSTALLSCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/z-push-install =====<br />
<nowiki><br />
#!/bin/sh<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ..."<br />
echo<br />
cat <<HERE1 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases<br />
{<br />
# vim: ft=perl:<br />
<br />
\$haveSSL = (exists \${modSSL}{status} and \${modSSL}{status} eq "enabled") ? 'yes' : 'no';<br />
my \$zwebmailStatus = \$zarafa{'status'} || "disabled";<br />
my \$zwebmailAccessType = \$zarafa{'access'} || "SSL";<br />
<br />
my \$dirs;<br />
\$dirs{zarafa} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webaccess} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webmail} = '/usr/share/zarafa-webaccess';<br />
if (\$imp{'status'} eq 'enabled') {\$dirs{webmail} = ''};<br />
\$dirs{webapp} = '/usr/share/zarafa-webapp';<br />
\$dirs{'Microsoft-Server-ActiveSync'} = '/var/www/html/z-push/index.php';<br />
<br />
return " # Zarafa is disabled in this VirtualHost\n"<br />
unless \$zwebmailStatus eq 'enabled';<br />
<br />
foreach \$place ('zarafa','webmail','webaccess','webapp','Microsoft-Server-ActiveSync')<br />
{<br />
if ((\$port eq "80") && (\$haveSSL eq 'yes') && (\$zwebmailAccessType eq 'SSL'))<br />
{<br />
\$OUT .= " RewriteRule ^/\$place(/.*|\\$) https://%{HTTP_HOST}/\$place\\\$1 [L,R]\n";<br />
} else {<br />
if ((\$dirs{\$place}) ne '') {\$OUT .= " Alias /\$place \$dirs{\$place}\n"};<br />
}<br />
} <br />
}<br />
HERE1<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ..."<br />
echo<br />
cat <<HERE2 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias<br />
{<br />
my \$zstatus = \$zarafa{'status'};<br />
<br />
if (defined \$zstatus && \$zstatus eq 'enabled')<br />
{<br />
\$OUT .= qq(<br />
#--------------------------------------------------------------------<br />
# Zarafa specific configuration files.<br />
#--------------------------------------------------------------------<br />
<br />
Alias /zarafa /usr/share/zarafa-webaccess/<br />
<Directory /usr/share/zarafa-webaccess/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
Alias /webapp /usr/share/zarafa-webapp/<br />
<Directory /usr/share/zarafa-webapp/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
<Directory /var/www/html/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php .php3<br />
php_flag magic_quotes_gpc off<br />
</Directory><br />
<br />
<Directory /var/www/html/z-push/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag register_globals off<br />
php_flag magic_quotes_runtime off<br />
php_flag short_open_tag on<br />
</Directory><br />
<br />
);<br />
} <br />
else<br />
{<br />
\$OUT .= "# Zarafa Webmail is not configured as it is disabled in the config db";<br />
}<br />
}<br />
HERE2<br />
<br />
######################################<br />
# Configuration of Z-push<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of Z-push"<br />
/bin/echo<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
<br />
/bin/echo <br />
/bin/echo "Need to debug Z-push ?"<br />
/bin/echo "Values: yes or no."<br />
/bin/echo <br />
read DEBUGZPUSH<br />
if [ "$DEBUGZPUSH" == yes ]; then<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/touch /var/www/html/z-push/debug.txt; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chown www:www /var/www/html/z-push/debug.txt; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chmod 755 /var/www/html/z-push/debug.txt; fi<br />
else<br />
rm -f /var/www/html/z-push/debug.txt<br />
fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== UPGRADESCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/z-push-update =====<br />
<nowiki><br />
#!/bin/sh<br />
<br />
######################################<br />
# Configuration of Z-push<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of Z-push"<br />
/bin/echo<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
<br />
/bin/echo <br />
/bin/echo "Need to debug Z-push ?"<br />
/bin/echo "Values: yes or no."<br />
/bin/echo <br />
read DEBUGZPUSH<br />
if [ "$DEBUGZPUSH" == yes ]; then<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/touch /var/www/html/z-push/debug.txt; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chown www:www /var/www/html/z-push/debug.txt; fi<br />
FILE=/var/www/html/z-push/state; if [ -d $FILE ]; then /bin/chmod 755 /var/www/html/z-push/debug.txt; fi<br />
else<br />
rm -f /var/www/html/z-push/debug.txt<br />
fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== See further : "Any version" ====<br />
<br />
=== VERSION 2.0.x ===<br />
==== Download the Z-push-package (version 2.0 !!)====<br />
wget http://zarafa-deutschland.de/z-push-download/final/2.0/[z-push-latest version]<br />
<br />
Save in an installdirectory, ex. : root/InstallZPush<br />
<br />
==== Unpack the package for Z-push :====<br />
Go (cd /...) to the installdirectory (if you haven't done this yet) : <br />
<br />
cd /to the installdirectory<br />
<br />
And unpack :<br />
<br />
tar -zxvf z-push-[latest version] -C /usr/share<br />
<br />
==== Change the name of the created z-push-directory in /usr/share to 'z-push' ====<br />
<br />
==== INSTALLSCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/z-push-install =====<br />
<nowiki><br />
#!/bin/sh<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases ..."<br />
echo<br />
cat <<HERE1 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/29ZarafaAliases<br />
{<br />
# vim: ft=perl:<br />
<br />
\$haveSSL = (exists \${modSSL}{status} and \${modSSL}{status} eq "enabled") ? 'yes' : 'no';<br />
my \$zwebmailStatus = \$zarafa{'status'} || "disabled";<br />
my \$zwebmailAccessType = \$zarafa{'access'} || "SSL";<br />
<br />
my \$dirs;<br />
\$dirs{zarafa} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webaccess} = '/usr/share/zarafa-webaccess';<br />
\$dirs{webmail} = '/usr/share/zarafa-webaccess';<br />
if (\$imp{'status'} eq 'enabled') {\$dirs{webmail} = ''};<br />
\$dirs{webapp} = '/usr/share/zarafa-webapp';<br />
\$dirs{'Microsoft-Server-ActiveSync'} = '/usr/share/z-push/index.php';<br />
<br />
return " # Zarafa is disabled in this VirtualHost\n"<br />
unless \$zwebmailStatus eq 'enabled';<br />
<br />
foreach \$place ('zarafa','webmail','webaccess','webapp','Microsoft-Server-ActiveSync')<br />
{<br />
if ((\$port eq "80") && (\$haveSSL eq 'yes') && (\$zwebmailAccessType eq 'SSL'))<br />
{<br />
\$OUT .= " RewriteRule ^/\$place(/.*|\\$) https://%{HTTP_HOST}/\$place\\\$1 [L,R]\n";<br />
} else {<br />
if ((\$dirs{\$place}) ne '') {\$OUT .= " Alias /\$place \$dirs{\$place}\n"};<br />
}<br />
} <br />
}<br />
HERE1<br />
<br />
#<br />
#--- /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ---<br />
#<br />
echo<br />
echo "Creating /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias ..."<br />
echo<br />
cat <<HERE2 > /etc/e-smith/templates/etc/httpd/conf/httpd.conf/86ZarafaAlias<br />
{<br />
my \$zstatus = \$zarafa{'status'};<br />
<br />
if (defined \$zstatus && \$zstatus eq 'enabled')<br />
{<br />
\$OUT .= qq(<br />
#--------------------------------------------------------------------<br />
# Zarafa specific configuration files.<br />
#--------------------------------------------------------------------<br />
<br />
Alias /zarafa /usr/share/zarafa-webaccess/<br />
<Directory /usr/share/zarafa-webaccess/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
Alias /webapp /usr/share/zarafa-webapp/<br />
<Directory /usr/share/zarafa-webapp/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php<br />
php_flag magic_quotes_gpc off<br />
php_flag track_vars on<br />
</Directory><br />
<br />
<Directory /usr/share/z-push/><br />
Options -Indexes<br />
AllowOverride All<br />
order allow,deny<br />
allow from all<br />
AddType application/x-httpd-php .php .php3<br />
php_flag magic_quotes_gpc off<br />
php_flag register_globals off<br />
php_flag magic_quotes_runtime off<br />
php_flag short_open_tag on<br />
</Directory><br />
<br />
);<br />
} <br />
else<br />
{<br />
\$OUT .= "# Zarafa Webmail is not configured as it is disabled in the config db";<br />
}<br />
}<br />
HERE2<br />
<br />
######################################<br />
# Configuration of Z-push<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of Z-push"<br />
/bin/echo<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/echo -e "** $FILE already exists, skipping **\n"; else /bin/mkdir $FILE; fi<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/echo -e "** $FILE already exists, skipping **\n"; else /bin/mkdir $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== UPGRADESCRIPT ====<br />
===== nano -w /etc/e-smith/events/actions/z-push-update =====<br />
<nowiki><br />
#!/bin/sh<br />
<br />
######################################<br />
# Configuration of Z-push<br />
######################################<br />
<br />
/bin/echo<br />
/bin/echo "Configuration of Z-push"<br />
/bin/echo<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/echo -e "** $FILE already exists, skipping **\n"; else /bin/mkdir $FILE; fi<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/lib/z-push; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/echo -e "** $FILE already exists, skipping **\n"; else /bin/mkdir $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/chown -R www:www $FILE; fi<br />
FILE=/var/log/z-push; if [ -d $FILE ]; then /bin/chmod 755 $FILE; fi<br />
<br />
/bin/echo<br />
/bin/echo "Expanding http.conf-template"<br />
/bin/echo<br />
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf<br />
<br />
/bin/echo<br />
/bin/echo "Restarting httpd"<br />
/bin/echo<br />
/usr/bin/sv restart /service/httpd-e-smith<br />
<br />
</nowiki><br />
<br />
===== To save : =====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== See further : "Any version" ====<br />
<br />
=== ANY VERSION (1.5.x or 2.0.x)===<br />
==== Edit the config.php file in the Z-Push directory to fit your needs. ====<br />
ex. Set your timezone in the config.php file.<br />
<br />
==== Execute z-push-install (see script above !!!!) ====<br />
<br />
/bin/chmod 554 /etc/e-smith/events/actions/z-push-install<br />
<br />
cd /etc/e-smith/events/actions/<br />
<br />
./z-push-install<br />
<br />
== UPGRADING of Z-push ==<br />
=== VERSION 1.5 (1.5.x -> 1.5.x)===<br />
==== Download the Z-push-package (version 1.5 !!)====<br />
<br />
wget http://zarafa-deutschland.de/z-push-download/final/1.5/[z-push-latest version]<br />
<br />
Save in an installdirectory, ex. : root/InstallZPush<br />
<br />
==== Unpack the corresponding package for ZCP and the package for Z-push :====<br />
<br />
Go (cd /...) to the installdirectory (if you haven't done this yet) : <br />
<br />
cd /to the installdirectory<br />
<br />
And unpack :<br />
<br />
tar -zxvf z-push-[latest version] -C /var/www/html<br />
<br />
==== Change the name of the created z-push-directory in /var/www/html to 'z-push'====<br />
==== See further : "Any version" ====<br />
=== VERSION 2.0 (2.0.x -> 2.0.x)===<br />
==== Download the Z-push-package (version 2.0 !!)====<br />
<br />
wget http://zarafa-deutschland.de/z-push-download/final/2.0/[z-push-latest version]<br />
<br />
Save in an installdirectory, ex. : root/InstallZPush<br />
<br />
<br />
==== Unpack the package for Z-push :====<br />
<br />
Go (cd /...) to the installdirectory (if you haven't done this yet) : <br />
<br />
cd /to the installdirectory<br />
<br />
And unpack :<br />
<br />
tar -zxvf z-push-[latest version] -C /usr/share<br />
<br />
==== Change the name of the created z-push-directory in /usr/share to 'z-push'====<br />
==== See further : "Any version" ====<br />
=== VERSION 1.5.x -> 2.0.x ===<br />
<br />
The easiest way to upgrade is to follow the steps for a new installation of version 2.0. The states of Z-Push 1.X are not compatible and there is no upgrade path, but as this version implements a fully automatic resynchronisation of devices it should not affect the users and work without the user interaction<br />
<br />
=== ANY VERSION ===<br />
==== Edit the config.php file in the Z-Push directory to fit your needs. ====<br />
ex. Set your timezone in the config.php file.<br />
<br />
==== Execute z-push-update (see script above !!!!) ====<br />
<br />
/bin/chmod 554 /etc/e-smith/events/actions/z-push-update<br />
<br />
cd /etc/e-smith/events/actions/<br />
<br />
./z-push-update<br />
<br />
== Managing Zarafa-users/companies : ==<br />
=== With Unix-plugin ===<br />
Zarafa-users are created with the creation of a SME-user, but you have to enable delivery to zarafa for these SME-users. <br />
==== Enable maildelivery to zarafa for a user : ====<br />
db accounts setprop [USERNAME] zarafa enabled<br />
/etc/e-smith/events/actions/qmail-update-user<br />
==== Disable maildelivery to zarafa for a user : ====<br />
db accounts setprop [USERNAME] zarafa disabled<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
==== Enable mail delivery to zarafa for ALL users : ====<br />
config setprop zarafa-server GlobalForward enabled<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
==== Other options for managing users ====<br />
zarafa-admin --help<br />
<br />
=== With DB-plugin ===<br />
==== Create company (in a Multi-company-environment) ====<br />
/etc/e-smith/events/actions/zarafa-create-company<br />
<br />
==== Create user ====<br />
/etc/e-smith/events/actions/zarafa-create-user<br />
==== Disable maildelivery to zarafa for a user : ====<br />
db accounts setprop [USERNAME] zarafa disabled<br />
/etc/e-smith/events/actions/qmail-update-user<br />
==== Other options for managing users/companies ====<br />
zarafa-admin --help<br />
<br />
== Usefull commands : ==<br />
<br />
=== Change db-entries (Change default-values in zarafa-config-files) ===<br />
config setprop [zarafa-service] [key] [value]<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
/etc/e-smith/events/actions/zarafa-services restart<br />
<br />
==== Change loglevel to 5 (= max. (default = 2))====<br />
config setprop zarafa-server log_level 5<br />
config setprop zarafa-dagent log_level 5<br />
config setprop zarafa-spooler log_level 5<br />
config setprop zarafa-monitor log_level 5<br />
config setprop zarafa-ical log_level 5<br />
config setprop zarafa-gateway log_level 5<br />
config setprop zarafa-licensed log_level 5<br />
config setprop zarafa-indexer log_level 5<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
/etc/e-smith/events/actions/zarafa-services restart<br />
<br />
==== Change index-interval to 60 minutes (= max. (default = 5))====<br />
config setprop zarafa-indexer index_interval 60<br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
/etc/e-smith/events/actions/zarafa-services restart<br />
<br />
==== Setting system-email-address ====<br />
config setprop zarafa-server system_email_address [admin@mydomain.com] <br />
/etc/e-smith/events/actions/zarafa-expand-templates<br />
/etc/e-smith/events/actions/zarafa-services restart<br />
<br />
=== Debugging Z-push 1.5.x (not for 2.0.x) ===<br />
==== Disable (debugging is enabled by default in this howto) ====<br />
rm -f /var/www/html/z-push/debug.txt<br />
==== Enable after disabling (debugging is enabled by default in this howto) ====<br />
/bin/touch /var/www/html/z-push/debug.txt<br />
/bin/chown www:www /var/www/html/z-push/debug.txt<br />
/bin/chmod 755 /var/www/html/z-push/debug.txt<br />
<br />
=== View userdetails ===<br />
zarafa-admin --details [user]<br />
<br />
=== Setting/Changing send-emailadres for a user ===<br />
zarafa-admin -u [user] -e [send-emailadres]<br />
<br />
=== Setting/Changing fullname for a user ===<br />
zarafa-admin -u [user] -f "[full name]"<br />
<br />
=== Quota-settings ===<br />
zarafa-admin -u [user] --qo y --qw 1600 --qs 1800 --qh 2000<br />
<br />
=== Give a user administrator-privileges ===<br />
zarafa-admin -u [user] -a y<br />
<br />
== Usefull plugins : ==<br />
=== Password-plugin for webaccess (ONLY FOR DB-PLUGIN) ===<br />
[https://community.zarafa.com/pg/plugins/project/157/developer/dw2412/passwd-plugin Dev-page]<br />
<br />
After installation : in /var/lib/zarafa-webaccess/plugins/passwd/dialogs/pwdchange.php, change this line :<br />
<br />
$passwd_cmd = "/usr/local/bin/zarafa-passwd -u %s -o %s -p %s";<br />
<br />
to this :<br />
<br />
$passwd_cmd = "/usr/bin/zarafa-passwd -u '%s' -o '%s' -p '%s'";<br />
<br />
=== Password-change by users from outsite your network for webaccess/webapp (IF USING THE UNIX PLUGIN) ===<br />
==== Install Usermanager ====<br />
[[UserManager]] : Install smeserver-userpanel and smeserver-userpanels<br />
<br />
==== nano /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/VirtualHosts/28UserManagerProxyPass ====<br />
<nowiki><br />
{<br />
# vim: ft=perl:<br />
$haveSSL = (exists ${modSSL}{status} and ${modSSL}{status} eq "enabled") ? 'yes' : 'no';<br />
$plainTextAccess = ${'httpd-admin'}{PermitPlainTextAccess} || 'no';<br />
$OUT = '';<br />
foreach $place ('user-manager','server-common','user')<br />
{<br />
if (($port eq "80") && ($haveSSL eq 'yes') && ($plainTextAccess ne 'yes'))<br />
{<br />
$OUT .= " RewriteRule ^/$place(/.*|\$) https://%{HTTP_HOST}/$place\$1 [L,R,NC]\n";<br />
} else {<br />
$OUT .= " ProxyPass /$place http://127.0.0.1:${'httpd-admin'}{TCPPort}/$place\n";<br />
$OUT .= " ProxyPassReverse /$place http://127.0.0.1:${'httpd-admin'}{TCPPort}/$place\n";<br />
}<br />
$OUT .= " <Location /$place>\n";<br />
$OUT .= " order deny,allow\n";<br />
$OUT .= " deny from all\n";<br />
$OUT .= " allow from all\n"; <br />
$OUT .= " </Location>\n";<br />
}<br />
}<br />
</nowiki><br />
<br />
==== To save : ====<br />
CTRL + X<br />
yes<br />
<ENTER><br />
<br />
==== Via the Server-Manager : Delegate the userpanel-password to external users ====<br />
Now these external users can change from outsite your network there sme-password : https://www.yourdomain.tld/user<br />
<br />
=== WebApp - OwnCloud attachment plug-in ===<br />
<br />
[https://community.zarafa.com/pg/plugins/project/16024/developer/h44z/webapp-owncloud-attachment-plugin OwnCloud attachment plug-in]<br />
<br />
=== WebApp - Dropbox attachment plug-in===<br />
<br />
[https://community.zarafa.com/pg/blog/read/14505/webapp-the-dropbox-plugin Dropbox plug-in]<br />
<br />
== Webmail : ==<br />
Access with a browser,<br />
<br />
https://server/zarafa<br />
https://server/webaccess<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/webapp (NEW VERSION OF WEBACCESS)<br />
<br />
== Connecting Outlook : ==<br />
<br />
On your Windowsclients, execute zarafaclient.msi (Moved earlier to an installshare in your network - cf. supra)<br />
<br />
Configure Outlook (point it to your zarafaserver with the credentials of a created Zarafa-user (if DB-plugin : create Zarafa-users first))<br />
<br />
== Connecting other clients : ==<br />
=== IMAP/POP3 ===<br />
The default ports for Zarafa are 8000 + default values<br />
*so imap = 8143, imaps = 8993<br />
*so pop3 = 8110, pop3s = 8995<br />
<br />
== Zarafa-documentation : ==<br />
<br />
=== Zarafa Administrator Manual ===<br />
[http://doc.zarafa.com/7.0/Administrator_Manual/en-US/html-single/index.html Zarafa Administrator Manual]<br><br />
[http://doc.zarafa.com/7.0/Release_Notes/en-US/html-single Release notes (changes in the Zarafa-configfiles)]<br><br />
=== Zarafa User Manual ===<br />
[http://doc.zarafa.com/trunk/User_Manual_WebApp/en-US/html/ Usermanual Zarafa-Webapp]<br />
<br />
=== Help for the zarafa-admin-tool ===<br />
zarafa-admin --help<br />
=== man-pages ===<br />
==== services-man-pages ====<br />
man zarafa-server<br />
man zarafa-monitor<br />
man zarafa-dagent<br />
man zarafa-gateway<br />
man zarafa-spooler<br />
man zarafa-ical<br />
man zarafa-indexer<br />
man zarafa-licensed<br />
==== configuation-man-pages ====<br />
man zarafa-server.cfg<br />
man zarafa-monitor.cfg<br />
man zarafa-dagent.cfg<br />
man zarafa-gateway.cfg<br />
man zarafa-spooler.cfg<br />
man zarafa-ical.cfg<br />
man zarafa-indexer.cfg<br />
man zarafa-licensed.cfg<br />
man zarafa-unix.cfg<br />
<br />
[[Category:Howto]]<br />
[[Category:Groupware]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa&diff=23453
Zarafa
2014-01-26T18:14:46Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa}}<br />
{{Level|advanced}}<br />
{{Note box|<br />
'''This wiki page is specific to SME7 only.'''<br />
<br />
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME8 [[Zarafa_on_SME8|Zarafa on SME 8]].'''<br />
<br />
'''There is a separate wiki page with a ''fully automated'' install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa on SME 9|Zarafa on SME 9]].'''<br />
}}<br />
<br />
===Maintainers===<br />
Darrell May<br />
<br />
Stephen Noble http://dungog.net/wiki<br />
<br />
=== Version ===<br />
{{#smeversion:smeserver-zarafa}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
<br />
===Installation===<br />
<br />
==== Latest zarafa tested version ====<br />
Information on previous versions of zarafa rpms can be found in the [http://download.zarafa.com/zarafa/release/docs/changelog.en.txt changelog document]<br />
<br />
==== Zarafa rpms installation ====<br />
<br />
http://www.zarafa.com/download-community<br />
<br />
Distribution: Rhel 4 = SME 7 :: Rhel 5 = SME 8<br />
<br />
Select a version, the 3 Outlook license version, or the GPL version. (which doesn't have the zarafa-licensed-*.rpm)<br />
<br />
tar -zxvf zarafa-6.*.tar.gz<br />
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-6*.rpm zarafa-webaccess-*.rpm zarafa-licensed-*.rpm<br />
<br />
This will also install as a dependency: ''sysstat''<br />
{{Note box| You have to enable InnoDB support in MySql in order to get zarafa-server running, for information on how to do so, see [[MySQL#Enable_InnoDB_engine]]}}<br />
<br />
==== smeserver-zarafa ====<br />
<br />
{{Note box| This is an alpha release. Possibly for production servers after testing with per user settings first.<br />
<br />
You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir.<br />
<br />
A minimal amount of disruption can be achieved by enabling per user, that user just enables another IMAP connection in their email client on port 8143, they could then just drag and drop mail between SME to Zarafa mail stores. }}<br />
<br />
Install a fresh SME 7.4 test server and perform the following:<br />
<br />
yum install smeserver-zarafa --enablerepo=smedev<br />
config setprop zarafa-licensed status disabled #GPL version only<br />
<br />
{{Note box|If you installed the GPL version only (without outlook support), you need to create the (empty) file '/var/log/zarafa/licensed.log'. This file is required in all cases. Without this file (and using the GPL non-Outlook version), the Zarafa configuration panel in server manager will not be displayed.}}<br />
<br />
<br />
After rpm install execute the following:<br />
<br />
/etc/e-smith/events/actions/zarafa-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
{{Note box| You will be prompted to select the user plugin you wish to test. We suggest the db method. Note the ldap plugin is currently not supported in the rpm. The unix plugin reads existing SME user details but also includes groups and machine names (messy). The db plugin is pristine however you need to enter all the user details. In both cases the user must exist in SME first as a standard user. A decision on which plugin we will choose for final deployment is still to be determined.}}<br />
<br />
==== Updating ====<br />
Download newer rpms, then<br />
rpm -Uvh zarafa-6*.rpm zarafa-webaccess-*.rpm libvmime-0*.rpm libical-0*.rpm zarafa-licensed-*.rpm<br />
/etc/e-smith/events/actions/zarafa-update<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
===Usage===<br />
====Managing Users====<br />
Enable mail delivery to zarafa for users:<br />
<br />
for all users<br />
config setprop zarafa-server GlobalForward enabled<br />
or for individual users<br />
db accounts setprop $USERNAME zarafa enabled<br />
apply<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
If you chose the db plugin, run:<br />
<br />
/etc/e-smith/events/actions/zarafa-create-user<br />
<br />
or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )<br />
<br />
<br />
====Webmail====<br />
Access with a browser,<br />
<br />
https://server/zarafa<br />
https://server/webaccess<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
<br />
* Outlook 2007 client generates ''Error 0x80070057'' on send and receive if the Zarafa<br />
server is added to an existing profile. Creating a new clean profile solved<br />
the problem.<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
=====Thunderbird=====<br />
It seems that in the latest Thunderbird versions security tightened and Thunderbird will simply reject Self Signed Certificates when you try to connect to a (remote) SME Server on secure ports.<br />
You first must add all the secure services ports to the security exceptions of Thunderbird under:<br />
* tools->options->advanced->certificates->view certificates->Add Exception<br />
and add your server address INLCUDING the specific port number of the service for EACH of the service-ports!<br />
<br />
The format must be:<br />
https://yourserver.com:8993 (for IMAPS)<br />
https://yourserver.com:465 (SMTP)<br />
https://yourserver.com:8089 (Caldav)<br />
etc. etc<br />
<br />
After accepting the self signed certificate for each service-port, you then can add an new email account and the Self Signed Certificate will not be rejected and you normally accept or install it like any other certificate.<br />
<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
==== Calendar CalDAV / iCal ====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>https://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>https://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>https://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>https://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>https://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>https://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>https://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>https://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>https://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>https://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf<br />
<br />
<br />
Download the latest Z-push version (see: http://z-push.sourceforge.net).<br />
wget http://download2.berlios.de/z-push/z-push-1.2.2.tar.gz<br />
<br />
Extract the files:<br />
tar -zxvf z-push-1.2.2.tar.gz -C /var/www/html<br />
<br />
'State'-dir needs to be writable for apache:<br />
chmod 755 /var/www/html/z-push/state<br />
chown www:www /var/www/html/z-push/state<br />
<br />
Expand and restart<br />
expand-template /etc/httpd/conf/httpd.conf<br />
sv restart httpd-e-smith<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=== Extras ===<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/<br />
<br />
----<br />
[[Category: Contrib]]<br />
[[Category: Groupware]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa&diff=23452
Zarafa
2014-01-26T18:14:13Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa}}<br />
{{Level|advanced}}<br />
<br />
{{Note box|<br />
'''This wiki page is specific to SME7 only.'''<br />
<br />
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME8 [[Zarafa_on_SME8|Zarafa on SME 8]].'''<br />
<br />
'''There is a separate wiki page with a ''fully automated'' install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa on SME 9|Zarafa on SME 9]].'''<br />
}}<br />
<br />
<br />
===Maintainers===<br />
Darrell May<br />
<br />
Stephen Noble http://dungog.net/wiki<br />
<br />
=== Version ===<br />
{{#smeversion:smeserver-zarafa}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
<br />
===Installation===<br />
<br />
==== Latest zarafa tested version ====<br />
Information on previous versions of zarafa rpms can be found in the [http://download.zarafa.com/zarafa/release/docs/changelog.en.txt changelog document]<br />
<br />
==== Zarafa rpms installation ====<br />
<br />
http://www.zarafa.com/download-community<br />
<br />
Distribution: Rhel 4 = SME 7 :: Rhel 5 = SME 8<br />
<br />
Select a version, the 3 Outlook license version, or the GPL version. (which doesn't have the zarafa-licensed-*.rpm)<br />
<br />
tar -zxvf zarafa-6.*.tar.gz<br />
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-6*.rpm zarafa-webaccess-*.rpm zarafa-licensed-*.rpm<br />
<br />
This will also install as a dependency: ''sysstat''<br />
{{Note box| You have to enable InnoDB support in MySql in order to get zarafa-server running, for information on how to do so, see [[MySQL#Enable_InnoDB_engine]]}}<br />
<br />
==== smeserver-zarafa ====<br />
<br />
{{Note box| This is an alpha release. Possibly for production servers after testing with per user settings first.<br />
<br />
You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir.<br />
<br />
A minimal amount of disruption can be achieved by enabling per user, that user just enables another IMAP connection in their email client on port 8143, they could then just drag and drop mail between SME to Zarafa mail stores. }}<br />
<br />
Install a fresh SME 7.4 test server and perform the following:<br />
<br />
yum install smeserver-zarafa --enablerepo=smedev<br />
config setprop zarafa-licensed status disabled #GPL version only<br />
<br />
{{Note box|If you installed the GPL version only (without outlook support), you need to create the (empty) file '/var/log/zarafa/licensed.log'. This file is required in all cases. Without this file (and using the GPL non-Outlook version), the Zarafa configuration panel in server manager will not be displayed.}}<br />
<br />
<br />
After rpm install execute the following:<br />
<br />
/etc/e-smith/events/actions/zarafa-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
{{Note box| You will be prompted to select the user plugin you wish to test. We suggest the db method. Note the ldap plugin is currently not supported in the rpm. The unix plugin reads existing SME user details but also includes groups and machine names (messy). The db plugin is pristine however you need to enter all the user details. In both cases the user must exist in SME first as a standard user. A decision on which plugin we will choose for final deployment is still to be determined.}}<br />
<br />
==== Updating ====<br />
Download newer rpms, then<br />
rpm -Uvh zarafa-6*.rpm zarafa-webaccess-*.rpm libvmime-0*.rpm libical-0*.rpm zarafa-licensed-*.rpm<br />
/etc/e-smith/events/actions/zarafa-update<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
===Usage===<br />
====Managing Users====<br />
Enable mail delivery to zarafa for users:<br />
<br />
for all users<br />
config setprop zarafa-server GlobalForward enabled<br />
or for individual users<br />
db accounts setprop $USERNAME zarafa enabled<br />
apply<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
If you chose the db plugin, run:<br />
<br />
/etc/e-smith/events/actions/zarafa-create-user<br />
<br />
or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )<br />
<br />
<br />
====Webmail====<br />
Access with a browser,<br />
<br />
https://server/zarafa<br />
https://server/webaccess<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
<br />
* Outlook 2007 client generates ''Error 0x80070057'' on send and receive if the Zarafa<br />
server is added to an existing profile. Creating a new clean profile solved<br />
the problem.<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
=====Thunderbird=====<br />
It seems that in the latest Thunderbird versions security tightened and Thunderbird will simply reject Self Signed Certificates when you try to connect to a (remote) SME Server on secure ports.<br />
You first must add all the secure services ports to the security exceptions of Thunderbird under:<br />
* tools->options->advanced->certificates->view certificates->Add Exception<br />
and add your server address INLCUDING the specific port number of the service for EACH of the service-ports!<br />
<br />
The format must be:<br />
https://yourserver.com:8993 (for IMAPS)<br />
https://yourserver.com:465 (SMTP)<br />
https://yourserver.com:8089 (Caldav)<br />
etc. etc<br />
<br />
After accepting the self signed certificate for each service-port, you then can add an new email account and the Self Signed Certificate will not be rejected and you normally accept or install it like any other certificate.<br />
<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
==== Calendar CalDAV / iCal ====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>https://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>https://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>https://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>https://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>https://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>https://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>https://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>https://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>https://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>https://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf<br />
<br />
<br />
Download the latest Z-push version (see: http://z-push.sourceforge.net).<br />
wget http://download2.berlios.de/z-push/z-push-1.2.2.tar.gz<br />
<br />
Extract the files:<br />
tar -zxvf z-push-1.2.2.tar.gz -C /var/www/html<br />
<br />
'State'-dir needs to be writable for apache:<br />
chmod 755 /var/www/html/z-push/state<br />
chown www:www /var/www/html/z-push/state<br />
<br />
Expand and restart<br />
expand-template /etc/httpd/conf/httpd.conf<br />
sv restart httpd-e-smith<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=== Extras ===<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/<br />
<br />
----<br />
[[Category: Contrib]]<br />
[[Category: Groupware]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=23421
Zarafa on SME 9
2014-01-26T09:13:26Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta1. It should be ready for production servers when SME9 reaches RC stage.<br />
This contrib will NOT work on SME8, there are unresolved dependencies.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
Now install smeserver-zarafa-unix by performing the following:<br />
yum install smeserver-zarafa-unix --enablerepo=smedev<br />
<br />
NOTE: If you installed the GPL version of Zarafa, you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
After rpm install execute the following:<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
=====To disable global Zarafa for all users=====<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
=====To enable an individual user if Global is disabled=====<br />
db accounts setprop $USERNAME Zarafa enabled<br />
signal-event user-modify $USERNAME<br />
=====To enable the admin account=====<br />
db accounts setprop admin Zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
=====Known working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=====Additional Mobile Synchronization Information=====<br />
<br />
'''SSL Synchronization with Windows Mobile devices'''<br />
<br />
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=23420
Zarafa on SME 9
2014-01-26T08:41:33Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta1. It should be ready for production servers when SME9 reaches RC stage.<br />
This contrib will NOT work on SME8, there are unresolved dependencies.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
Now install smeserver-zarafa-unix by performing the following:<br />
yum install smeserver-zarafa-unix --enablerepo=smedev<br />
<br />
NOTE: If you installed the GPL version of Zarafa, you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
After rpm install execute the following:<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
=====To disable global Zarafa for all users=====<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
=====To enable an individual user if Global is disabled=====<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
=====To enable the admin account=====<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
=====Known working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=====Additional Mobile Synchronization Information=====<br />
<br />
'''SSL Synchronization with Windows Mobile devices'''<br />
<br />
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Imapsync&diff=21889
Imapsync
2013-10-22T14:12:51Z
<p>Pfloor: </p>
<hr />
<div>=== About ===<br />
imapsync allows you to transfer or synchronize data between any two IMAP servers. This could be used in any of several scenarios:<br />
* Upgrading from one mail server to another (SME -> SME, Exchange -> SME, Notes -> SME)<br />
* Backing up email from one IMAP server to another<br />
* Automated spam learning when using SME with an internal mail server (see the [[#Advanced_Example: Exchange Public Folders|Advanced]] example below).<br />
<br />
<br />
Author: Gilles LAMIRAL <lamiral-at-linux-france.org><br />
<br />
* Author's [http://www.linux-france.org/prj/imapsync/README README]<br />
* Author's [http://www.linux-france.org/prj/imapsync/ChangeLog Change Log]<br />
* Author's [http://www.linux-france.org/prj/imapsync/dist/ Distribution Folder]<br />
* Note about [http://www.linux-france.org/prj/imapsync/BUG_IMAPClient_3.xx Bugs with perl-Mail-IMAPClient-3.x]<br />
<br />
=== Installation ===<br />
==== Enable the dag repository ====<br />
{{Repository|dag}}<br />
<br />
==== Install imapsync ====<br />
yum --enablerepo=dag install imapsync<br />
<br />
=== Examples ===<br />
==== Basic Example: Account Duplication ====<br />
This example would copy all existing folders from foo@imap.truc.org to bar@imap.trac.org<br />
/usr/bin/imapsync --noauthmd5 \<br />
--host1 imap.truc.org --user1 foo --passfile1 /etc/secret1 \<br />
--host2 imap.trac.org --user2 bar --passfile2 /etc/secret2<br />
<br />
Bear in mind that you would need to create /etc/secret1 and /etc/secret2 containing the correct passwords for imapuser1 and imapuser2 respectively.<br />
<br />
==== Advanced Example: Exchange Public Folders ====<br />
This example will transfer the public folders 'LearnAsSpam' and 'LearnAsHam' from an Exchange server to the specified user on your SME server.<br />
<br />
If you create and schedule a script to run this command regularly, and combine it with [http://bugs.contribs.org/show_bug.cgi?id=1701#c25 LearnAsSpam.pl] and [http://wiki.contribs.org/Email#Setup_Blacklists_.26_Bayesian_Autolearning|Bayesian Auto-Learning] you could let the users on an internal Exchange Server train your SME spamassassin by dragging SPAM or HAM into public folders in their Outlook.<br />
<br />
Assumptions:<br />
* For the Exchange Server:<br />
** the user '''spamfilter''' exists on the Exchange server<br />
** the password for '''spamfilter''' on the Exchange server is in the file ''/root/secret1''<br />
** the Exchange Server user '''spamfilter''' has ''Owner'' permissions on both ''Public Folders/LearnAsSpam'' and ''Public Folders/LearnAsHam''<br />
* For the SME Server<br />
** the user '''spamfilter''' exists<br />
** the password for '''spamfilter''' on the SME server is in ''/root/secret2''<br />
** the folders ''LearnAsSpam'' and ''LearnAsHam'' exist in the email root for '''spamfilter'''<br />
<br />
=====imapsync command=====<br />
<nowiki>/usr/bin/imapsync \<br />
-- noauthmd5 \<br />
--host1 a.b.c.d --port1 993 --ssl1 --user1 spamfilter --passfile1 /root/secret1 \<br />
--delete --expunge1 --prefix1 "Public Folders." \<br />
--host2 localhost --port2 993 --ssl2 --user2 spamfilter --passfile2 /root/secret2 \<br />
--folder "Public Folders/LearnAsSpam" \<br />
--folder "Public Folders/LearnAsHam" \<br />
--noauthmd5 </nowiki><br />
<br />
====Migrating users and data to Zarafa====<br />
Zarafa migration whitepaper describes various ways of migrating your users and your data to a Zarafa server.<br />
<br />
http://download.zarafa.com/zarafa/release/docs/zarafa_migration.en.pdf<br />
<br />
=====Folder Naming=====<br />
SME and Zarafa use different folder naming. To enhance migration SME folders should be renamed prior to migration.<br />
<br />
drafts > Drafts <br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
=====IMAP migration from SME/IMAP to Zarafa/IMAP=====<br />
By default smeserver-zarafa enables zarafa IMAP on port 8143<br />
<br />
Perform a user mail sync from SME/IMAP (host1/port1) to Zarafa/IMAP (host2/port2) <br />
<br />
imapsync --noauthmd5 --host1 localhost --port1 143 --split1 500 --user1 <username> \<br />
--password1 <password> --sep2 / --prefix2 "" --host2 localhost --port2 8143 \<br />
--split2 500 --user2 <username> --password2 <password><br />
<br />
Example to synchronize a user named 'bob' with password 'bob123' from SME IMAP into Zarafa:<br />
<br />
imapsync --noauthmd5 --host1 localhost --port1 143 --split1 500 --user1 bob \<br />
--password1 bob123 --sep2 / --prefix2 "" --host2 localhost --port2 8143 --split2 500 \<br />
--user2 bob --password2 bob123<br />
<br />
'''Note:''' If the synchronization process terminates, apparently successfully, but only part-way through, delete the dovecot.index.cache file in the last folder copied and restart the process. Adding "--useheader 'Message-ID' --skipsize" to the command above will prevent duplicates if the process does have to be restarted.<br />
<br />
[[Category: Howto]]<br />
[[Category: Mail]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=21886
Zarafa on SME 9
2013-10-22T13:59:06Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta1. It should be ready for production servers when SME9 reaches RC stage.<br />
This contrib will NOT work on SME8, there are unresolved dependencies.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
NOTE: Built packages are not on the build server yet. See [[bugzilla:7383]] for RPM and SRPM packages.<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
Now install smeserver-zarafa-unix by performing the following:<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
After rpm install execute the following:<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
=====To disable global Zarafa for all users=====<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
=====To enable an individual user if Global is disabled=====<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
=====To enable the admin account=====<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
=====Known working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=====Additional Mobile Synchronization Information=====<br />
<br />
'''SSL Synchronization with Windows Mobile devices'''<br />
<br />
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=21885
Zarafa on SME 9
2013-10-22T13:53:56Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
NOTE: Built packages are not on the build server yet. See [[bugzilla:7383]] for RPM and SRPM packages.<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
Now install smeserver-zarafa-unix by performing the following:<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
After rpm install execute the following:<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
=====To disable global Zarafa for all users=====<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
=====To enable an individual user if Global is disabled=====<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
=====To enable the admin account=====<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
=====Known working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=====Additional Mobile Synchronization Information=====<br />
<br />
'''SSL Synchronization with Windows Mobile devices'''<br />
<br />
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=21789
Zarafa on SME 9
2013-10-17T06:17:03Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9beta1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
NOTE: Built packages are not on the build server yet. See [[bugzilla:7383]] for RPM and SRPM packages.<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.6-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Additional Mobile Synchronization Information====<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=19203
Zarafa on SME 9
2013-02-27T05:48:03Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
NOTE: Built packages are not on the build server yet. See [[bugzilla:7383]] for RPM and SRPM packages.<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.6-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Additional Mobile Synchronization Information====<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa&diff=19202
Zarafa
2013-02-27T05:28:21Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa}}<br />
{{Level|advanced}}<br />
<br />
There is a separate page on how to install Zarafa 7.x on SME8 [[Zarafa_on_SME8|here]]<br />
<br />
There is a separate page with a fully automated install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa on SME 9|here]]<br />
<br />
<br />
===Maintainers===<br />
Darrell May<br />
<br />
Stephen Noble http://dungog.net/wiki<br />
<br />
=== Version ===<br />
{{#smeversion:smeserver-zarafa}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
<br />
===Installation===<br />
<br />
==== Latest zarafa tested version ====<br />
Information on previous versions of zarafa rpms can be found in the [http://download.zarafa.com/zarafa/release/docs/changelog.en.txt changelog document]<br />
<br />
==== Zarafa rpms installation ====<br />
<br />
http://www.zarafa.com/download-community<br />
<br />
Distribution: Rhel 4 = SME 7 :: Rhel 5 = SME 8<br />
<br />
Select a version, the 3 Outlook license version, or the GPL version. (which doesn't have the zarafa-licensed-*.rpm)<br />
<br />
tar -zxvf zarafa-6.*.tar.gz<br />
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-6*.rpm zarafa-webaccess-*.rpm zarafa-licensed-*.rpm<br />
<br />
This will also install as a dependency: ''sysstat''<br />
{{Note box| You have to enable InnoDB support in MySql in order to get zarafa-server running, for information on how to do so, see [[MySQL#Enable_InnoDB_engine]]}}<br />
<br />
==== smeserver-zarafa ====<br />
<br />
{{Note box| This is an alpha release. Possibly for production servers after testing with per user settings first.<br />
<br />
You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir.<br />
<br />
A minimal amount of disruption can be achieved by enabling per user, that user just enables another IMAP connection in their email client on port 8143, they could then just drag and drop mail between SME to Zarafa mail stores. }}<br />
<br />
Install a fresh SME 7.4 test server and perform the following:<br />
<br />
yum install smeserver-zarafa --enablerepo=smedev<br />
config setprop zarafa-licensed status disabled #GPL version only<br />
<br />
{{Note box|If you installed the GPL version only (without outlook support), you need to create the (empty) file '/var/log/zarafa/licensed.log'. This file is required in all cases. Without this file (and using the GPL non-Outlook version), the Zarafa configuration panel in server manager will not be displayed.}}<br />
<br />
<br />
After rpm install execute the following:<br />
<br />
/etc/e-smith/events/actions/zarafa-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
{{Note box| You will be prompted to select the user plugin you wish to test. We suggest the db method. Note the ldap plugin is currently not supported in the rpm. The unix plugin reads existing SME user details but also includes groups and machine names (messy). The db plugin is pristine however you need to enter all the user details. In both cases the user must exist in SME first as a standard user. A decision on which plugin we will choose for final deployment is still to be determined.}}<br />
<br />
==== Updating ====<br />
Download newer rpms, then<br />
rpm -Uvh zarafa-6*.rpm zarafa-webaccess-*.rpm libvmime-0*.rpm libical-0*.rpm zarafa-licensed-*.rpm<br />
/etc/e-smith/events/actions/zarafa-update<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
===Usage===<br />
====Managing Users====<br />
Enable mail delivery to zarafa for users:<br />
<br />
for all users<br />
config setprop zarafa-server GlobalForward enabled<br />
or for individual users<br />
db accounts setprop $USERNAME zarafa enabled<br />
apply<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
If you chose the db plugin, run:<br />
<br />
/etc/e-smith/events/actions/zarafa-create-user<br />
<br />
or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )<br />
<br />
<br />
====Webmail====<br />
Access with a browser,<br />
<br />
https://server/zarafa<br />
https://server/webaccess<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
<br />
* Outlook 2007 client generates ''Error 0x80070057'' on send and receive if the Zarafa<br />
server is added to an existing profile. Creating a new clean profile solved<br />
the problem.<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
=====Thunderbird=====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
==== Calendar CalDAV / iCal ====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf<br />
<br />
<br />
Download the latest Z-push version (see: http://z-push.sourceforge.net).<br />
wget http://download2.berlios.de/z-push/z-push-1.2.2.tar.gz<br />
<br />
Extract the files:<br />
tar -zxvf z-push-1.2.2.tar.gz -C /var/www/html<br />
<br />
'State'-dir needs to be writable for apache:<br />
chmod 755 /var/www/html/z-push/state<br />
chown www:www /var/www/html/z-push/state<br />
<br />
Expand and restart<br />
expand-template /etc/httpd/conf/httpd.conf<br />
sv restart httpd-e-smith<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=== Extras ===<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/<br />
<br />
----<br />
[[Category: Contrib]]<br />
[[Category: Groupware]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=19011
Zarafa on SME 9
2013-02-23T07:34:56Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your application.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.6-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Additional Mobile Synchronization Information====<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=19010
Zarafa on SME 9
2013-02-23T07:24:05Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
z-push now has RPM's built for RHEL6 making the install simple...<br />
<br />
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html<br />
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html<br />
<br />
You will need 2 packages, z-push and z-push-zarafa. Download the latest packages, as of this writing, 2.0.6-1 works without any issue.<br />
<br />
yum localinstall z-push*<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
===Additional Refrences===<br />
<br />
<b>The following is from the original Zarafa page and is provided for reference only. Items below are UNTESTED...</b><br />
<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
====Thunderbird====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
====Calendar CalDAV / iCal====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Additional Mobile Synchronization Information====<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with Android 4.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning? | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18935
Zarafa on SME 9
2013-02-21T08:01:18Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
TO BE CONTINUED!</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18934
Zarafa on SME 9
2013-02-21T07:59:00Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]] [[Category: SME Server 9.0 Development]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
TO BE CONTINUED!</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18933
Zarafa on SME 9
2013-02-21T07:57:49Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]] [[Category: Groupware]] [[Category: Mail]] [[Category: Webapps]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
TO BE CONTINUED!</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18932
Zarafa on SME 9
2013-02-21T07:55:09Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib, Mail]]<br />
[[Category: Groupware]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
TO BE CONTINUED!</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18931
Zarafa on SME 9
2013-02-21T07:53:59Z
<p>Pfloor: </p>
<hr />
<div>[[Category: Contrib]]<br />
[[Category: Groupware]]<br />
{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
TO BE CONTINUED!</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18930
Zarafa on SME 9
2013-02-21T07:51:50Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<This is to remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Now install smeserver-zarafa-unix by performing the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993<br />
<br />
TO BE CONTINUED!</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18929
Zarafa on SME 9
2013-02-21T07:48:37Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm <<Remove the dev rpms, they are not required.<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Install a fresh SME 9 test server and perform the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18928
Zarafa on SME 9
2013-02-21T07:41:27Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Install a fresh SME 9 test server and perform the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18927
Zarafa on SME 9
2013-02-21T07:39:47Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa on SME 9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. Further, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Install a fresh SME 9 test server and perform the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18926
Zarafa on SME 9
2013-02-21T07:39:00Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa_on_SME9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. Further, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Install a fresh SME 9 test server and perform the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18925
Zarafa on SME 9
2013-02-21T07:37:45Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa on SME9}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. Further, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Install a fresh SME 9 test server and perform the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18924
Zarafa on SME 9
2013-02-21T07:36:48Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa}}<br />
{{Level|Advanced}}<br />
{{Note box|This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.}}<br />
{{Warning box|This contrib does not use the standard mail locations of SME. The mail delivery is changed to a new service that uses MySQL to store mail messages and /home/e-smith/files/zarafa/ to store attachments. By default, MySQL and /home/e-smith/files/zarafa/ are included in the standard SME backup schema. Make sure you include these if you have a custom backup schema}}<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. Further, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Install a fresh SME 9 test server and perform the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18923
Zarafa on SME 9
2013-02-21T07:20:12Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa}}<br />
{{Level|Advanced}}<br />
<br />
<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropriate rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| Everything is done automatically for you by the post-install event so you do not need to do anything further. This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Install a fresh SME 9 test server and perform the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To disable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa_on_SME_9&diff=18922
Zarafa on SME 9
2013-02-21T07:18:43Z
<p>Pfloor: Created page with "{{Languages|Zarafa}} {{Level|Advanced}} ===Maintainers=== Paul Floor ===Version=== {{#smeversion:smeserver-zarafa-unix}} ===Description=== http://www.zarafa.com Zar..."</p>
<hr />
<div>{{Languages|Zarafa}}<br />
{{Level|Advanced}}<br />
<br />
<br />
<br />
===Maintainers===<br />
Paul Floor<br />
<br />
===Version===<br />
{{#smeversion:smeserver-zarafa-unix}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
There is an additional interface called zarafa-webapp with additional features<br />
<br />
===Installation===<br />
<br />
====Latest zarafa tested version====<br />
Information on latest and previous versions of zarafa rpms can be found in the [http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt changelog document]<br />
<br />
====Zarafa rpms installation====<br />
<br />
http://download.zarafa.com/community/final/7.1/<br />
<br />
Select the appropraite rhel-6 arch for your hardware.<br />
<br />
Note: The free version contains the free 3 Outlook license version. if you are planning on using or testing this with any outlook clients, you will want to download the free version.<br />
<br />
tar -zxvf zcp*.tar.gz<br />
cd into zcp directory<br />
rm -f *dev*.rpm<br />
yum localinstall *.rpm<br />
<br />
This will also install several dependencies.<br />
<br />
====smeserver-zarafa-unix====<br />
<br />
{{Note box| Everything is done automatically for you by the post-install event so you do not need to do anything further. This is a tested contrib and currently works on SME9alpha1. It should be ready for production servers when SME9 reaches RC stage.<br />
<br />
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}<br />
<br />
Install a fresh SME 9 test server and perform the following:<br />
<br />
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)<br />
<br />
NOTE: On the GPL version you must disable zarafa-licensed...<br />
config setprop zarafa-licensed status disabled <br />
<br />
<br />
After rpm install execute the following:<br />
<br />
signal-event zarafa-post-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
<br />
To diable global Zarafa for all users...<br />
config setprop zarafa-server GlobalForward disabled<br />
signal-event user-modify<br />
<br />
To enable an individual user if Global is disabled...<br />
db accounts setprop $USERNAME zarafa enabled<br />
signal-event user-modify $USERNAME<br />
To enable the admin account...<br />
db accounts setprop admin zarafa enabled<br />
signal-event user-modify-admin<br />
<br />
====Webmail====<br />
Access with a browser,<br />
https://server/zarafa<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
https://server/zarafa-webapp (This is the new Zarafa Webapp with additional features)<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
so imap = 8143, imaps 8993</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa&diff=18920
Zarafa
2013-02-21T05:29:53Z
<p>Pfloor: </p>
<hr />
<div>{{Languages|Zarafa}}<br />
{{Level|advanced}}<br />
<br />
There is a separate page on how to install Zarafa 7.x on SME8 [[Zarafa_on_SME8|here]]<br />
<br />
There is a separate page with a fully automated install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa on SME 9|here]]<br />
<br />
<br />
===Maintainers===<br />
Darrell May<br />
<br />
Stephen Noble http://dungog.net/wiki<br />
<br />
Paul Floor<br />
<br />
=== Version ===<br />
{{#smeversion:smeserver-zarafa}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
<br />
===Installation===<br />
<br />
==== Latest zarafa tested version ====<br />
Information on previous versions of zarafa rpms can be found in the [http://download.zarafa.com/zarafa/release/docs/changelog.en.txt changelog document]<br />
<br />
==== Zarafa rpms installation ====<br />
<br />
http://www.zarafa.com/download-community<br />
<br />
Distribution: Rhel 4 = SME 7 :: Rhel 5 = SME 8<br />
<br />
Select a version, the 3 Outlook license version, or the GPL version. (which doesn't have the zarafa-licensed-*.rpm)<br />
<br />
tar -zxvf zarafa-6.*.tar.gz<br />
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-6*.rpm zarafa-webaccess-*.rpm zarafa-licensed-*.rpm<br />
<br />
This will also install as a dependency: ''sysstat''<br />
{{Note box| You have to enable InnoDB support in MySql in order to get zarafa-server running, for information on how to do so, see [[MySQL#Enable_InnoDB_engine]]}}<br />
<br />
==== smeserver-zarafa ====<br />
<br />
{{Note box| This is an alpha release. Possibly for production servers after testing with per user settings first.<br />
<br />
You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir.<br />
<br />
A minimal amount of disruption can be achieved by enabling per user, that user just enables another IMAP connection in their email client on port 8143, they could then just drag and drop mail between SME to Zarafa mail stores. }}<br />
<br />
Install a fresh SME 7.4 test server and perform the following:<br />
<br />
yum install smeserver-zarafa --enablerepo=smedev<br />
config setprop zarafa-licensed status disabled #GPL version only<br />
<br />
{{Note box|If you installed the GPL version only (without outlook support), you need to create the (empty) file '/var/log/zarafa/licensed.log'. This file is required in all cases. Without this file (and using the GPL non-Outlook version), the Zarafa configuration panel in server manager will not be displayed.}}<br />
<br />
<br />
After rpm install execute the following:<br />
<br />
/etc/e-smith/events/actions/zarafa-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
{{Note box| You will be prompted to select the user plugin you wish to test. We suggest the db method. Note the ldap plugin is currently not supported in the rpm. The unix plugin reads existing SME user details but also includes groups and machine names (messy). The db plugin is pristine however you need to enter all the user details. In both cases the user must exist in SME first as a standard user. A decision on which plugin we will choose for final deployment is still to be determined.}}<br />
<br />
==== Updating ====<br />
Download newer rpms, then<br />
rpm -Uvh zarafa-6*.rpm zarafa-webaccess-*.rpm libvmime-0*.rpm libical-0*.rpm zarafa-licensed-*.rpm<br />
/etc/e-smith/events/actions/zarafa-update<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
===Usage===<br />
====Managing Users====<br />
Enable mail delivery to zarafa for users:<br />
<br />
for all users<br />
config setprop zarafa-server GlobalForward enabled<br />
or for individual users<br />
db accounts setprop $USERNAME zarafa enabled<br />
apply<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
If you chose the db plugin, run:<br />
<br />
/etc/e-smith/events/actions/zarafa-create-user<br />
<br />
or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )<br />
<br />
<br />
====Webmail====<br />
Access with a browser,<br />
<br />
https://server/zarafa<br />
https://server/webaccess<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
<br />
* Outlook 2007 client generates ''Error 0x80070057'' on send and receive if the Zarafa<br />
server is added to an existing profile. Creating a new clean profile solved<br />
the problem.<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
=====Thunderbird=====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
==== Calendar CalDAV / iCal ====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Tasks''' <br />
|-<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/tasks</nowiki><br />
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf<br />
<br />
<br />
Download the latest Z-push version (see: http://z-push.sourceforge.net).<br />
wget http://download2.berlios.de/z-push/z-push-1.2.2.tar.gz<br />
<br />
Extract the files:<br />
tar -zxvf z-push-1.2.2.tar.gz -C /var/www/html<br />
<br />
'State'-dir needs to be writable for apache:<br />
chmod 755 /var/www/html/z-push/state<br />
chown www:www /var/www/html/z-push/state<br />
<br />
Expand and restart<br />
expand-template /etc/httpd/conf/httpd.conf<br />
sv restart httpd-e-smith<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=== Extras ===<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/<br />
<br />
----<br />
[[Category: Contrib]]<br />
[[Category: Groupware]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=SquidGuard&diff=15942
SquidGuard
2011-11-02T00:54:55Z
<p>Pfloor: /* smeserver packaged version */</p>
<hr />
<div>===SquidGuard===<br />
<br />
====smeserver packaged version====<br />
<br />
J Bennett has packaged squidguard into a sme server compatible application.<br />
<br />
If you have not installed the Dag repository please follow this instruction. <br />
{{Repository|Dag}}<br />
<br />
Download smeserver-squidguard-1.0-34.noarch.rpm to a folder on your sme server<br />
wget http://mirror.contribs.org/contribs/jbennett/sme7/squidguard/RPMS/smeserver-squidguard-1.0-35.noarch.rpm <br />
<br />
cd to the folder on your sme server where smeserver-squidguard is located and do<br />
<br />
yum localinstall smeserver-squidguard*.rpm --enablerepo=dag<br />
<br />
That should install the correct package and any dependency rpms it requires. You must have the dag repository configured on your sme server (with status=disabled).<br />
<br />
After installing the packages you must do<br />
signal-event post-upgrade<br />
signal-event reboot<br />
This will restart your server. The web interface will not work if you fail to do the above commands.<br />
<br />
Then use the server manager panel to control it all. There is a DB command to configure the blacklist.<br />
The default blacklist location is http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/contrib/blacklists.tar.gz <br />
<br />
If you wish to change the default blacklist to something else do (for example)<br />
<br />
config show squidguard<br />
config setprop squidguard Blacklist http://www.shallalist.de/Downloads/shallalist.tar.gz<br />
<br />
The supdate script will convert the lists to *.db files which load a lot faster when stopping and starting squidguard.<br />
<br />
Use the content filtering panel in server-manager, to add entries.<br />
You have trusted and untrusted (domains, urls, expressions).<br />
Add your entries, then restart squid with<br />
/etc/rc7.d/S90squid stop<br />
/etc/rc7.d/S90squid start<br />
<br />
You will know when things are ready when you see this in the /var/log/squidguard/squidguard.log file:<br />
<br />
2007-03-18 17:14:54 [3687] squidGuard 1.2.0 started (1174256093.054)<br />
<br />
2007-03-18 17:14:54 [3687] squidGuard ready for requests (1174256094.968)<br />
<br />
<br />
See advice of mrjhb3 here:<br />
<br />
http://forums.contribs.org/index.php?topic=36217.msg160088#msg160088<br />
<br />
====Previous version package information====<br />
<br />
Information about a previous version of squidguard is here:<br />
<br />
URL redirector used to use blacklists with the proxysoftware Squid.<br />
<br />
Mini Howto: http://forums.contribs.org/index.php?topic=34337.msg151745#msg151745<br />
<br />
====References====<br />
<br />
Squidguard Homepage: http://www.squidguard.org/<br />
<br />
----<br />
[[Category:Howto]]<br />
[[Category:Administration:Content Spam Virus Blocking]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Imapsync&diff=15930
Imapsync
2011-10-22T07:59:35Z
<p>Pfloor: /* Install imapsync */</p>
<hr />
<div>=== About ===<br />
imapsync allows you to transfer or synchronize data between any two IMAP servers. This could be used in any of several scenarios:<br />
* Upgrading from one mail server to another (SME -> SME, Exchange -> SME, Notes -> SME)<br />
* Backing up email from one IMAP server to another<br />
* Automated spam learning when using SME with an internal mail server (see the [[#Advanced_Example: Exchange Public Folders|Advanced]] example below).<br />
<br />
<br />
Author: Gilles LAMIRAL <lamiral-at-linux-france.org><br />
<br />
* Author's [http://www.linux-france.org/prj/imapsync/README README]<br />
* Author's [http://www.linux-france.org/prj/imapsync/ChangeLog Change Log]<br />
* Author's [http://www.linux-france.org/prj/imapsync/dist/ Distribution Folder]<br />
* Note about [http://www.linux-france.org/prj/imapsync/BUG_IMAPClient_3.xx Bugs with perl-Mail-IMAPClient-3.x]<br />
<br />
=== Installation ===<br />
==== Enable the dag repository ====<br />
{{Repository|dag}}<br />
(see [[Talk:Dag]] for SME 8)<br />
<br />
==== Install imapsync ====<br />
yum --enablerepo=dag install imapsync<br />
<br />
=== Examples ===<br />
==== Basic Example: Account Duplication ====<br />
This example would copy all existing folders from foo@imap.truc.org to bar@imap.trac.org<br />
/usr/bin/imapsync --noauthmd5 \<br />
--host1 imap.truc.org --user1 foo --passfile1 /etc/secret1 \<br />
--host2 imap.trac.org --user2 bar --passfile2 /etc/secret2<br />
<br />
Bear in mind that you would need to create /etc/secret1 and /etc/secret2 containing the correct passwords for imapuser1 and imapuser2 respectively.<br />
<br />
==== Advanced Example: Exchange Public Folders ====<br />
This example will transfer the public folders 'LearnAsSpam' and 'LearnAsHam' from an Exchange server to the specified user on your SME server.<br />
<br />
If you create and schedule a script to run this command regularly, and combine it with [http://bugs.contribs.org/show_bug.cgi?id=1701#c25 LearnAsSpam.pl] and [http://wiki.contribs.org/Email#Setup_Blacklists_.26_Bayesian_Autolearning|Bayesian Auto-Learning] you could let the users on an internal Exchange Server train your SME spamassassin by dragging SPAM or HAM into public folders in their Outlook.<br />
<br />
Assumptions:<br />
* For the Exchange Server:<br />
** the user '''spamfilter''' exists on the Exchange server<br />
** the password for '''spamfilter''' on the Exchange server is in the file ''/root/secret1''<br />
** the Exchange Server user '''spamfilter''' has ''Owner'' permissions on both ''Public Folders/LearnAsSpam'' and ''Public Folders/LearnAsHam''<br />
* For the SME Server<br />
** the user '''spamfilter''' exists<br />
** the password for '''spamfilter''' on the SME server is in ''/root/secret2''<br />
** the folders ''LearnAsSpam'' and ''LearnAsHam'' exist in the email root for '''spamfilter'''<br />
<br />
=====imapsync command=====<br />
<nowiki>/usr/bin/imapsync \<br />
-- noauthmd5 \<br />
--host1 a.b.c.d --port1 993 --ssl1 --user1 spamfilter --passfile1 /root/secret1 \<br />
--delete --expunge1 --prefix1 "Public Folders." \<br />
--host2 localhost --port2 993 --ssl2 --user2 spamfilter --passfile2 /root/secret2 \<br />
--folder "Public Folders/LearnAsSpam" \<br />
--folder "Public Folders/LearnAsHam" \<br />
--noauthmd5 </nowiki><br />
<br />
====Migrating users and data to Zarafa====<br />
Zarafa migration whitepaper describes various ways of migrating your users and your data to a Zarafa server.<br />
<br />
http://download.zarafa.com/zarafa/release/docs/zarafa_migration.en.pdf<br />
<br />
=====Folder Naming=====<br />
SME and Zarafa use different folder naming. To enhance migration SME folders should be renamed prior to migration.<br />
<br />
drafts > Drafts <br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
=====IMAP migration from SME/IMAP to Zarafa/IMAP=====<br />
By default smeserver-zarafa enables zarafa IMAP on port 8143<br />
<br />
Perform a user mail sync from SME/IMAP (host1/port1) to Zarafa/IMAP (host2/port2) <br />
<br />
imapsync --noauthmd5 --host1 localhost --port1 143 --split1 500 --user1 <username> \<br />
--password1 <password> --sep2 / --prefix2 "" --host2 localhost --port2 8143 \<br />
--split2 500 --user2 <username> --password2 <password><br />
<br />
Example to synchronize a user named 'bob' with password 'bob123' from SME IMAP into Zarafa:<br />
<br />
imapsync --noauthmd5 --host1 localhost --port1 143 --split1 500 --user1 bob \<br />
--password1 bob123 --sep2 / --prefix2 "" --host2 localhost --port2 8143 --split2 500 \<br />
--user2 bob --password2 bob123<br />
<br />
'''Note:''' If the synchronization process terminates, apparently successfully, but only part-way through, delete the dovecot.index.cache file in the last folder copied and restart the process. Adding "--useheader 'Message-ID' --skipsize" to the command above will prevent duplicates if the process does have to be restarted.<br />
<br />
[[Category: Howto]]<br />
[[Category: Mail]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Talk:Zarafa&diff=15030
Talk:Zarafa
2010-06-29T04:28:10Z
<p>Pfloor: /* Sogo */</p>
<hr />
<div>===Sogo===<br />
<br />
FYI, I'm now using [[Sogo]] instead of zarafa, hence I have stopped work on smeserver-zarafa.<br />
<br />
Sogo may not be as complete as zarafa, but is simpler to intergrate/maintain and will likely have a wider usage.<br />
<br />
If zarafa is important to you and no one else wants to maintain the contrib, I'll offer to do it commercially, (if this is inappropriate please remove)<br />
<br />
I will mantain it for now, Paul Floor<br />
<br />
[[User:Snoble|Snoble]] 01:59, 14 March 2010 (UTC)<br />
<br />
=== Suggestions===<br />
If you can advise on standard configuration, please make it a bug so it is added to the rpm<br />
<br />
[[User:Snoble|Snoble]] 07:32, 22 December 2008 (UTC)<br />
<br />
<br />
=== smeserver-zarafa-0.9-48===<br />
<br />
/etc/e-smith/events/actions/zarafa-services-stop has been removed<br />
<br />
/etc/e-smith/events/actions/zarafa-services<br />
Usage: start|stop|restart|enabled|disabled<br />
<br />
start services<br />
stop services<br />
restart services<br />
enabled - set db values to enabled, zarafa will start on reboot<br />
disabled - set db values to disabled, zarafa won't start on reboot<br />
<br />
<br />
InnoDB support is enabled automatically, we need to add this note later<br />
<br />
{{Note box| InnoDB support in MySql has been enabled in order to get zarafa-server running, for details see [[MySQL#Enable_InnoDB_engine]]}}<br />
<br />
=== zarafa-6.40 ===<br />
<br />
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-*.rpm catdoc-*.rpm<br />
<br />
==== indexing service ====<br />
<br />
The catdoc-rpm is needed for the new [http://www.zarafa.com/news/26-jan-zarafa-releases-community-version-its-collaboration-platform-640 indexing service] that is introduced with Zarafa 6.40... but the indexing-service is not yet handled by smeserver-zarafa. --[[User:Jester|jester]] 15:42, 13 February 2010 (UTC)<br />
<br />
the catdoc rpm has un meet dependencies on SME 7 so it's only listed on discussion not the main page, <br />
<br />
yes it's not implemented yet, it'll only be implemented in sme8 unless others find the dependencies<br />
<br />
[[User:Snoble|Snoble]] 01:13, 20 February 2010 (UTC)<br />
<br />
Dependencies are poppler and poppler-utils. Available here:<br />
<br />
ftp://ftp.pbone.net/mirror/apt.kde-redhat.org/kde-redhat/redhat/4/i386/RPMS.stable/poppler-0.5.4-0.3.el4.i386.rpm<br />
<br />
ftp://ftp.pbone.net/mirror/apt.kde-redhat.org/kde-redhat/redhat/4/i386/RPMS.stable/poppler-utils-0.5.4-0.3.el4.i386.rpm<br />
<br />
NOTE: Some poppler versions have been identified with security issues. I didn't have time to look into this version.<br />
<br />
Paul Floor.<br />
<br />
=== SME 8 beta ===<br />
<br />
==== php 5.2.10 ====<br />
<br />
The php mapi files zarafa uses are compiled against 5.1.6, if sme 8 uses 5.2.10 we have a problem<br />
<br />
here is one workaround http://forums.zarafa.com/viewtopic.php?f=9&t=3263&p=18753#p18753</div>
Pfloor
https://wiki.koozali.org/index.php?title=Zarafa&diff=15029
Zarafa
2010-06-29T04:27:19Z
<p>Pfloor: /* Maintainers */</p>
<hr />
<div>{{Languages|Zarafa}}<br />
{{Level|advanced}}<br />
<br />
===Maintainers===<br />
Darrell May<br />
<br />
Stephen Noble http://dungog.net/wiki<br />
<br />
Paul Floor<br />
<br />
=== Version ===<br />
{{#smeversion:smeserver-zarafa}}<br />
<br />
===Description===<br />
http://www.zarafa.com<br />
<br />
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft<br />
Outlook, which enables the sharing of mail and appointments from Outlook and a<br />
web-based interface.<br />
<br />
<br />
===Installation===<br />
<br />
==== Latest zarafa tested version ====<br />
Information on previous versions of zarafa rpms can be found in the [http://download.zarafa.com/zarafa/release/docs/changelog.en.txt changelog document]<br />
<br />
==== Zarafa rpms installation ====<br />
<br />
http://www.zarafa.com/download-community<br />
<br />
Distribution: Rhel 4 = SME 7 :: Rhel 5 = SME 8<br />
<br />
Select a version, the 3 Outlook license version, or the GPL version. (which doesn't have the zarafa-licensed-*.rpm)<br />
<br />
tar -zxvf zarafa-6.*.tar.gz<br />
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-6*.rpm zarafa-webaccess-*.rpm zarafa-licensed-*.rpm<br />
<br />
{{Note box| You have to enable InnoDB support in MySql in order to get zarafa-server running, for information on how to do so, see [[MySQL#Enable_InnoDB_engine]]}}<br />
<br />
==== smeserver-zarafa ====<br />
<br />
{{Note box| This is a beta release. Possibly for production servers after testing with per user settings first.<br />
<br />
You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir.<br />
<br />
A minimal amount of disruption can be achieved by enabling per user, that user just enables another IMAP connection in their email client on port 8143, they could then just drag and drop mail between SME to Zarafa mail stores. }}<br />
<br />
Install a fresh SME 7.4 test server and perform the following:<br />
<br />
yum install smeserver-zarafa --enablerepo=smecontribs<br />
config setprop zarafa-licensed status disabled #GPL version only<br />
<br />
{{Note box|If you installed the GPL version only (without outlook support), you need to create the (empty) file '/var/log/zarafa/licensed.log'. This file is required in all cases. Without this file (and using the GPL non-Outlook version), the Zarafa configuration panel in server manager will not be displayed.}}<br />
<br />
<br />
After rpm install execute the following:<br />
<br />
/etc/e-smith/events/actions/zarafa-install<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
{{Note box| You will be prompted to select the user plugin you wish to test. We suggest the db method. Note the ldap plugin is currently not supported in the rpm. The unix plugin reads existing SME user details but also includes groups and machine names (messy). The db plugin is pristine however you need to enter all the user details. In both cases the user must exist in SME first as a standard user. A decision on which plugin we will choose for final deployment is still to be determined.}}<br />
<br />
==== Updating ====<br />
Download newer rpms, then<br />
rpm -Uvh zarafa-6*.rpm zarafa-webaccess-*.rpm libvmime-0*.rpm libical-0*.rpm zarafa-licensed-*.rpm<br />
/etc/e-smith/events/actions/zarafa-update<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
===Usage===<br />
====Managing Users====<br />
Enable mail delivery to zarafa for users:<br />
<br />
for all users<br />
config setprop zarafa-server GlobalForward enabled<br />
or for individual users<br />
db accounts setprop $USERNAME zarafa enabled<br />
apply<br />
/etc/e-smith/events/actions/qmail-update-user<br />
<br />
If you chose the db plugin, run:<br />
<br />
/etc/e-smith/events/actions/zarafa-create-user<br />
<br />
or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )<br />
<br />
<br />
====Webmail====<br />
Access with a browser,<br />
<br />
https://server/zarafa<br />
https://server/webaccess<br />
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')<br />
<br />
====Outlook====<br />
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz<br />
<br />
<br />
* Outlook 2007 client generates ''Error 0x80070057'' on send and receive if the Zarafa<br />
server is added to an existing profile. Creating a new clean profile solved<br />
the problem.<br />
<br />
====IMAP====<br />
The default ports for Zarafa are 8000 + default values<br />
<br />
so imap = 8143, imaps 8993<br />
<br />
SME and Zarafa use different folder naming.<br />
<br />
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]<br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
=====Thunderbird=====<br />
<br />
The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder, <br />
<br />
Change in the config editor<br />
<br />
Preferences > advance > config editor, find mail.server.number and add new string as below<br />
user_pref("mail.server.server5.port", "8143");<br />
user_pref("mail.server.server5.name", "zac@232.net");<br />
user_pref("mail.server.server5.numHdrsToKeep", 30);<br />
user_pref("mail.server.server5.timeout", 29);<br />
<br />
right click > new<br />
preference name > mail.server.server5.trash_folder_name<br />
value > Deleted Items<br />
<br />
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");<br />
<br />
Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders<br />
<br />
If junkmail exists just delete it.<br />
<br />
==== Calendar CalDAV / iCal ====<br />
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...<br />
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}<br />
<br />
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below<br />
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)<br />
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl3}}|'''URL'''<br />
|{{Hl3}}|'''Calendar''' <br />
|-<br />
|<nowiki>http://server:8089/ical/</nowiki><br />
|user's own default calendar via ical (not recommended)<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|user's own default calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|0ther-user's calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar></nowiki><br />
|user's self created calendar in user's (own) store<br />
|-<br />
|<nowiki>http://server:8089/caldav/<user>/<calendar>/<subcal></nowiki><br />
|user's self created subcalendar in a self created calendar<br />
|-<br />
|<nowiki>http://server:8089/caldav/public/<calendar>/</nowiki><br />
|calendar folder in the public folder<br />
|-<br />
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''<br />
|-<br />
|<nowiki>http://server:8089/caldav/</nowiki><br />
|User's calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/<other-user></nowiki><br />
|Other-users calendar list<br />
|-<br />
|<nowiki>http://server:8089/caldav/public</nowiki><br />
|Public folders list<br />
|-<br />
|}<br />
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.<br />
<br />
====Mobile synchronisation====<br />
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.<br />
<br />
You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf<br />
<br />
<br />
Download the latest Z-push version (see: http://z-push.sourceforge.net).<br />
wget http://download2.berlios.de/z-push/z-push-1.2.2.tar.gz<br />
<br />
Extract the files:<br />
tar -zxvf z-push-1.2.2.tar.gz -C /var/www/html<br />
<br />
'State'-dir needs to be writable for apache:<br />
chmod 755 /var/www/html/z-push/state<br />
chown www:www /var/www/html/z-push/state<br />
<br />
Expand and restart<br />
expand-template /etc/httpd/conf/httpd.conf<br />
sv restart httpd-e-smith<br />
<br />
=====SSL Synchronization with Windows Mobile devices=====<br />
Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.<br />
<br />
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.<br />
<br />
Here are the steps to add your server as a trusted platform on your WM6 mobile :<br />
<br />
<br />
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.<br />
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER<br />
<br />
<br />
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer<br />
<br />
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :<br />
*in microsoft windows open a certificate by double clicking on it<br />
*in "Detail" Tab pane choose "Copy to file" <br />
*Choose Binary coded DER X.509 (.cer) format<br />
*save resulting .cer certificates on local machine<br />
4. transfer .cer certificates on your mobile using windows explorer<br />
<br />
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.<br />
<br />
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.<br />
<br />
=====Know working hardware=====<br />
Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.<br />
<br />
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.<br />
<br />
Tested and working with IPHONE. Push mail not tested.<br />
<br />
Tested and working with Nokia 6120 Classic. Push mail not tested.<br />
<br />
=== Extras ===<br />
====Command line admin====<br />
man zarafa for details<br />
<br />
List users:<br />
/usr/bin/zarafa-admin -l<br />
<br />
Update a user to admin status:<br />
/usr/bin/zarafa-admin -u <username> -a 1<br />
<br />
====Migrating users and data to Zarafa====<br />
<br />
http://wiki.contribs.org/Imapsync<br />
<br />
====Customizing the Calendar====<br />
<br />
The labels and categories in the calendar can be altered to suit user requirements.<br />
<br />
The labels are defined in<br />
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225<br />
The categories are in <br />
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.<br />
<br />
==== Zarafa Bayesian learning ====<br />
<br />
This howto enables SpamAssasin [[:Zarafa Bayesian Learning | Bayesian learning for Zarafa]]<br />
<br />
==== Mail Sorting ====<br />
Maildrop as configured with <br />
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa<br />
<br />
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29, <br />
<br />
==== Backup and restore ====<br />
===== Backup =====<br />
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :<br />
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok<br />
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.<br />
<br />
===== Restore =====<br />
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}<br />
<br />
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.<br />
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :<br />
*stopping zarafa server<br />
/etc/rc.d/init.d/zarafa-server stop<br />
*deleting all tables currently into zarafa database<br />
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \<br />
gawk '{print "drop table " $1 ";"}' | mysql zarafa<br />
*import the backup of zarafa database<br />
cd /directory/containing/your/backup<br />
mysql < zarafa.dump<br />
* restart zarafa server<br />
/etc/rc.d/init.d/zarafa-server start<br />
<br />
=== Bugs ===<br />
Check your logs when troubleshooting or reporting bugs<br />
<br />
tail -f /var/log/zarafa/*<br />
tail /var/log/slapd<br />
tail /var/log/messages<br />
<br />
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.<br />
<br />
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org<br />
<br />
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/<br />
<br />
----<br />
[[Category: Contrib]]<br />
[[Category: Groupware]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=Talk:Zarafa&diff=14343
Talk:Zarafa
2010-03-08T05:59:22Z
<p>Pfloor: /* indexing service */</p>
<hr />
<div>=== Suggestions===<br />
If you can advise on standard configuration, please make it a bug so it is added to the rpm<br />
<br />
[[User:Snoble|Snoble]] 07:32, 22 December 2008 (UTC)<br />
<br />
<br />
=== smeserver-zarafa-0.9-48===<br />
<br />
/etc/e-smith/events/actions/zarafa-services-stop has been removed<br />
<br />
/etc/e-smith/events/actions/zarafa-services<br />
Usage: start|stop|restart|enabled|disabled<br />
<br />
start services<br />
stop services<br />
restart services<br />
enabled - set db values to enabled, zarafa will start on reboot<br />
disabled - set db values to disabled, zarafa won't start on reboot<br />
<br />
<br />
InnoDB support is enabled automatically, we need to add this note later<br />
<br />
{{Note box| InnoDB support in MySql has been enabled in order to get zarafa-server running, for details see [[MySQL#Enable_InnoDB_engine]]}}<br />
<br />
=== zarafa-6.40 ===<br />
<br />
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-*.rpm catdoc-*.rpm<br />
<br />
==== indexing service ====<br />
<br />
The catdoc-rpm is needed for the new [http://www.zarafa.com/news/26-jan-zarafa-releases-community-version-its-collaboration-platform-640 indexing service] that is introduced with Zarafa 6.40... but the indexing-service is not yet handled by smeserver-zarafa. --[[User:Jester|jester]] 15:42, 13 February 2010 (UTC)<br />
<br />
the catdoc rpm has un meet dependencies on SME 7 so it's only listed on discussion not the main page, <br />
<br />
yes it's not implemented yet, it'll only be implemented in sme8 unless others find the dependencies<br />
<br />
[[User:Snoble|Snoble]] 01:13, 20 February 2010 (UTC)<br />
<br />
Dependencies are poppler and poppler-utils. Available here:<br />
<br />
ftp://ftp.pbone.net/mirror/apt.kde-redhat.org/kde-redhat/redhat/4/i386/RPMS.stable/poppler-0.5.4-0.3.el4.i386.rpm<br />
<br />
ftp://ftp.pbone.net/mirror/apt.kde-redhat.org/kde-redhat/redhat/4/i386/RPMS.stable/poppler-utils-0.5.4-0.3.el4.i386.rpm<br />
<br />
NOTE: Some poppler versions have been identified with security issues. I didn't have time to look into this version.<br />
<br />
Paul Floor.<br />
<br />
=== SME 8 beta ===<br />
<br />
==== php 5.2.10 ====<br />
<br />
The php mapi files zarafa uses are compiled against 5.1.6, if sme 8 uses 5.2.10 we have a problem<br />
<br />
here is one workaround http://forums.zarafa.com/viewtopic.php?f=9&t=3263&p=18753#p18753</div>
Pfloor
https://wiki.koozali.org/index.php?title=User_talk:Pfloor&diff=14338
User talk:Pfloor
2010-03-06T20:06:04Z
<p>Pfloor: Blanked the page</p>
<hr />
<div></div>
Pfloor
https://wiki.koozali.org/index.php?title=User_talk:Pfloor&diff=14337
User talk:Pfloor
2010-03-06T20:04:34Z
<p>Pfloor: Created page with '<paypal></paypal>'</p>
<hr />
<div><paypal></paypal></div>
Pfloor
https://wiki.koozali.org/index.php?title=Imapsync&diff=12748
Imapsync
2009-04-17T05:12:55Z
<p>Pfloor: /* IMAP migration from SME/IMAP to Zarafa/IMAP */</p>
<hr />
<div>=== About ===<br />
imapsync allows you to transfer or synchronize data between any two IMAP servers. This could be used in any of several scenarios:<br />
* Upgrading from one mail server to another (SME -> SME, Exchange -> SME, Notes -> SME)<br />
* Backing up email from one IMAP server to another<br />
* Automated spam learning when using SME with an internal mail server (see the [[#Advanced_Example: Exchange Public Folders|Advanced]] example below).<br />
<br />
<br />
Author: Gilles LAMIRAL <lamiral-at-linux-france.org><br />
<br />
* Author's [http://www.linux-france.org/prj/imapsync/README README]<br />
* Author's [http://www.linux-france.org/prj/imapsync/ChangeLog Change Log]<br />
* Author's [http://www.linux-france.org/prj/imapsync/dist/ Distribution Folder]<br />
* Note about [http://www.linux-france.org/prj/imapsync/BUG_IMAPClient_3.xx Bugs with perl-Mail-IMAPClient-3.x]<br />
<br />
=== Installation ===<br />
==== Enable the dag repository ====<br />
{{Repository|dag}}<br />
<br />
==== Install imapsync ====<br />
yum --enablerepo=dag install perl-Mail-IMAPClient-2.2.9 imapsync<br />
<br />
'''IMPORTANT'''<br />
If you install imapsync without specifying perl-Mail-IMAPClient-'''2.2.9''' on the command line as shown above, yum will download and install the latest available version of perl-Mail-IMAPClient - currently 3.x - which does not work according to the author of imapsync. If this happens, you will get an error about IMAPClient every time you run imapsync.<br />
<br />
If you have accidentally installed the wrong version of IMAPClient, you can correct the problem using the command below. When done, reinstall imapsync as shown above.<br />
yum remove perl-Mail-IMAPClient<br />
<br />
=== Examples ===<br />
==== Basic Example: Account Duplication ====<br />
This example would copy all existing folders from foo@imap.truc.org to bar@imap.trac.org<br />
/usr/bin/imapsync \<br />
--host1 imap.truc.org --user1 foo --passfile1 /etc/secret1 \<br />
--host2 imap.trac.org --user2 bar --passfile2 /etc/secret2<br />
<br />
Bear in mind that you would need to create /etc/secret1 and /etc/secret2 containing the correct passwords for imapuser1 and imapuser2 respectively.<br />
<br />
==== Advanced Example: Exchange Public Folders ====<br />
This example will transfer the public folders 'LearnAsSpam' and 'LearnAsHam' from an Exchange server to the specified user on your SME server.<br />
<br />
If you create and schedule a script to run this command regularly, and combine it with [http://bugs.contribs.org/show_bug.cgi?id=1701#c25 LearnAsSpam.pl] and [http://wiki.contribs.org/Email#Setup_Blacklists_.26_Bayesian_Autolearning|Bayesian Auto-Learning] you could let the users on an internal Exchange Server train your SME spamassassin by dragging SPAM or HAM into public folders in their Outlook.<br />
<br />
Assumptions:<br />
* For the Exchange Server:<br />
** the user '''spamfilter''' exists on the Exchange server<br />
** the password for '''spamfilter''' on the Exchange server is in the file ''/root/secret1''<br />
** the Exchange Server user '''spamfilter''' has ''Owner'' permissions on both ''Public Folders/LearnAsSpam'' and ''Public Folders/LearnAsHam''<br />
* For the SME Server<br />
** the user '''spamfilter''' exists<br />
** the password for '''spamfilter''' on the SME server is in ''/root/secret2''<br />
** the folders ''LearnAsSpam'' and ''LearnAsHam'' exist in the email root for '''spamfilter'''<br />
<br />
=====imapsync command=====<br />
<nowiki>/usr/bin/imapsync \<br />
-- noauthmd5 \<br />
--host1 a.b.c.d --port1 993 --ssl1 --user1 spamfilter --passfile1 /root/secret1 \<br />
--delete --expunge1 --prefix1 "Public Folders." \<br />
--host2 localhost --port2 993 --ssl2 --user2 spamfilter --passfile2 /root/secret2 \<br />
--folder "Public Folders/LearnAsSpam" \<br />
--folder "Public Folders/LearnAsHam" \<br />
--noauthmd5 </nowiki><br />
<br />
====Migrating users and data to Zarafa====<br />
Zarafa migration whitepaper describes various ways of migrating your users and your data to a Zarafa server.<br />
<br />
http://download.zarafa.com/zarafa/release/docs/zarafa_migration.en.pdf<br />
<br />
=====Folder Naming=====<br />
SME and Zarafa use different folder naming. To enhance migration SME folders should be renamed prior to migration.<br />
<br />
drafts > Drafts <br />
sent-mail > Sent Items<br />
trash > Deleted Items<br />
junkmail > Junk E-mail<br />
<br />
=====IMAP migration from SME/IMAP to Zarafa/IMAP=====<br />
Configure zarafa for migration enabling IMAP on port 8144 <br />
<br />
Perform a user mail sync from SME/IMAP (host1/port1) to Zarafa/IMAP (host2/port2) <br />
<br />
imapsync --noauthmd5 --host1 localhost --port1 143 --split1 500 --user1 <username> --password1 <password> --sep2 / --prefix2 "" --host2 localhost --port2 8144 --split2 500 --user2 <username> --password2 <password><br />
<br />
Example to synchronize a user named 'bob' with password 'bob123' from SME IMAP into Zarafa:<br />
<br />
imapsync --noauthmd5 --host1 localhost --port1 143 --split1 500 --user1 bob --password1 bob123 --sep2 / --prefix2 "" --host2 localhost --port2 8144 --split2 500 --user2 bob --password2 bob123<br />
<br />
'''Note:''' If the synchronization process terminates, apparently successfully, but only part-way through, delete the dovecot.index.cache file in the last folder copied and restart the process. Adding "--useheader 'Message-ID' --skipsize" to the command above will prevent duplicates if the process does have to be restarted.<br />
<br />
[[Category: Howto]]<br />
[[Category: Mail]]</div>
Pfloor
https://wiki.koozali.org/index.php?title=KnownProblems&diff=11987
KnownProblems
2008-12-26T16:58:10Z
<p>Pfloor: </p>
<hr />
<div>This section is to be used to document problems that cannot or will not be fixed through development of SME7.<br />
<br />
<br />
===Backup/Restore===<br />
<br />
*Using a combination of hardware and software compression for tape backup causes errors<br />
You should use only one of software or hardware compression. Doing both may exercise bugs, and won't reduce the size of data on the tape - it is more likely to increase it. <br />
[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1276860&amp;group_id=96750]]<br />
<br />
<br />
*Backup to desktop 4GB limit<br />
As in previous versions of SME Server, the backup to desktop function has a limit of 4GB. It's not fixable until we know where the limit or limits are. All these components are involved in transferring the backup file, and at least one of them is truncating at 4GB: tar, perl, mod_proxy, apache, TCP stack, browser at desktop end. See this bug listing for details [[ Bugzilla:701 ]]<br />
<br />
===Hardware===<br />
<br />
This is an incomplete list of problems, you can also check the <br />
[[:SME_Server:Documentation:FAQ#Hardware_Compatibility_List | Hardware_Compatibility_List]]<br />
<br />
====Problem with NIC card or integrated NIC.====<br />
If your NIC card isn't working, replace it with a different one. If your integrated NIC isn't working, disabling onboard lan and inserting pci network card works.<br />
<br />
Problem reports have been submitted with the following NIC's:<br />
<br />
*Realtek 8169 Ethernet is not recommended, The driver included in CentOS 4.1 is out of date and has problems.<br />
<br />
*Two identical Realtec nic's caused a kernal panic, Model unknown<br />
<br />
*Intel 82573L Gigabit Ethernet says the e1000 driver should work but doesn't <br />
<br />
*3com 905 (Cyclone) Ethernet is not recommended. This card 'may' not be detected though a site<br />
has reported success (0000:00:0d.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xb800. Vers LK1.1.19).<br />
<br />
*D-Link DGE-530T Rev-B1 on SME 7.1 does not work.<br />
<br />
*D-Link DFE-530TXS rev. A1 Ethernet adaptor not recognized (a.k.a. DL10050, Sundance)<br />
[[http://sourceforge.net/tracker/index.php?func=detail&amp;aid=1359597&amp;group_id=96750&amp;atid=615772 sourceforge]]<br />
[[https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154349 redhat]]<br />
<br />
====Systems or motherboards may need a bios update or are unsupported====<br />
*2001 CUSI-M motherboard - bios<br />
<br />
*Tyan S2850G2N with AMD Opteron 160, BIOS update >= 112 <br />
<br />
*Compaq ProLiant 6400R's see [[bugzilla:2175]]<br />
<br />
*Asus TUSL2-C intel 815ep atx motherboard - [[bugzilla:3033]]<br />
<br />
*Intel board D946GZIS - unsupported<br />
<br />
*Boards using a Dual Pentium Pro are unlikely to work<br />
<br />
*ASUS P5VD2-VM Motherboard - unsupported [[bugzilla:3086]]<br />
<br />
====SATA II drives are not fully supported====<br />
We suggest jumpering sata 300 drives to 150 until there is a newer kernel that supports them and/or the controllers better<br />
<br />
====Boot options for install====<br />
See [[:Booting#Installer Boot Options]].<br />
<br />
====Unsorted====<br />
*Losing too many ticks<br />
A kernel bug with Athlon64 processors may cause the system to run slowly, possibly fixed with a later kernel<br />
<br />
<br />
*VGA problem with VIA EPIA board<br />
Once the installer loads the VGA display loses sync and it is impossible to read what is being displayed. There is a workaround, see this bug report for details: [[ Bugzilla:236 ]]<br />
<br />
<br />
*VIA EPIA CL1000 (dual LAN, single processor)<br />
The smp kernal fails to boot - non-smp works like a charm...<br />
<br />
<br />
*Slow Disk Format<br />
Installing 2 discs as Primary and Secondary on the same IDE channel may cause<br />
slow formatting and is not a very good idea because:<br />
<br />
1-May hamper system performance.<br />
<br />
2-Does not provide system redundancy if you loose the IDE channel.<br />
<br />
<br />
*Why does my clock run too fast in SME Server under VMware?<br />
If you are testing SME Server on VMware, you may notice the clock doen't keep time accurately. See this bug report for details and a possible fix. <br />
[[http://sourceforge.net/tracker/index.php?func=detail&amp;aid=1303401&amp;group_id=96750&amp;atid=615772]]<br />
Perhaps this might be of use: [http://synapticsolutions.com.au/?page_id=28 <nowiki>Synaptic: Clock Running fast in CentOS 4.3 [SME7] Guest</nowiki>]<br />
<br />
<br />
*Boot failure after install if you have enabled hardware raid<br />
There sometimes seem to be conflicts with the SME Server automatic software raid setup in combination with hardware raid. Disabling the hardware raid in your motherboard or controller card's bios is the suggested fix. See these bug reports for details: <br />
[[https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1286560&amp;group_id=96750&amp;atid=615772]]<br />
[[https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1304784&amp;group_id=96750&amp;atid=615772]]<br />
<br />
<br />
*Booting in SMP mode results in kernel panic with certain hardware<br />
The combination of a 2MB Cache P4 3.0GHZ CPU, and a Giga-byte GA-81848P775-G (Intel 848P chipset) motherboard produces this problem. Other simialar hardware may be affected. If you encounter this problem, see this bug report for a workaround. <br />
[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1325350&amp;group_id=96750]]<br />
<br />
<br />
*Legacy ~MegaRAID driver is no longer included<br />
Certain raid cards that worked under SME Server 6, do not work under SME Server 7. <br />
<br />
Adapters with the following PCI vendor ID and device ID pairs are not supported by the megaraid_mbox driver: vendor, device = 0x101E, 0x9010; 0x101E, 0x9060; 0x8086, 0x1960. The lspci -n command can be used to display the IDs for adapters installed in a particular machine. Products with these IDs are known by (but not limited to) the following model names: Broadcom 5820, Dell PERC (dual-channel fast/wide SCSI) RAID controller, Dell PERC2/SC (single-channel Ultra SCSI) RAID controller, Dell PERC2/DC (dual-channel Ultra SCSI) RAID controller, Dell CERC (four-channel ATA/100) RAID controller, DRAC 1, MegaRAID 428, MegaRAID 466, MegaRAID Express 500, HP NetRAID 3Si and 1M. <br />
<br />
Both Dell and LSI Logic have indicated that they no longer support these models in the 2.6 kernel. As a result, these adapters are no longer supported in Red Hat Enterprise Linux 4 Update 1, upon which SME Server 7 is based. <br />
<br />
See this bug listing for details, there is an unsupported workaround if needed: <br />
[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1274199&amp;group_id=96750]]<br />
<br />
*Raid on HP server Proliant ML330 with adaptec RAID is unsupported<br />
<br />
*aic7xxx driver hangs on installation boot<br />
On some Compaq Proliant servers (specifically an ML370 G2), &amp; possibly others, the aic7xxx driver will hang if there is nothing connected to the adaptor or if it is not terminated correctly. On most Proliants you can tell the BIOS to not allocate an IRQ to the device which effectively disables it; the ML370 G2 uses an AIC-7899 chip on the motherboard. This problem also exists in the ~CentOS 4.3 base. SME 6.0 loads fine which would seem to indicate that the newer driver in ~CentOS 4.3 can't handle the older system (this Proliant is probably 5 years old). [[Bugzilla:373]]<br />
<br />
<br />
*Anaconda doesn't support >2Tb<br />
Installing on large storage devices will take a significant amount of work. see [[Bugzilla:1963]]<br />
<br />
<br />
*Older systems stop at reboot<br />
This may be an issue from the older P2 and early P3 era BIOS'es but the problem may also occur on some newer chipsets, that don't follow the "specs" for power saving features. Also, this problem seems to be more prevalent in multi-CPU machines. Only a kernel change could provide a real fix to this issue.<br />
For some motherboards, there may be a workaround by adding appropriate text to the grub config.<br />
The addition of the noapic and acpi=off to etc/grub.conf might solve the problem of reboots failing.<br />
<br />
<br />
*I'm burning the SMESERVER cd. When I check the md5sum on this burner, it returns an *incorrect* value. What gives?<br />
Try a different cd burner. We've found in the past that some drives provide an extra garbage block when reading back the image. This results in an incorrect md5sum value.<br />
<br />
<br />
*I'm trying to use an old tape drive with my SMESERVER but I can't get it working. What gives?<br />
SMESERVER does not provide ide-tape (which is deprecated by Dell and RedHat).<br />
<br />
<br />
*My Adaptec DPT raid controller is not migrated on upgrade. What gives?<br />
The Adaptec DPT raid controller won't work for upgrades. However, the Adaptec DPT raid controller works on new installs. For details visit: [[http://bugs.contribs.org/show_bug.cgi?id=833]]<br />
<br />
<br />
*I've loaded the SMESERVER into my hardware without problems. Now my SMESERVER freezes when I reboot. What gives?<br />
Most likely this is a problem with the video card or sound card. The best fixes are to replace the video/sound card, disable the video/sound in the bios (if it's integrated on the motherboard) or remove the video/sound card altogether. Video/sound isn't needed on the SMESERVER and can be managed via the SERVER-MANAGER. <br />
<br />
Please note that other hardware devices such as CD-ROM drives as well as mismatched IDE cables may cause a problem, (i.e. kernel panic on reboot after installation). For details, visit:[[http://bugs.contribs.org/show_bug.cgi?id=985]]<br />
<br />
<br />
*My SMESERVER suddenly stopped working. I look in the log messages I see: kernel: ata1: command 0x35 timeout, stat 0x50 host_stat 0x1. Any ideas what could be causing this?<br />
Most likely, this is either a hardware or BIOS problem or a kernel bug. It's very unlikely we can fix any of those. However, you can try editing /etc/grub/grub.conf. In this file, close to the top, you'll see the latest kernel. It looks like this: <br />
kernel /vmlinuz-2.6.9-42.0.10.EL ro root=/dev/vg_primary/lv_root<br />
Add "noapic" to the end. It should look like this:<br />
kernel /vmlinuz-2.6.9-42.0.10.EL ro root=/dev/vg_primary/lv_root noapic<br />
Then reboot. Hopefully the problem goes away.<br />
<br />
<br />
*Is there a problem installing SMESERVER with my NFORCE motherboard?<br />
Submitted reports claim that nForce boards based on the 410 or 430 chipset won't work [[http://bugs.contribs.org/show_bug.cgi?id=1240]].<br />
<br />
<br />
*Is there a problem installing SMESERVER with my ZIP drive?<br />
Submitted reports claim that installing SMESERVER on a system with a ZIP drive won't work [[http://bugs.contribs.org/show_bug.cgi?id=1348]].<br />
<br />
<br />
*Is there a problem installing SMESERVER with my laptop?<br />
SME Server has never supported laptop PCMCIA network adaptors. This being said, some possible workarounds have been identified in [[Bugzilla:1246]]<br />
<br />
<br />
*Symbios 53c895 scsi raid card<br />
This is a hardware issue. It worked with SME6 but doesn't work with SME7.<br />
<br />
===Installation (not hardware related) &amp; Initial Configuration===<br />
<br />
*Why is there a delay after verifying administrator password?<br />
On "slow" system, there is a delay (2-5 seconds) after verifying administrator password. This is because the password is actually set and checked at this point. Everything else we wait until the script is done to perform any actions. <br />
[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1264659&amp;group_id=96750]]<br />
<br />
<br />
*Use /server-manager, not /e-smith-manager<br />
In previous versions, both aliases worked, but in SME Server 7 you must use /server-manager to access the server manager. <br />
[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1275334&group_id=96750]]<br />
<br />
<br />
*Why can the system not be named 'mail', 'ftp' or 'www'?<br />
If you choose one of these for the hostmane of your server, the atalk (Appletalk) service will have errors and fail. See these bug listings for details: <br />
[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1223012&amp;group_id=96750]] [[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1264588&amp;group_id=96750 <br />
<br />
<br />
*Why is there no option to create reinstallation disk?<br />
There is no option to create a reinstallion disk during installation or later from the Administration section of the server-manager. <br />
This is intentional, since it required too much effort to keep it up-to-date as kernels change. The CD contains a rescue mode, which is a better environment for fixing problems, and a reinstall followed by a restore of the configuration works well without us supporting another method. <br />
Additionally, the kernel has grown too large for a floppy plus initrd. Even Redhat installs no longer offer to create a boot floppy at install time. <br />
More details can be found in [[Bugzilla:792]].<br />
<br />
<br />
*4 disk install - md1 is raid1 and md2 is raid5<br />
Even if you have 4 (or more) disks, which are supported by your motherboard and ~CentOS, md1 is always set up as a 4 disk raid1. This is, because you can't boot off a raid-5. md1 is the boot partition and must either be non-raid or raid-1. md2 will be set up as a 4 disk raid5 as expected. <br />
More information can be found in [[Bugzilla:759]].<br />
<br />
<br />
*Anaconda crash from rescue mode when starting network interfaces<br />
There is a problem with the installer and as networking is not essential for a rescue function it won't be fixed any time soon. Note however that this is no longer an issue with version 7.2. [[Bugzilla:712]]<br />
<br />
<br />
*On first boot after installation, system name appears on terminal 1 while on terminal 2 and 3 it shows as "localhost". <br />
This is because the gettys on tty2 and tty3 are started before the configuration wizard runs, and therefore before the system name has been set. Also note that the correct system name is displayed after someone logs out from VT2 or VT3?)<br />
<br />
<br />
*The installation gave an exception when trying to format already formatted disks.<br />
In some cases, you may have to manually wipe re-used disks.<br />
<br />
===Services===<br />
<br />
====Restarting NUT====<br />
*My UPS doesn't work although its status says that it's running. What gives?<br />
Rather than: <br />
service nut restart<br />
Use: <br />
service nut stop<br />
<wait a few seconds><br />
service nut start<br />
Details: http://bugs.contribs.org/show_bug.cgi?id=2738</div>
Pfloor
https://wiki.koozali.org/index.php?title=SME_Server:Documentation:FAQ&diff=11758
SME Server:Documentation:FAQ
2008-12-09T00:46:49Z
<p>Pfloor: /* Proxy Pass */</p>
<hr />
<div>{{Languages|SME_Server:Documentation:FAQ}}<br />
<br />
==Frequently Asked Questions==<br />
<br />
This Section lists ''Frequently Asked Questions'' (FAQ) for SME 7. Problems many people run into installing SME 7 for the first time or upgrading to later versions are found here.<br />
<br />
If your question isn't listed here, it's possible it's a ''Rarely Asked Question'' (RAQ), in which case you'll be better off searching for answers in [http://bugs.contribs.org Bugzilla]. <br />
<br />
===Installation troubles===<br />
====Installer prompts for installation file location====<br />
Problems have been reported installing SME Server off a PATA CD-ROM drive. The system is able to boot from the CD-ROM drive but after that you get prompted by a message to specify the location where the installation image can be found. This might either mean that the disk is not readable or the CD-ROM drive is not recognized.<br />
If you have validated the disk and are sure that the disk passes you might try to add the all-generic-ide option to the boot prompt before starting the installer like this:<br />
linux all-generic-ide<br />
<br />
===Yum Updates===<br />
==== Which repositories should be enabled====<br />
<br />
You should have the following repositories enabled (blue)<br />
CentOS - os<br />
CentOS - updates<br />
SME Server - addons<br />
SME Server - extras<br />
SME Server - os<br />
SME Server - updates.<br />
<br />
DO NOT enable '''SME Server - updates testing''' which is considered beta, unless<br />
* it is a TEST server NOT a production server or<br />
* you want to be part of a bug-testing group.<br />
<br />
Additionally <br />
* '''SME Server - test''' is considered alpha <br />
* '''SME Server - dev''' contains automatically built rpms. It contains lots of experimental,<br />
incomplete and mutually incompatible packages.<br />
<br />
{{Warning box|msg=If upgrading from a system prior to 7.1 update 1, ie a 7.1 CD install or earlier,<br />
you need to ensure you have the latest versions of the following rpms prior to applying the rest of the updates.<br />
This speeds up install process and avoids updates from centos that may be ahead of the distribution.<br />
<br />
yum update dbus dbus-glib smeserver-support smeserver-yum yum yum-plugin-fastest-mirror python-sqlite <br />
signal-event post-upgrade; signal-event reboot<br />
}}<br />
<br />
{{Note box|A system installed from the SME 7.1 CD will have the 5 repositories above enabled. A system installed from the SME 7.0 iso and updated to 7.1 or later will only have the 3 SME Server repositories enabled. After updating from SME 7.0 to SME 7.1.x you should enable the ''Centos - os'' & ''Centos - updates'' repositories in server-manager.<br />
}}<br />
<br />
*For another way to reset the repositories to the default see [[:Adding_Software#Restoring_Default_Yum_Repositories]]<br />
<br />
====Reconfigure / post-upgrade and reboot====<br />
*When is a post-upgrade and reboot required?<br />
The server manager yum installer has no way of determining whether<br />
any configuration files will change if all are re-expanded or to know which<br />
binaries have changed (or use libraries which have now changed) and therefore<br />
need to be restarted. The only '''safe''' option is to reconfigure and restart<br />
everything.<br />
<br />
After clicking '''Reconfigure''' check the Status message and that the server does actually reboot.<br />
Rarely circumstances arise that prevent the reconfigure from triggering. If so run the following,<br />
<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
====Updating from SME 7.x to SME 7.2====<br />
See [[:Updating_to_SME_7.2#Yum_Update]]<br />
<br />
<br />
<br />
====General====<br />
*Please Wait - Yum Running (prereposetup)<br />
This means Yum is working out what updates are available.<br />
Occasionally such as when large sets of updates are released this could take 10+ minutes to complete<br />
<br />
*Yum doesn't seem to be working correctly. What do I do now?<br />
If for some reason you can't get yum to work correctly, try:<br />
yum clean metadata<br />
or possibly 'yum clean all'<br />
yum update<br />
<br />
*Fix for 'Metadata file does not match checksum'<br />
Typical error message<br />
http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz: <br />
[Errno -1] Metadata file does not match checksum Trying other mirror.<br />
Error: failure: repodata/primary.xml.gz from dag: [Errno 256] No more mirrors to try.<br />
<br />
To flush the up stream proxies, using wget, run:<br />
<br />
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/filelists.xml.gz<br />
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz<br />
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/repomd.xml<br />
yum update<br />
<br />
* An unclean shutdown during a system update can put the system into a state where it's difficult to recover.<br />
find all the duplicate rpm's<br />
rpm -qa | sort | less <br />
Then remove all the duplicate rpm's<br />
rpm -e --nodeps rpmname<br />
Install the newest rpms <br />
yum install rpmname<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
* Where can I go to learn more about yum, and about how SME uses it?<br />
[[:Adding_Software ]], man yum, http://linux.duke.edu/projects/yum/<br />
<br />
====Adding, removing or disabling repositories ====<br />
<br />
*What is the recommended way to add other yum repositories<br />
The following code uses the dag repository as an example and sets the status to disabled. <br />
The repository is configured to be used via the command line with the --enablerepo= option <br />
{{Repository|dag}}<br />
<br />
*How do I remove yum repositories<br />
<br />
db yum_repositories delete repositoryname<br />
signal-event yum-modify<br />
<br />
*How do I disable a repository to allow future use via command line with the --enablerepo= option<br />
<br />
db yum_repositories repositoryname setprop status disabled<br />
signal-event yum-modify<br />
<br />
====Other popular repositories====<br />
<br />
http://wiki.contribs.org/Category:Yum_Repository<br />
<br />
Be careful updating software from these repositories. Only update packages by name eg.<br />
yum update --enablerepo=reponame packagename<br />
<br />
Do not do a general update with the 3rd party repository enabled as it could update many packages that will overwrite SME versions.<br />
<br />
===Hardware Compatibility List===<br />
[http://wiki.contribs.org/KnownProblems#Hardware List of Hardware that known have problems with SME Server]<br />
<br />
Maintaining a complete HCL is difficult, <br />
the following links will give a indication of hardware being used by SME Servers and upstream providers<br />
<br />
*https://hardware.redhat.com/index.cgi<br />
*http://smolt.contribs.org<br />
*http://wiki.centos.org/HardwareList<br />
<br />
===Client Computers===<br />
<br />
*Samba trust relationships lost?<br />
This is a possible bug with an upgrade from SME6. After an upgrade, local workstations cannot log in. If you are experiencing this problem, please have a look at this bug for a fix, and provide followup: <br />
[https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1234009&amp;group_id=96750&amp;atid=615772]<br />
<br />
<br />
*Windows XP Clients - Patch to logon to SME domain<br />
This patch can be used when Windows XP clients won't be able to log on to the SME Server domain. The registry patch is located here: <br />
http://servername/server-resources/regedit/winxplogon.reg<br />
Double click on the winxplogon.reg file and the settings will be added to the Windows Registry.<br />
<br />
<br />
*How to disable password caching on Windows 95/98/ME/2000 Clients?<br />
This patch can be used if you don't want Windows clients to remember password for shared folders on SME Server. The registry patch is located here: http://servername/server-resources/regedit/win98pwdcache.reg <br />
Just double click on the win98pwdcache.reg file and the settings will be added to the Windows Registry. <br />
<br />
'''Note'''<br />
Although the filename seems to indicate that this patch will only work for Windows 98, but it also works in Windows 95, Windows ME and Windows 2000.<br />
<br />
<br />
*LDAP Directory Gives MAPI_E_CALL_FAIL Errors on Outlook 2002 or Outlook 2003<br />
In Outlook 2002 or 2003 when someone tries to find a contact using the LDAP server, a message stating that "Unavailable critical extension" and then a second message saying "The search could not be completed. MAPI_E_CALL_FAIL" shows up and nothing shows up from the search. The directory works beautifully in Thunderbird 1.5 as well as Outlook 2000, but not 2002 or 2003. More information can be found here: [http://support.microsoft.com/default.aspx?scid=kb;en-us;555536&amp;sd=rss&amp;spid=2559] [http://bugs.contribs.org/show_bug.cgi?id=1406]<br />
<br />
<br />
*Where is the netlogon directory?<br />
The netlogon directory is located on the SMESERVER at: /home/e-smith/files/samba/netlogon<br />
It can also be found by a client computer at: \\servername\netlogon<br />
<br />
===Web Applications===<br />
*chmod 777<br />
<br />
Using 777 is always wrong (despite the fact that many howtos recommend it). 0770 is sufficient, as long as www is a member of the group owning the directory, and is safer.<br />
<br />
Use chown www /path/to/dir <br /><br />
and preferably put your app in /opt/app not in an ibay <br />
<br />
* Generic Instructions for Installing a Web Application<br />
http://wiki.contribs.org/Generic_WebApp_rpm<br />
<br />
*Wasn't mod_perl installed in previous versions? How do I install it?<br />
It may have been, but it was not used so it is no longer included. If you do want to install it do the following:<br />
<br />
'''Note'''<br />
The commands on a linux shell are case-sensitive, this means that Capital is not the same as capital.<br />
<br />
yum install mod_perl<br />
config setprop modPerl status enabled<br />
signal-event post-upgrade ; signal-event reboot<br />
<br />
*The directory structure is visible. How do I disable indexes in ibays?<br />
SME Server 6.0, 6.0.1, and 6.5 all had the following for the ibays/html directory - "Options Indexes Includes". This would indicate that indexes were allowed for html directories. In SME Server 7.0 this is made a parameter and it defaults to enabled to be compatible with SME Server releases before SME Server 7.0 installations. <br />
<br />
To disable indexes for an ibay in SME Server 7.0 do the following:<br />
<br />
db accounts setprop //ibayname// Indexes disabled <br />
signal-event ibay-modify //ibayname// <br />
<br />
This issue was first reported here: <br />
[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1275351&amp;group_id=96750]]<br />
<br />
*I need to create (or install) a PHP application that needs access to the /tmp directory.<br />
db accounts setprop ibayname PHPBaseDir /tmp/:/home/e-smith/files/ibays/ibayname/<br />
signal-event ibay-modify ibayname<br />
<br />
By default if you have PHP code in an IBAY, it can only run in that IBAY. The above commands will allow PHP code in the IBAY to run outside of its installed directory. <br />
<br />
Here is a list of all the [[:DB_Variables_Configuration#Apache_server_ibay_specific_.28httpd-e-smith.29 | IBAY specific settings]]<br />
<br />
===Reset the root and admin password===<br />
<br />
1. Restart your server and at the beginning of the boot-up use the arrow keys to select the kernel you would like to boot into.<br />
<br />
2. Press A , to allow you to append parameters to your grub boot settings.<br />
<br />
3. Be careful not to change anything, only add the following after the A (Be sure to put a space before single):<br />
single<br />
4. Press enter. you will be presented with a prompt.<br />
<br />
5. At this prompt type the following two commands (each followed by a return). You will be asked to provide a new password. <br />
Reset both your root and your admin password and set them to the same value:<br />
passwd root<br />
passwd admin<br />
Reboot your server and everything should be okay now.<br />
<br />
<br />
===File Size Limitations===<br />
*Apache, the web server can only transfer or show files under 2G<br />
<br />
*Backup to USB Disk<br />
FAT32 only supports file size of <4GB. It is recommended that you format your external usb drives to ext3.<br />
<br />
<br />
===Domains===<br />
<br />
*When I create a DOMAIN, I don't see anything listed in the HOSTNAMES AND ADDRESSES panel for that DOMAIN.<br />
<br />
For a domain to be effective (for email or web), it needs to be configured as INTERNET DNS SERVERS (this is the default value). Since the domain resolves via INTERNET DNS SERVERS, no hostnames or addresses are created locally. For more info please visit the Administration Manual section regarding Domains: [[http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter13#Domains]]<br />
<br />
<br />
===Virus Scanning===<br />
*When you elect to nightly scan your server for viruses the current default is to scan /home/e-smith/files<br />
<br />
Note that early SME 7 Servers defaulted to /. <br />
<br />
Also you may want to scan under /opt if have contribs that store user data there<br />
<br />
the db property to change to the default <br />
config setprop clamav FilesystemScanFilesystems /home/e-smith/files<br />
or to scan different areas of the server is<br />
config setprop clamav FilesystemScanFilesystems /home/e-smith/files,/opt<br />
<br />
*How do I exclude some directories from scanning<br />
Set the db value to exclude more directories<br />
<br />
The default<br />
config setprop clamav FilesystemScanExclude /proc,/sys,/usr/share,/var<br />
<br />
Change with<br />
config setprop clamav FilesystemScanExclude /proc,/sys,/usr/share,/var,/home/e-smith/files/ibays<br />
<br />
After any change, run the signal-event for expand and regenerate configuration files, and restart pertinent services<br />
<br />
signal-event clamav-update<br />
<br />
===Proxy Pass===<br />
<br />
*I want to pass some http requests to a server behind my SME Server or external to my site, how can I do this?<br />
<br />
You can set a ProxyPass directive that will pass certain requests to an internal or external server that hosts the domain to be proxypassed:<br />
db domains set proxypassdomain.com domain <br />
db domains setprop proxypassdomain.com Nameservers internet<br />
db domains setprop proxypassdomain.com ProxyPassTarget http://xxx.xxx.xxx.xxx/<br />
db domains setprop proxypassdomain.com TemplatePath ProxyPassVirtualHosts <br />
signal-event domain-create proxypassdomain.com<br />
where proxypassdomain.com is the domain name hosted on the internal or external server<br />
and http://xxx.xxx.xxx.xxx/ is the IP address of the internal or external server eg 192.168.1.20 or 122.456.12.171 (it must be the publicly accessible IP if an external server)<br />
<br />
<br />
To delete a ProxyPass directive that you previously set up:<br />
db domains delete proxypassdomain.com<br />
signal-event domain-delete proxypassdomain.com<br />
<br />
{{Note box|If you have added the internal or external server's domain name as a virtual domain on the SME Server, you must remove it prior to issuing these commands. The server-manager domains panel will show the proxy pass entry but you will not be able to edit it, see [[bugzilla:1612]].<br />
}}<br />
<br />
===Shell Access===<br />
*I need to give a user shell access to the SME Server.<br />
<br />
Shell access should only be provided to users who have a *need* for it and can be trusted. <br />
<br />
Before a user can have shell access Admin must enable ssh access at <br />
server-manager -> Security -> Remote Access<br />
<br />
You then enable shell access for a user by:<br />
db accounts setprop username Shell /bin/bash<br />
chsh -s /bin/bash username<br />
<br />
===Upgrading Server===<br />
*What's the best way to upgrade to a new server ?<br />
An article is written for this subject. Please visit: http://wiki.contribs.org/UpgradeDisk<br />
<br />
===Changing maximum Ibay, Account or Group name length===<br />
* How do I change the default maximum (12 characters) name length of an I-Bay, account or group?<br />
Enter following command on the console as root:<br />
/sbin/e-smith/db configuration set maxIbayNameLength xx<br />
/sbin/e-smith/db configuration set maxAcctNameLength xx<br />
/sbin/e-smith/db configuration set maxGroupNameLength xx<br />
where 'xx' is the new size e.g. 15.<br />
<br />
Followed by:<br />
/sbin/e-smith/signal-event console-save<br />
<br />
===Deletion of Users Ibays Groups===<br />
*I can't delete & create a user for some reason. What do I do now?<br />
If for some reason you can't delete & create a user, then first do:<br />
signal-event user-delete <username><br />
db accounts delete <username><br />
<br />
*I can't delete & create a ibay for some reason. What do I do now?<br />
If for some reason you can't delete & create a ibay, then first do:<br />
signal-event ibay-delete <ibayname><br />
db accounts delete <ibayname><br />
<br />
*I can't delete & create a group for some reason. What do I do now?<br />
If for some reason you can't delete & create a group, then first do:<br />
signal-event group-delete <groupname><br />
db accounts delete <groupname><br />
<br />
<br />
*I was looking in the home directory of a user and I see a hidden directory called ".junkmail". Do I need that? Can I delete it?<br />
Don't remove or rename .junkmail folders.<br />
<br />
===Password Strength Checking===<br />
*How can I change password strength & what do the strength settings mean?<br />
<br />
{{Warning box|It is strongly advised not to set the password strength setting to ''none'' as this will lower the security of your server significantly.}}<br />
<br />
{{Note box|PAM module requires passwords to be at least 6 characters long, so setting a password that is shorter than that may cause other problems later. SME server default settings enforce 7 character passwords.}}<br />
<br />
The following settings are available to specify the password strength on SME Server:<br />
<br />
{|<br />
! setting<br />
! explanation<br />
|- <br />
| ''strong'' <br />
| The password is passed through Cracklib for dictionary type word checking as well as requiring upper case, lower case, number, non alpha and a mimimum length of 7 characters.<br />
|- <br />
| ''normal''<br />
| The password requires upper case, lower case, number, non alpha and a minimum length of 7 characters.<br />
|- <br />
| ''none''<br />
| The password can be anything as no checking is done.<br />
Please note that "none" does not mean no password, it just means no password strength checking, so you can enter any (weak) password you want as long as it is at least 7 characters long.<br />
|}<br />
<br />
To set password strength do:<br />
config setprop passwordstrength Admin strengthvalue<br />
config setprop passwordstrength Users strengthvalue<br />
config setprop passwordstrength Ibays strengthvalue<br />
where strengthvalue is one of the entries listed in the table above.<br />
<br />
e.g. <br />
config setprop passwordstrength Users normal<br />
<br />
To review the current settings do:<br />
config show passwordstrength<br />
<br />
which should display something like:<br />
<br />
passwordstrength=configuration<br />
Admin=strong<br />
Ibays=strong<br />
Users=strong<br />
<br />
References:<br />
<ol></li><li>[https://sourceforge.net/tracker/?func=detail&atid=615772&&aid=1228269&group_id=96750 Old Bugtracker on SF.net: Sme7a22 - user passwords]<br />
</li><li>[[Bugzilla:161]]</li><br />
<li>[[Bugzilla:2686]]</li></ol><br />
<br />
<br />
===Hard Drives, RAID's, USB Hard Drives===<br />
*How should I setup my hard-drives?<br />
We never recommend anything other than a '''single disk install''' or '''multiple disks of the same type'''. Anything else and you are following an unrecommended setup and you will need to navigate for yourself. Repeat, we never recommend anything other than a '''single disk install''' or '''multiple disks of the same type'''. If you're thinking of doing anything else (setup your own partitions), read this section again.<br />
<br />
*How should I setup my RAID?<br />
A full article on RAID is found here: [[:Raid]]<br />
<br />
<br />
*I want to use a hardware RAID. What do you suggest?<br />
Please see the notes in the RAID article: [[:Raid#Raid_Notes]]<br />
<br />
<br />
*How do I recover an SME Server with lvm drives<br />
A full article on the recovery method is found here: [[:Recovering_SME_Server_with_lvm_drives]]<br />
<br />
<br />
*I'm installing a RAID 5 but it seems to take a long time. Is there something wrong?<br />
RAID 5 systems (those with 3+ disks) can take a long time during and after the install for everything to sync. Reportedly, it takes almost 2 hours before the disks finally finish syncing on 4 X 80GB disks.<br />
<br />
<br />
*If I boot my SMESERVER with a USB hard drive attached, it recognizes the drive. However, after unplugging the drive, then replugging, it no longer exists. Any ideas why?<br />
Reportedly, some external usb hd's must be completely powered up before connecting the usb cable.<br />
<br />
<br />
*If I boot my SMESERVER with a USB hard drive attached, it doesn't recognize the drive. Any workarounds for this?<br />
Some USB drives need to be plugged twice into the server to be recognized.<br />
<br />
===Backups & Restores===<br />
*AIT-1 Backup: buffer unreliable<br />
An AIT-1 is unreliable if used with variable block size. Set the setting<br />
config setprop flexbackup TapeBlocksize 512<br />
AIT-2, DAT and LTO seem to work well with variable block size.<br />
<br />
<br />
*Slow tape backup performance may be improved by changing Flex backup settings<br />
config setprop flexbackup Blocksize 256<br />
config setprop flexbackup BufferMegs 16<br />
<br />
<br />
*In the ADMIN CONSOLE, there is an option to BACKUP TO USB but there are no restore options.<br />
The RESTORE option is only visible on a new install. If you missed this during install, you can<br />
config set PasswordSet no <br />
signal-event post-upgrade; signal-event reboot <br />
<br />
During reboot reconfiguration process you should see the new restore via USB backup option. <br />
-NOW plug in the usb drive (Do not plug in the usb drive until you reach this point).<br />
-pick YES or RESTORE (or whatever is presented to you)<br />
<br />
<br />
===Supervised Services===<br />
*Many services on SME are supervised, to see which are type<br />
ps ax |grep runsv<br />
To control them read the sv manual<br />
man sv<br />
<br />
*it seems that "sv u http-e-smith" gives no errors, even if the service fails to restart, so you need to use "sv s httpd-e-smith" to check if it fails (example: due to a httpd.conf error)<br />
<br />
This is just the way that runsv (part of the runit package) works. The "sv u http-e-smith"<br />
only sends a message to runsv saying that we want the service to be up. <br />
runsv then will keep trying to get the service running.<br />
<br />
<br />
===Server-Manager===<br />
*I can't access the server-manager. What do I do now?<br />
There are many reasons why you wouldn't be to access the server-manager. First try:<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
If you still can't access, there are reports that a certificates mis-match might have occurred after update. In that case:<br />
rm /home/e-smith/ssl.key/*.key<br />
rm /home/e-smith/ssl.pem/*.pem<br />
rm /home/e-smith/ssl.crt/*.crt<br />
signal-event domain-modify; signal-event reboot<br />
<br />
<br />
*I used to access the SERVER-MANAGER with localhost:980 remotely via SSH tunnel and now I can't. What happened?<br />
This feature has been deprecated a long time and finally removed in V7.2<br />
<br />
If you really want to use this then forward 443 to localhost:443 and then use<br />
https://localhost/server-manager/<br />
<br />
<br />
*Using a ssh client, the /server-manager login screen is difficult to read<br />
The text is white, so you need to adjust your ssh client to use a dark background<br />
<br />
<br />
*I've renamed my server with the ADMIN CONSOLE. The old name appears under the SERVER-MANAGER, HOSTNAMES panel. It cannot be deleted as there are no MODIFY/REMOVE links.<br />
<br />
-login to the shell console<br />
-type: db hosts setprop <local.mycompany.local> static no<br />
-go to the HOSTNAMES & ADDRESSES panel and you should be able to modify/remove the name<br />
<br />
===Booting with SMP kernel after upgrade to version 7.2 from CD===<br />
*I've upgraded and now the SMP kernel isn't available. <br />
This is because when upgrading to 7.2 from CD, kernel modules are <br />
missing for SMP '''IF''' the output of "cat/proc/cpuinfo" <br />
does not show multiple processors. The SMP kernel, if not present, can be installed via yum using:<br />
Do:<br />
yum install kernel-smp kmod-ppp-smp kmod-slip-smp kmod-appletalk-smp<br />
signal-event post-upgrade<br />
signal-event reboot<br />
Details: http://bugs.contribs.org/show_bug.cgi?id=3095<br />
<br />
*I'm getting a kernel panic after upgrade from CD. What do I do now?<br />
When upgrading with a CD, the upgrade will rewrite the grub.conf file. As a result, any additional boot arguments (i.e. acpi=off) will be lost during upgrade. Please edit the grub.conf file.<br />
<br />
<br />
===Special Characters===<br />
*I get strange characters & letters when look at my file names.<br />
If you get filenames that look like: "éèÃ.txt" It's most likely because the SME server isn't understanding special characters you may be using. You can change it to understand special characters in filenames by:<br />
db configuration setprop smb UnixCharSet ISO8859-1<br />
expand-template /etc/smb.conf<br />
/etc/init.d/smb restart<br />
<br />
<br />
===Upstream proxy server configuration===<br />
<br />
*How do I configure a mandatory upstream proxy server, there used to be a panel in earlier versions of sme server, but it's missing in sme7.x<br />
<br />
config set SquidParent a.b.c.d<br />
config set SquidParentPort nnn<br />
signal-event post-upgrade<br />
signal-event reboot<br />
<br />
[The SquidParentPort setting is optional if the upstream proxy is on port 3128.]<br />
<br />
From http://forums.contribs.org/index.php?topic=32998.msg140512#msg140512<br />
<br />
<br />
===Memory usage and limits===<br />
<br />
*How much memory can sme server handle<br />
<br />
SME server currently (v7.3) supports 16GB of RAM, with a maximum of 3GB per process. These limits can easily be increased to 64GB total and 4GB per process by installing and running the "hugemem" variant of the kernel<br />
<br />
*Why does my sme server always seem to be using all the memory, there is no spare memory left<br />
<br />
Utilities such as top or htop always report that all available memory is being used.<br />
The Linux OS is designed to utilise all available memory all of the time. If other processes require more memory then it is made available to those processes. Fully utilising all the available memory is a good thing as it optimises the performanece of your server.<br />
<br />
*How can I tell if my sme server needs more memory<br />
<br />
Watch the availabe swap memory usage eg using top, htop or ps -aux. If swap memory usage regularly exceeds 50% of the available swap memory, then you should add more physical RAM to your system.<br />
Other indications that additional RAM is required are "out of memory" messages in log files, and at times the server becomes inactive for a period, often related to spam & virus scanning & high email loads.<br />
<br />
{{:Booting}}<br />
<br />
{{:Log_Files}}<br />
<br />
{{:Email}}<br />
<br />
{{:Firewall}}<br />
<br />
{{:MySQL}}<br />
<br />
==PHP==<br />
<br />
===Why does SME Server still not have PHP 5? ===<br />
To go short SME Server is based on Centos 4.x which in term is based on RedHat Enterprise Linux 4.x. Since the development team is limited in person and time, all work is done in spare time, we do not have the time to implement such big changes and cope with the maintenance of such work.<br />
<br />
===Is PHP 4.x on SME Server still safe to run? ===<br />
Yes, because security fixes and bug fixes are backported to the 4.x releases and they are propagated to the users as updates, for more information have a look at [http://www.redhat.com/security/updates/backporting/ this page on the RedHat website].<br />
<br />
==Known Problems==<br />
<br />
{{Note box|This section is to be used to document problems that cannot or will not <br><br />
be fixed through development of SME7. <br><br />
Please refer to the [[:KnownProblems]] page}}</div>
Pfloor
https://wiki.koozali.org/index.php?title=Moving_SME_to_new_Hardware&diff=11682
Moving SME to new Hardware
2008-11-27T16:50:21Z
<p>Pfloor: </p>
<hr />
<div>{{Languages}}<br />
=== Introduction ===<br />
There are many ways to move a SME 7 Server installation to new hardware. <br />
This document describes a method using the '''[[Affa]]''' contrib.<br><br />
Affa makes it possible to move with a minimal downtime of the production server.<br><br />
In the following it is assumed that <code>prodIP</code> is the IP address of your production server and <code>newIP</code> is the IP address of the new server hardware. Replace both placeholders by your real IP addresses.<br />
<br />
=== Preparation ===<br />
==== Production server ====<br />
Enable remote administration ssh access in the server-manager of <code>prodIP</code>. This involves setting both the 'Secure shell access' for the local network, and the 'Allow administrative command line access over secure shell' setting, which must be set to 'Yes'.<br><br />
Log into the <code>prodIP</code> box and run an update<br><br />
<br />
yum update<br />
<br />
If packages were updated signalling post-upgrade and reboot events is required.<br />
<br />
==== New hardware ====<br />
Install SME Server from the latest CDROM/ISO. Assign an unused IP address (<code>newIP</code>) and disable DHCP.<br><br />
Enable remote ssh access in the server-manager on the newIP box.<br />
<br />
'''''Note:''' From now on all further steps can be done remotely via ssh login.''<br><br />
<br />
Log into the <code>newIP</code> box and run an update<br><br />
<br />
yum update<br />
<br />
Signalling post-upgrade and reboot events is required.<br><br />
<br />
<br />
Install the Affa RPM<br />
/usr/bin/yum install --enablerepo=smecontribs smeserver-affa<br />
<br />
Configure Affa<br><br />
db affa set prodserv job<br />
db affa setprop prodserv remoteHostName prodIP<br />
db affa setprop prodserv RPMCheck yes<br />
<br />
Generate DSA keys and send the public key to the <code>prodIP</code> server<br><br />
affa --send-key prodserv<br />
<br />
The answer from ProdIP server will be<br><br />
Job prodserv: root@ProdIP's password:<br />
enter the root ProdIP password. The answer will be:<br><br />
Public key sent to prodIP<br />
<br />
=== Copying data ===<br />
Run the Affa job on the <code>newIP</code> box<br />
<br />
affa --run prodserv<br />
<br />
Depending on the amount of data and the speed of hardware and network this first job run can take a really long time.<br />
<br />
Now view the file <code>/var/affa/prodserv/rpms-missing.txt</code><br />
<br />
less /var/affa/prodserv/rpms-missing.txt<br />
<br />
You will find a list of RPMs which are installed on <code>prodIP</code> but not on this server (<code>newIP</code>) and also RPMs installed with different versions. Install or update the listed RPMs. To verify, you can run the steps of this chapter again. Finally the rpms-missing.txt should not list any RPMs.<br />
<br />
=== Final data synchronization ===<br />
Ask your users to log off.<br><br />
Log into the <code>prodIP</code> box and stop all services that can modify data.<br />
<br />
SVC='qpsmtpd sqpsmtpd crond imap pop3 imaps pop3s ftp httpd-e-smith atalk smb qmail' <br />
for s in $SVC; do service $s stop; done<br />
<br />
'''''Note:''' Downtime of the production server starts here''<br />
<br />
Log into the <code>newIP</code> box and run the Affa job again<br />
<br />
affa --run prodserv<br />
<br />
This run will complete very quickly as only differences since the the last run needs to be synchronsized.<br />
=== Switch over to the new hardware ===<br />
Log into the <code>prodIP</code> box and power it off<br />
<br />
poweroff<br />
<br />
<br />
Log into the <code>newIP</code> box and rise this server to your production server<br />
<br />
affa --rise --all prodserv<br />
<br />
This action will complete very quickly as only hardlinks are used and no data is physically moved.<br><br />
Now do a reboot<br />
<br />
reboot<br />
'''''Note:''' Downtime of the production server ends here''<br />
<br />
<br />
You now have an identical copy of your old production server running on the new hardware. Your users can now log on.<br />
<br />
=== Cleaning up ===<br />
Remove the Affa archives<br />
<br />
/bin/rm -rf /var/affa<br />
<br />
Remove the Affa packages<br />
<br />
yum remove smeserver-affa perl-Filesys-DiskFree<br />
<br />
'''Note:''' Don't forget to clean up. Otherwise you will waste disk space and see strange quota reports. See this [http://forums.contribs.org/index.php?topic=40737.msg198064#msg198064 forum thread] for details.<br />
<br />
=== Additional information ===<br />
==== Performance ====<br />
With this method you should be able to move a typical 50 Gbyte sized server to new hardware with downtime less than 20 minutes. The final sync and the rise time does not really depend on the total files size, but on the number of files and directories.<br />
==== SME 6 Server ====<br />
Although Affa was designed for SME 7, you can move a SME 6 server to a hardware with SME 7 installed. But there are a few restrictions:<br />
* You cannot yum update the SME 6<br />
* You cannot use the RPM comparision, as SME 6 doesn't have yum installed and all packages would differ anyway. Skip <code>db affa setprop prodserv RPMCheck yes</code><br />
* You must set rsync--inplace to no: <br />
<br />
db affa setprop prodserv rsync--inplace no<br />
<br />
* The command <code>affa --rise prodserv</code> will complain about old-style db paths. Ignore these errors. After reboot login as admin on the '''local''' console and set the new Network Interfaces manually. Reboot again.<br />
* You cannot work remotely.<br />
[[Category: Howto]]<br />
[[Category: Backup]]<br />
----</div>
Pfloor