summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeroen van Meeuwen (Kolab Systems) <vanmeeuwen@kolabsys.com>2012-09-03 12:14:18 (GMT)
committerJeroen van Meeuwen (Kolab Systems) <vanmeeuwen@kolabsys.com>2012-09-03 12:14:18 (GMT)
commit1784a3c46fc3765fa05202e4ce1a8b6bb90eec59 (patch)
treef097ec6e79599a86c0c73ca22443d05c026e27c2
parent7394896c7b493a92d76c354c057a89102536fc0d (diff)
downloadkolab-docs-1784a3c46fc3765fa05202e4ce1a8b6bb90eec59.tar.gz
Update translations
Add section on the recipient policy
-rw-r--r--About_Kolab_Groupware/.tx/config2
-rw-r--r--About_Kolab_Groupware/de-DE/About_Kolab_Groupware.po2
-rw-r--r--About_Kolab_Groupware/de-DE/Article_Info.po2
-rw-r--r--About_Kolab_Groupware/de-DE/Revision_History.po2
-rw-r--r--About_Kolab_Groupware/de-DE/sect-About_Kolab_Groupware.po2
-rw-r--r--About_Kolab_Groupware/de-DE/sect-Feedback.po2
-rw-r--r--About_Kolab_Groupware/de-DE/sect-Kolab_Product_Series.po2
-rw-r--r--About_Kolab_Groupware/de-DE/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--About_Kolab_Groupware/es-ES/About_Kolab_Groupware.po2
-rw-r--r--About_Kolab_Groupware/es-ES/Article_Info.po2
-rw-r--r--About_Kolab_Groupware/es-ES/Revision_History.po2
-rw-r--r--About_Kolab_Groupware/es-ES/sect-About_Kolab_Groupware.po2
-rw-r--r--About_Kolab_Groupware/es-ES/sect-Feedback.po2
-rw-r--r--About_Kolab_Groupware/es-ES/sect-Kolab_Product_Series.po2
-rw-r--r--About_Kolab_Groupware/es-ES/sect-Supported_Platforms_and_System_Requirements.po20
-rw-r--r--About_Kolab_Groupware/ja-JP/About_Kolab_Groupware.po35
-rw-r--r--About_Kolab_Groupware/ja-JP/Article_Info.po18
-rw-r--r--About_Kolab_Groupware/ja-JP/Author_Group.po6
-rw-r--r--About_Kolab_Groupware/ja-JP/Revision_History.po18
-rw-r--r--About_Kolab_Groupware/ja-JP/sect-About_Kolab_Groupware.po48
-rw-r--r--About_Kolab_Groupware/ja-JP/sect-Feedback.po92
-rw-r--r--About_Kolab_Groupware/ja-JP/sect-Kolab_Product_Series.po104
-rw-r--r--About_Kolab_Groupware/ja-JP/sect-Supported_Platforms_and_System_Requirements.po36
-rw-r--r--About_Kolab_Groupware/nl-NL/About_Kolab_Groupware.po2
-rw-r--r--About_Kolab_Groupware/nl-NL/Article_Info.po2
-rw-r--r--About_Kolab_Groupware/nl-NL/Revision_History.po2
-rw-r--r--About_Kolab_Groupware/nl-NL/sect-About_Kolab_Groupware.po2
-rw-r--r--About_Kolab_Groupware/nl-NL/sect-Feedback.po2
-rw-r--r--About_Kolab_Groupware/nl-NL/sect-Kolab_Product_Series.po2
-rw-r--r--About_Kolab_Groupware/nl-NL/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--About_Kolab_Groupware/pot/About_Kolab_Groupware.pot4
-rw-r--r--About_Kolab_Groupware/pot/Article_Info.pot4
-rw-r--r--About_Kolab_Groupware/pot/Author_Group.pot4
-rw-r--r--About_Kolab_Groupware/pot/Revision_History.pot4
-rw-r--r--About_Kolab_Groupware/pot/sect-About_Kolab_Groupware.pot4
-rw-r--r--About_Kolab_Groupware/pot/sect-Feedback.pot4
-rw-r--r--About_Kolab_Groupware/pot/sect-Kolab_Product_Series.pot4
-rw-r--r--About_Kolab_Groupware/pot/sect-Supported_Platforms_and_System_Requirements.pot4
-rw-r--r--Administrator_Guide/.tx/config2
-rw-r--r--Administrator_Guide/de-DE/Combating_Spam.po2
-rw-r--r--Administrator_Guide/de-DE/Configuring_the_Kolab_Server.po2
-rw-r--r--Administrator_Guide/de-DE/Detailed_Kolab_Server_Overview.po2
-rw-r--r--Administrator_Guide/de-DE/Kolab_Web_Administration_Panel.po2
-rw-r--r--Administrator_Guide/de-DE/Preface.po2
-rw-r--r--Administrator_Guide/de-DE/Revision_History.po2
-rw-r--r--Administrator_Guide/de-DE/Tweaking_Tips_for_389_Directory_Server.po2
-rw-r--r--Administrator_Guide/de-DE/Tweaking_Tips_for_Cyrus_IMAP.po2
-rw-r--r--Administrator_Guide/de-DE/Tweaking_Tips_for_Postfix.po69
-rw-r--r--Administrator_Guide/de-DE/Tweaking_Tips_for_Roundcube.po2
-rw-r--r--Administrator_Guide/de-DE/Upgrading_Accounts_from_Kolab_Format_version_2.po2
-rw-r--r--Administrator_Guide/de-DE/Upgrading_from_Kolab_2_on_OpenPKG.po8
-rw-r--r--Administrator_Guide/de-DE/Verifying_the_Installation.po2
-rw-r--r--Administrator_Guide/de-DE/chap-About_Kolab_Groupware.po2
-rw-r--r--Administrator_Guide/de-DE/part-Clients.po2
-rw-r--r--Administrator_Guide/de-DE/part-Kolab_Server.po2
-rw-r--r--Administrator_Guide/de-DE/sect-About_Kolab_Groupware.po2
-rw-r--r--Administrator_Guide/de-DE/sect-Feedback.po2
-rw-r--r--Administrator_Guide/de-DE/sect-Kolab_Product_Series.po2
-rw-r--r--Administrator_Guide/de-DE/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Administrator_Guide/de-DE/step-convert-seen-databases.po2
-rw-r--r--Administrator_Guide/de-DE/step-select-all-mailboxes.po2
-rw-r--r--Administrator_Guide/en-US/Administrator_Guide.xml10
-rw-r--r--Administrator_Guide/en-US/Book_Info.xml40
-rw-r--r--Administrator_Guide/en-US/Combating_Spam.xml1318
-rw-r--r--Administrator_Guide/en-US/Configuring_the_Kolab_Server.xml265
-rwxr-xr-xAdministrator_Guide/en-US/Detailed_Kolab_Server_Overview.xml776
-rw-r--r--Administrator_Guide/en-US/Kolab_Web_Administration_Panel.xml658
-rw-r--r--Administrator_Guide/en-US/Preface.xml8
-rw-r--r--Administrator_Guide/en-US/Revision_History.xml38
-rw-r--r--Administrator_Guide/en-US/Tweaking_Tips_for_389_Directory_Server.xml230
-rw-r--r--Administrator_Guide/en-US/Tweaking_Tips_for_Cyrus_IMAP.xml302
-rw-r--r--Administrator_Guide/en-US/Tweaking_Tips_for_Postfix.xml68
-rw-r--r--Administrator_Guide/en-US/Tweaking_Tips_for_Roundcube.xml348
-rw-r--r--Administrator_Guide/en-US/Upgrading_Accounts_from_Kolab_Format_version_2.xml72
-rw-r--r--Administrator_Guide/en-US/Upgrading_Cyrus_IMAP_from_2.3_to_2.4.xml222
-rw-r--r--Administrator_Guide/en-US/Upgrading_from_Kolab_2_on_OpenPKG.xml500
-rw-r--r--Administrator_Guide/en-US/Verifying_the_Installation.xml608
-rw-r--r--Administrator_Guide/en-US/chap-About_Kolab_Groupware.xml38
-rw-r--r--Administrator_Guide/en-US/part-Clients.xml8
-rwxr-xr-xAdministrator_Guide/en-US/part-Kolab_Server.xml24
-rw-r--r--Administrator_Guide/en-US/sect-Kolab_Recipient_Policy_and_Web_Administration_Panel.xml464
-rw-r--r--Administrator_Guide/es-ES/Combating_Spam.po2
-rw-r--r--Administrator_Guide/es-ES/Configuring_the_Kolab_Server.po2
-rw-r--r--Administrator_Guide/es-ES/Detailed_Kolab_Server_Overview.po2
-rw-r--r--Administrator_Guide/es-ES/Kolab_Web_Administration_Panel.po2
-rw-r--r--Administrator_Guide/es-ES/Preface.po2
-rw-r--r--Administrator_Guide/es-ES/Revision_History.po2
-rw-r--r--Administrator_Guide/es-ES/Tweaking_Tips_for_389_Directory_Server.po2
-rw-r--r--Administrator_Guide/es-ES/Tweaking_Tips_for_Cyrus_IMAP.po2
-rw-r--r--Administrator_Guide/es-ES/Tweaking_Tips_for_Postfix.po69
-rw-r--r--Administrator_Guide/es-ES/Tweaking_Tips_for_Roundcube.po2
-rw-r--r--Administrator_Guide/es-ES/Upgrading_Accounts_from_Kolab_Format_version_2.po2
-rw-r--r--Administrator_Guide/es-ES/Upgrading_from_Kolab_2_on_OpenPKG.po8
-rw-r--r--Administrator_Guide/es-ES/Verifying_the_Installation.po2
-rw-r--r--Administrator_Guide/es-ES/chap-About_Kolab_Groupware.po2
-rw-r--r--Administrator_Guide/es-ES/part-Clients.po2
-rw-r--r--Administrator_Guide/es-ES/part-Kolab_Server.po2
-rw-r--r--Administrator_Guide/es-ES/sect-About_Kolab_Groupware.po2
-rw-r--r--Administrator_Guide/es-ES/sect-Feedback.po2
-rw-r--r--Administrator_Guide/es-ES/sect-Kolab_Product_Series.po2
-rw-r--r--Administrator_Guide/es-ES/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Administrator_Guide/es-ES/step-convert-seen-databases.po2
-rw-r--r--Administrator_Guide/es-ES/step-select-all-mailboxes.po2
-rw-r--r--Administrator_Guide/fr-FR/Tweaking_Tips_for_Postfix.po56
-rw-r--r--Administrator_Guide/fr-FR/Upgrading_from_Kolab_2_on_OpenPKG.po6
-rw-r--r--Administrator_Guide/ja-JP/Administrator_Guide.po6
-rw-r--r--Administrator_Guide/ja-JP/Author_Group.po6
-rw-r--r--Administrator_Guide/ja-JP/Book_Info.po6
-rw-r--r--Administrator_Guide/ja-JP/Combating_Spam.po407
-rw-r--r--Administrator_Guide/ja-JP/Configuring_the_Kolab_Server.po108
-rw-r--r--Administrator_Guide/ja-JP/Detailed_Kolab_Server_Overview.po93
-rw-r--r--Administrator_Guide/ja-JP/Kolab_Web_Administration_Panel.po191
-rw-r--r--Administrator_Guide/ja-JP/Preface.po18
-rw-r--r--Administrator_Guide/ja-JP/Revision_History.po18
-rw-r--r--Administrator_Guide/ja-JP/Tweaking_Tips_for_389_Directory_Server.po82
-rw-r--r--Administrator_Guide/ja-JP/Tweaking_Tips_for_Cyrus_IMAP.po92
-rw-r--r--Administrator_Guide/ja-JP/Tweaking_Tips_for_Postfix.po43
-rw-r--r--Administrator_Guide/ja-JP/Tweaking_Tips_for_Roundcube.po71
-rw-r--r--Administrator_Guide/ja-JP/Upgrading_Accounts_from_Kolab_Format_version_2.po53
-rw-r--r--Administrator_Guide/ja-JP/Upgrading_Cyrus_IMAP_from_2.3_to_2.4.po15
-rw-r--r--Administrator_Guide/ja-JP/Upgrading_from_Kolab_2_on_OpenPKG.po170
-rw-r--r--Administrator_Guide/ja-JP/Verifying_the_Installation.po79
-rw-r--r--Administrator_Guide/ja-JP/chap-About_Kolab_Groupware.po27
-rw-r--r--Administrator_Guide/ja-JP/part-Clients.po18
-rw-r--r--Administrator_Guide/ja-JP/part-Kolab_Server.po18
-rw-r--r--Administrator_Guide/ja-JP/sect-About_Kolab_Groupware.po48
-rw-r--r--Administrator_Guide/ja-JP/sect-Feedback.po92
-rw-r--r--Administrator_Guide/ja-JP/sect-Kolab_Product_Series.po104
-rw-r--r--Administrator_Guide/ja-JP/sect-Supported_Platforms_and_System_Requirements.po36
-rw-r--r--Administrator_Guide/ja-JP/step-convert-seen-databases.po26
-rw-r--r--Administrator_Guide/ja-JP/step-select-all-mailboxes.po55
-rw-r--r--Administrator_Guide/nl-NL/Combating_Spam.po2
-rw-r--r--Administrator_Guide/nl-NL/Configuring_the_Kolab_Server.po2
-rw-r--r--Administrator_Guide/nl-NL/Detailed_Kolab_Server_Overview.po2
-rw-r--r--Administrator_Guide/nl-NL/Kolab_Web_Administration_Panel.po2
-rw-r--r--Administrator_Guide/nl-NL/Preface.po2
-rw-r--r--Administrator_Guide/nl-NL/Revision_History.po2
-rw-r--r--Administrator_Guide/nl-NL/Tweaking_Tips_for_389_Directory_Server.po2
-rw-r--r--Administrator_Guide/nl-NL/Tweaking_Tips_for_Cyrus_IMAP.po2
-rw-r--r--Administrator_Guide/nl-NL/Tweaking_Tips_for_Postfix.po69
-rw-r--r--Administrator_Guide/nl-NL/Tweaking_Tips_for_Roundcube.po2
-rw-r--r--Administrator_Guide/nl-NL/Upgrading_Accounts_from_Kolab_Format_version_2.po2
-rw-r--r--Administrator_Guide/nl-NL/Upgrading_from_Kolab_2_on_OpenPKG.po8
-rw-r--r--Administrator_Guide/nl-NL/Verifying_the_Installation.po2
-rw-r--r--Administrator_Guide/nl-NL/chap-About_Kolab_Groupware.po2
-rw-r--r--Administrator_Guide/nl-NL/part-Clients.po2
-rw-r--r--Administrator_Guide/nl-NL/part-Kolab_Server.po2
-rw-r--r--Administrator_Guide/nl-NL/sect-About_Kolab_Groupware.po2
-rw-r--r--Administrator_Guide/nl-NL/sect-Feedback.po2
-rw-r--r--Administrator_Guide/nl-NL/sect-Kolab_Product_Series.po2
-rw-r--r--Administrator_Guide/nl-NL/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Administrator_Guide/nl-NL/step-convert-seen-databases.po2
-rw-r--r--Administrator_Guide/nl-NL/step-select-all-mailboxes.po2
-rw-r--r--Administrator_Guide/pot/Administrator_Guide.pot4
-rw-r--r--Administrator_Guide/pot/Author_Group.pot4
-rw-r--r--Administrator_Guide/pot/Book_Info.pot4
-rw-r--r--Administrator_Guide/pot/Combating_Spam.pot4
-rw-r--r--Administrator_Guide/pot/Configuring_the_Kolab_Server.pot6
-rw-r--r--Administrator_Guide/pot/Detailed_Kolab_Server_Overview.pot4
-rw-r--r--Administrator_Guide/pot/Kolab_Web_Administration_Panel.pot4
-rw-r--r--Administrator_Guide/pot/Preface.pot4
-rw-r--r--Administrator_Guide/pot/Revision_History.pot4
-rw-r--r--Administrator_Guide/pot/Tweaking_Tips_for_389_Directory_Server.pot4
-rw-r--r--Administrator_Guide/pot/Tweaking_Tips_for_Cyrus_IMAP.pot4
-rw-r--r--Administrator_Guide/pot/Tweaking_Tips_for_Postfix.pot56
-rw-r--r--Administrator_Guide/pot/Tweaking_Tips_for_Roundcube.pot4
-rw-r--r--Administrator_Guide/pot/Upgrading_Accounts_from_Kolab_Format_version_2.pot4
-rw-r--r--Administrator_Guide/pot/Upgrading_Cyrus_IMAP_from_2.3_to_2.4.pot4
-rw-r--r--Administrator_Guide/pot/Upgrading_from_Kolab_2_on_OpenPKG.pot8
-rw-r--r--Administrator_Guide/pot/Verifying_the_Installation.pot4
-rw-r--r--Administrator_Guide/pot/chap-About_Kolab_Groupware.pot4
-rw-r--r--Administrator_Guide/pot/part-Clients.pot4
-rw-r--r--Administrator_Guide/pot/part-Kolab_Server.pot4
-rw-r--r--Administrator_Guide/pot/sect-About_Kolab_Groupware.pot4
-rw-r--r--Administrator_Guide/pot/sect-Feedback.pot4
-rw-r--r--Administrator_Guide/pot/sect-Kolab_Product_Series.pot4
-rw-r--r--Administrator_Guide/pot/sect-Kolab_Recipient_Policy_and_Web_Administration_Panel.pot154
-rw-r--r--Administrator_Guide/pot/sect-Supported_Platforms_and_System_Requirements.pot4
-rw-r--r--Administrator_Guide/pot/step-convert-seen-databases.pot4
-rw-r--r--Administrator_Guide/pot/step-select-all-mailboxes.pot4
-rw-r--r--Architecture_and_Design/.tx/config2
-rw-r--r--Architecture_and_Design/de-DE/Administration_Panel.po47
-rw-r--r--Architecture_and_Design/de-DE/Akonadi_for_Integration_and_Caching.po2
-rw-r--r--Architecture_and_Design/de-DE/Archiving_amp_Discovery.po2
-rw-r--r--Architecture_and_Design/de-DE/Authentication_amp_Authorization.po2
-rw-r--r--Architecture_and_Design/de-DE/Calendaring.po11
-rw-r--r--Architecture_and_Design/de-DE/Configuration_Management.po2
-rw-r--r--Architecture_and_Design/de-DE/Email.po33
-rw-r--r--Architecture_and_Design/de-DE/Enforcing_Entitlements.po2
-rw-r--r--Architecture_and_Design/de-DE/Feature_FAQ.po2
-rw-r--r--Architecture_and_Design/de-DE/Free_Busy.po2
-rw-r--r--Architecture_and_Design/de-DE/Groupware_Overview.po2
-rw-r--r--Architecture_and_Design/de-DE/Integration_amp_Interoperability.po2
-rw-r--r--Architecture_and_Design/de-DE/Kolab_Content_Filters.po2
-rw-r--r--Architecture_and_Design/de-DE/Kolab_Daemon.po2
-rw-r--r--Architecture_and_Design/de-DE/Kolab_Objects.po2
-rw-r--r--Architecture_and_Design/de-DE/Kolab_SMTP_Access_Policy.po2
-rw-r--r--Architecture_and_Design/de-DE/Kolab_Server_Overview.po2
-rw-r--r--Architecture_and_Design/de-DE/Migration.po2
-rw-r--r--Architecture_and_Design/de-DE/Mobile_Device_Synchronization.po15
-rw-r--r--Architecture_and_Design/de-DE/Preface.po2
-rw-r--r--Architecture_and_Design/de-DE/Revision_History.po2
-rw-r--r--Architecture_and_Design/de-DE/Smart_Clients.po2
-rw-r--r--Architecture_and_Design/de-DE/Terminology.po2
-rw-r--r--Architecture_and_Design/de-DE/sect-About_Kolab_Groupware.po2
-rw-r--r--Architecture_and_Design/de-DE/sect-Feedback.po2
-rw-r--r--Architecture_and_Design/de-DE/sect-Kolab_Product_Series.po2
-rw-r--r--Architecture_and_Design/de-DE/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Architecture_and_Design/es-ES/Administration_Panel.po2
-rw-r--r--Architecture_and_Design/es-ES/Akonadi_for_Integration_and_Caching.po2
-rw-r--r--Architecture_and_Design/es-ES/Archiving_amp_Discovery.po2
-rw-r--r--Architecture_and_Design/es-ES/Authentication_amp_Authorization.po2
-rw-r--r--Architecture_and_Design/es-ES/Calendaring.po2
-rw-r--r--Architecture_and_Design/es-ES/Configuration_Management.po2
-rw-r--r--Architecture_and_Design/es-ES/Email.po2
-rw-r--r--Architecture_and_Design/es-ES/Enforcing_Entitlements.po2
-rw-r--r--Architecture_and_Design/es-ES/Feature_FAQ.po2
-rw-r--r--Architecture_and_Design/es-ES/Free_Busy.po2
-rw-r--r--Architecture_and_Design/es-ES/Groupware_Overview.po47
-rw-r--r--Architecture_and_Design/es-ES/Integration_amp_Interoperability.po2
-rw-r--r--Architecture_and_Design/es-ES/Kolab_Content_Filters.po2
-rw-r--r--Architecture_and_Design/es-ES/Kolab_Daemon.po2
-rw-r--r--Architecture_and_Design/es-ES/Kolab_Objects.po2
-rw-r--r--Architecture_and_Design/es-ES/Kolab_SMTP_Access_Policy.po2
-rw-r--r--Architecture_and_Design/es-ES/Kolab_Server_Overview.po2
-rw-r--r--Architecture_and_Design/es-ES/Migration.po2
-rw-r--r--Architecture_and_Design/es-ES/Mobile_Device_Synchronization.po2
-rw-r--r--Architecture_and_Design/es-ES/Preface.po2
-rw-r--r--Architecture_and_Design/es-ES/Revision_History.po2
-rw-r--r--Architecture_and_Design/es-ES/Smart_Clients.po2
-rw-r--r--Architecture_and_Design/es-ES/Terminology.po2
-rw-r--r--Architecture_and_Design/es-ES/sect-About_Kolab_Groupware.po2
-rw-r--r--Architecture_and_Design/es-ES/sect-Feedback.po2
-rw-r--r--Architecture_and_Design/es-ES/sect-Kolab_Product_Series.po2
-rw-r--r--Architecture_and_Design/es-ES/sect-Supported_Platforms_and_System_Requirements.po20
-rw-r--r--Architecture_and_Design/ja-JP/Administration_Panel.po596
-rw-r--r--Architecture_and_Design/ja-JP/Akonadi_for_Integration_and_Caching.po259
-rw-r--r--Architecture_and_Design/ja-JP/Architecture_and_Design.po6
-rw-r--r--Architecture_and_Design/ja-JP/Archiving_amp_Discovery.po18
-rw-r--r--Architecture_and_Design/ja-JP/Authentication_amp_Authorization.po102
-rw-r--r--Architecture_and_Design/ja-JP/Author_Group.po6
-rw-r--r--Architecture_and_Design/ja-JP/Book_Info.po6
-rw-r--r--Architecture_and_Design/ja-JP/Calendaring.po22
-rw-r--r--Architecture_and_Design/ja-JP/Configuration_Management.po266
-rw-r--r--Architecture_and_Design/ja-JP/Email.po157
-rw-r--r--Architecture_and_Design/ja-JP/Enforcing_Entitlements.po132
-rw-r--r--Architecture_and_Design/ja-JP/Feature_FAQ.po332
-rw-r--r--Architecture_and_Design/ja-JP/Free_Busy.po127
-rw-r--r--Architecture_and_Design/ja-JP/Groupware_Overview.po27
-rw-r--r--Architecture_and_Design/ja-JP/Integration_amp_Interoperability.po43
-rw-r--r--Architecture_and_Design/ja-JP/Kolab_Content_Filters.po460
-rw-r--r--Architecture_and_Design/ja-JP/Kolab_Daemon.po140
-rw-r--r--Architecture_and_Design/ja-JP/Kolab_Objects.po183
-rw-r--r--Architecture_and_Design/ja-JP/Kolab_SMTP_Access_Policy.po161
-rw-r--r--Architecture_and_Design/ja-JP/Kolab_Server_Overview.po125
-rw-r--r--Architecture_and_Design/ja-JP/Migration.po18
-rw-r--r--Architecture_and_Design/ja-JP/Mobile_Device_Synchronization.po18
-rw-r--r--Architecture_and_Design/ja-JP/Preface.po18
-rw-r--r--Architecture_and_Design/ja-JP/Revision_History.po18
-rw-r--r--Architecture_and_Design/ja-JP/Smart_Clients.po143
-rw-r--r--Architecture_and_Design/ja-JP/Terminology.po169
-rw-r--r--Architecture_and_Design/ja-JP/sect-About_Kolab_Groupware.po48
-rw-r--r--Architecture_and_Design/ja-JP/sect-Feedback.po92
-rw-r--r--Architecture_and_Design/ja-JP/sect-Kolab_Product_Series.po104
-rw-r--r--Architecture_and_Design/ja-JP/sect-Supported_Platforms_and_System_Requirements.po36
-rw-r--r--Architecture_and_Design/nl-NL/Administration_Panel.po2
-rw-r--r--Architecture_and_Design/nl-NL/Akonadi_for_Integration_and_Caching.po2
-rw-r--r--Architecture_and_Design/nl-NL/Archiving_amp_Discovery.po2
-rw-r--r--Architecture_and_Design/nl-NL/Authentication_amp_Authorization.po2
-rw-r--r--Architecture_and_Design/nl-NL/Calendaring.po2
-rw-r--r--Architecture_and_Design/nl-NL/Configuration_Management.po2
-rw-r--r--Architecture_and_Design/nl-NL/Email.po2
-rw-r--r--Architecture_and_Design/nl-NL/Enforcing_Entitlements.po2
-rw-r--r--Architecture_and_Design/nl-NL/Feature_FAQ.po2
-rw-r--r--Architecture_and_Design/nl-NL/Free_Busy.po2
-rw-r--r--Architecture_and_Design/nl-NL/Groupware_Overview.po2
-rw-r--r--Architecture_and_Design/nl-NL/Integration_amp_Interoperability.po2
-rw-r--r--Architecture_and_Design/nl-NL/Kolab_Content_Filters.po2
-rw-r--r--Architecture_and_Design/nl-NL/Kolab_Daemon.po2
-rw-r--r--Architecture_and_Design/nl-NL/Kolab_Objects.po2
-rw-r--r--Architecture_and_Design/nl-NL/Kolab_SMTP_Access_Policy.po2
-rw-r--r--Architecture_and_Design/nl-NL/Kolab_Server_Overview.po2
-rw-r--r--Architecture_and_Design/nl-NL/Migration.po2
-rw-r--r--Architecture_and_Design/nl-NL/Mobile_Device_Synchronization.po2
-rw-r--r--Architecture_and_Design/nl-NL/Preface.po2
-rw-r--r--Architecture_and_Design/nl-NL/Revision_History.po2
-rw-r--r--Architecture_and_Design/nl-NL/Smart_Clients.po2
-rw-r--r--Architecture_and_Design/nl-NL/Terminology.po2
-rw-r--r--Architecture_and_Design/nl-NL/sect-About_Kolab_Groupware.po2
-rw-r--r--Architecture_and_Design/nl-NL/sect-Feedback.po2
-rw-r--r--Architecture_and_Design/nl-NL/sect-Kolab_Product_Series.po2
-rw-r--r--Architecture_and_Design/nl-NL/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Architecture_and_Design/pot/Administration_Panel.pot4
-rw-r--r--Architecture_and_Design/pot/Akonadi_for_Integration_and_Caching.pot4
-rw-r--r--Architecture_and_Design/pot/Architecture_and_Design.pot4
-rw-r--r--Architecture_and_Design/pot/Archiving_amp_Discovery.pot4
-rw-r--r--Architecture_and_Design/pot/Authentication_amp_Authorization.pot4
-rw-r--r--Architecture_and_Design/pot/Author_Group.pot4
-rw-r--r--Architecture_and_Design/pot/Book_Info.pot4
-rw-r--r--Architecture_and_Design/pot/Calendaring.pot4
-rw-r--r--Architecture_and_Design/pot/Configuration_Management.pot4
-rw-r--r--Architecture_and_Design/pot/Email.pot4
-rw-r--r--Architecture_and_Design/pot/Enforcing_Entitlements.pot4
-rw-r--r--Architecture_and_Design/pot/Feature_FAQ.pot4
-rw-r--r--Architecture_and_Design/pot/Free_Busy.pot4
-rw-r--r--Architecture_and_Design/pot/Groupware_Overview.pot4
-rw-r--r--Architecture_and_Design/pot/Integration_amp_Interoperability.pot4
-rw-r--r--Architecture_and_Design/pot/Kolab_Content_Filters.pot4
-rw-r--r--Architecture_and_Design/pot/Kolab_Daemon.pot4
-rw-r--r--Architecture_and_Design/pot/Kolab_Objects.pot4
-rw-r--r--Architecture_and_Design/pot/Kolab_SMTP_Access_Policy.pot4
-rw-r--r--Architecture_and_Design/pot/Kolab_Server_Overview.pot4
-rw-r--r--Architecture_and_Design/pot/Migration.pot4
-rw-r--r--Architecture_and_Design/pot/Mobile_Device_Synchronization.pot4
-rw-r--r--Architecture_and_Design/pot/Preface.pot4
-rw-r--r--Architecture_and_Design/pot/Revision_History.pot4
-rw-r--r--Architecture_and_Design/pot/Smart_Clients.pot4
-rw-r--r--Architecture_and_Design/pot/Terminology.pot4
-rw-r--r--Architecture_and_Design/pot/sect-About_Kolab_Groupware.pot4
-rw-r--r--Architecture_and_Design/pot/sect-Feedback.pot4
-rw-r--r--Architecture_and_Design/pot/sect-Kolab_Product_Series.pot4
-rw-r--r--Architecture_and_Design/pot/sect-Supported_Platforms_and_System_Requirements.pot4
-rw-r--r--Deployment_Guide/.tx/config2
-rw-r--r--Deployment_Guide/de-DE/Capacity_Planning.po2
-rw-r--r--Deployment_Guide/de-DE/High_Availability.po2
-rw-r--r--Deployment_Guide/de-DE/Infrastructure.po2
-rw-r--r--Deployment_Guide/de-DE/Kolab_Groupware_Components.po2
-rw-r--r--Deployment_Guide/de-DE/Kolab_Preparations.po2
-rw-r--r--Deployment_Guide/de-DE/LDAP_Installation.po2
-rw-r--r--Deployment_Guide/de-DE/LDAP_Integration.po2
-rw-r--r--Deployment_Guide/de-DE/Preface.po2
-rw-r--r--Deployment_Guide/de-DE/Revision_History.po2
-rw-r--r--Deployment_Guide/de-DE/sect-About_Kolab_Groupware.po2
-rw-r--r--Deployment_Guide/de-DE/sect-Feedback.po2
-rw-r--r--Deployment_Guide/de-DE/sect-Kolab_Product_Series.po2
-rw-r--r--Deployment_Guide/de-DE/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Deployment_Guide/es-ES/Capacity_Planning.po2
-rw-r--r--Deployment_Guide/es-ES/High_Availability.po2
-rw-r--r--Deployment_Guide/es-ES/Infrastructure.po2
-rw-r--r--Deployment_Guide/es-ES/Kolab_Groupware_Components.po2
-rw-r--r--Deployment_Guide/es-ES/Kolab_Preparations.po2
-rw-r--r--Deployment_Guide/es-ES/LDAP_Installation.po2
-rw-r--r--Deployment_Guide/es-ES/LDAP_Integration.po2
-rw-r--r--Deployment_Guide/es-ES/Preface.po2
-rw-r--r--Deployment_Guide/es-ES/Revision_History.po2
-rw-r--r--Deployment_Guide/es-ES/sect-About_Kolab_Groupware.po2
-rw-r--r--Deployment_Guide/es-ES/sect-Feedback.po2
-rw-r--r--Deployment_Guide/es-ES/sect-Kolab_Product_Series.po2
-rw-r--r--Deployment_Guide/es-ES/sect-Supported_Platforms_and_System_Requirements.po20
-rw-r--r--Deployment_Guide/ja-JP/Author_Group.po6
-rw-r--r--Deployment_Guide/ja-JP/Book_Info.po6
-rw-r--r--Deployment_Guide/ja-JP/Capacity_Planning.po59
-rw-r--r--Deployment_Guide/ja-JP/Deployment_Guide.po6
-rw-r--r--Deployment_Guide/ja-JP/High_Availability.po45
-rw-r--r--Deployment_Guide/ja-JP/Infrastructure.po41
-rw-r--r--Deployment_Guide/ja-JP/Kolab_Groupware_Components.po139
-rw-r--r--Deployment_Guide/ja-JP/Kolab_Preparations.po18
-rw-r--r--Deployment_Guide/ja-JP/LDAP_Installation.po31
-rw-r--r--Deployment_Guide/ja-JP/LDAP_Integration.po22
-rw-r--r--Deployment_Guide/ja-JP/Preface.po18
-rw-r--r--Deployment_Guide/ja-JP/Revision_History.po18
-rw-r--r--Deployment_Guide/ja-JP/sect-About_Kolab_Groupware.po48
-rw-r--r--Deployment_Guide/ja-JP/sect-Feedback.po92
-rw-r--r--Deployment_Guide/ja-JP/sect-Kolab_Product_Series.po104
-rw-r--r--Deployment_Guide/ja-JP/sect-Supported_Platforms_and_System_Requirements.po36
-rw-r--r--Deployment_Guide/nl-NL/Capacity_Planning.po2
-rw-r--r--Deployment_Guide/nl-NL/High_Availability.po2
-rw-r--r--Deployment_Guide/nl-NL/Infrastructure.po2
-rw-r--r--Deployment_Guide/nl-NL/Kolab_Groupware_Components.po2
-rw-r--r--Deployment_Guide/nl-NL/Kolab_Preparations.po2
-rw-r--r--Deployment_Guide/nl-NL/LDAP_Installation.po2
-rw-r--r--Deployment_Guide/nl-NL/LDAP_Integration.po2
-rw-r--r--Deployment_Guide/nl-NL/Preface.po2
-rw-r--r--Deployment_Guide/nl-NL/Revision_History.po2
-rw-r--r--Deployment_Guide/nl-NL/sect-About_Kolab_Groupware.po2
-rw-r--r--Deployment_Guide/nl-NL/sect-Feedback.po2
-rw-r--r--Deployment_Guide/nl-NL/sect-Kolab_Product_Series.po2
-rw-r--r--Deployment_Guide/nl-NL/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Deployment_Guide/pot/Author_Group.pot4
-rw-r--r--Deployment_Guide/pot/Book_Info.pot4
-rw-r--r--Deployment_Guide/pot/Capacity_Planning.pot4
-rw-r--r--Deployment_Guide/pot/Deployment_Guide.pot4
-rw-r--r--Deployment_Guide/pot/High_Availability.pot4
-rw-r--r--Deployment_Guide/pot/Infrastructure.pot4
-rw-r--r--Deployment_Guide/pot/Kolab_Groupware_Components.pot4
-rw-r--r--Deployment_Guide/pot/Kolab_Preparations.pot4
-rw-r--r--Deployment_Guide/pot/LDAP_Installation.pot4
-rw-r--r--Deployment_Guide/pot/LDAP_Integration.pot4
-rw-r--r--Deployment_Guide/pot/Preface.pot4
-rw-r--r--Deployment_Guide/pot/Revision_History.pot4
-rw-r--r--Deployment_Guide/pot/sect-About_Kolab_Groupware.pot4
-rw-r--r--Deployment_Guide/pot/sect-Feedback.pot4
-rw-r--r--Deployment_Guide/pot/sect-Kolab_Product_Series.pot4
-rw-r--r--Deployment_Guide/pot/sect-Supported_Platforms_and_System_Requirements.pot4
-rw-r--r--Development_Manual/.tx/config2
-rw-r--r--Development_Manual/de-DE/Chapter.po2
-rw-r--r--Development_Manual/de-DE/Development_Processes.po2
-rw-r--r--Development_Manual/de-DE/Documentation.po2
-rw-r--r--Development_Manual/de-DE/General_Kolab_Server_Components_Packaging_Notes.po2
-rw-r--r--Development_Manual/de-DE/Localization_and_Internationalization.po15
-rw-r--r--Development_Manual/de-DE/Packaging_with_APT.po2
-rw-r--r--Development_Manual/de-DE/Packaging_with_RPM.po2
-rw-r--r--Development_Manual/de-DE/Part-General_Kolab_Packaging_Notes.po2
-rw-r--r--Development_Manual/de-DE/Preface.po2
-rw-r--r--Development_Manual/de-DE/Revision_History.po2
-rw-r--r--Development_Manual/de-DE/TODO.po2
-rw-r--r--Development_Manual/de-DE/sect-About_Kolab_Groupware.po2
-rw-r--r--Development_Manual/de-DE/sect-Feedback.po2
-rw-r--r--Development_Manual/de-DE/sect-Kolab_Product_Series.po2
-rw-r--r--Development_Manual/de-DE/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Development_Manual/es-ES/Chapter.po2
-rw-r--r--Development_Manual/es-ES/Development_Processes.po2
-rw-r--r--Development_Manual/es-ES/Documentation.po2
-rw-r--r--Development_Manual/es-ES/General_Kolab_Server_Components_Packaging_Notes.po2
-rw-r--r--Development_Manual/es-ES/Localization_and_Internationalization.po2
-rw-r--r--Development_Manual/es-ES/Packaging_with_APT.po2
-rw-r--r--Development_Manual/es-ES/Packaging_with_RPM.po2
-rw-r--r--Development_Manual/es-ES/Part-General_Kolab_Packaging_Notes.po2
-rw-r--r--Development_Manual/es-ES/Preface.po2
-rw-r--r--Development_Manual/es-ES/Revision_History.po2
-rw-r--r--Development_Manual/es-ES/TODO.po2
-rw-r--r--Development_Manual/es-ES/sect-About_Kolab_Groupware.po2
-rw-r--r--Development_Manual/es-ES/sect-Feedback.po2
-rw-r--r--Development_Manual/es-ES/sect-Kolab_Product_Series.po2
-rw-r--r--Development_Manual/es-ES/sect-Supported_Platforms_and_System_Requirements.po20
-rw-r--r--Development_Manual/ja-JP/Author_Group.po6
-rw-r--r--Development_Manual/ja-JP/Book_Info.po6
-rw-r--r--Development_Manual/ja-JP/Chapter.po18
-rw-r--r--Development_Manual/ja-JP/Development_Manual.po6
-rw-r--r--Development_Manual/ja-JP/Development_Processes.po26
-rw-r--r--Development_Manual/ja-JP/Documentation.po18
-rw-r--r--Development_Manual/ja-JP/General_Kolab_Server_Components_Packaging_Notes.po18
-rw-r--r--Development_Manual/ja-JP/Localization_and_Internationalization.po18
-rw-r--r--Development_Manual/ja-JP/Packaging_with_APT.po80
-rw-r--r--Development_Manual/ja-JP/Packaging_with_RPM.po24
-rw-r--r--Development_Manual/ja-JP/Part-General_Kolab_Packaging_Notes.po18
-rw-r--r--Development_Manual/ja-JP/Preface.po18
-rw-r--r--Development_Manual/ja-JP/Revision_History.po18
-rw-r--r--Development_Manual/ja-JP/TODO.po39
-rw-r--r--Development_Manual/ja-JP/sect-About_Kolab_Groupware.po48
-rw-r--r--Development_Manual/ja-JP/sect-Feedback.po92
-rw-r--r--Development_Manual/ja-JP/sect-Kolab_Product_Series.po104
-rw-r--r--Development_Manual/ja-JP/sect-Supported_Platforms_and_System_Requirements.po36
-rw-r--r--Development_Manual/nl-NL/Chapter.po2
-rw-r--r--Development_Manual/nl-NL/Development_Processes.po2
-rw-r--r--Development_Manual/nl-NL/Documentation.po2
-rw-r--r--Development_Manual/nl-NL/General_Kolab_Server_Components_Packaging_Notes.po2
-rw-r--r--Development_Manual/nl-NL/Localization_and_Internationalization.po2
-rw-r--r--Development_Manual/nl-NL/Packaging_with_APT.po2
-rw-r--r--Development_Manual/nl-NL/Packaging_with_RPM.po2
-rw-r--r--Development_Manual/nl-NL/Part-General_Kolab_Packaging_Notes.po2
-rw-r--r--Development_Manual/nl-NL/Preface.po2
-rw-r--r--Development_Manual/nl-NL/Revision_History.po2
-rw-r--r--Development_Manual/nl-NL/TODO.po2
-rw-r--r--Development_Manual/nl-NL/sect-About_Kolab_Groupware.po2
-rw-r--r--Development_Manual/nl-NL/sect-Feedback.po2
-rw-r--r--Development_Manual/nl-NL/sect-Kolab_Product_Series.po2
-rw-r--r--Development_Manual/nl-NL/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Development_Manual/pot/Author_Group.pot4
-rw-r--r--Development_Manual/pot/Book_Info.pot4
-rw-r--r--Development_Manual/pot/Chapter.pot4
-rw-r--r--Development_Manual/pot/Development_Manual.pot4
-rw-r--r--Development_Manual/pot/Development_Processes.pot4
-rw-r--r--Development_Manual/pot/Documentation.pot4
-rw-r--r--Development_Manual/pot/General_Kolab_Server_Components_Packaging_Notes.pot4
-rw-r--r--Development_Manual/pot/Localization_and_Internationalization.pot4
-rw-r--r--Development_Manual/pot/Packaging_with_APT.pot4
-rw-r--r--Development_Manual/pot/Packaging_with_RPM.pot4
-rw-r--r--Development_Manual/pot/Part-General_Kolab_Packaging_Notes.pot4
-rw-r--r--Development_Manual/pot/Preface.pot4
-rw-r--r--Development_Manual/pot/Revision_History.pot4
-rw-r--r--Development_Manual/pot/TODO.pot4
-rw-r--r--Development_Manual/pot/sect-About_Kolab_Groupware.pot4
-rw-r--r--Development_Manual/pot/sect-Feedback.pot4
-rw-r--r--Development_Manual/pot/sect-Kolab_Product_Series.pot4
-rw-r--r--Development_Manual/pot/sect-Supported_Platforms_and_System_Requirements.pot4
-rw-r--r--Installation_Guide/.tx/config2
-rw-r--r--Installation_Guide/de-DE/Cyrus_IMAP.po2
-rw-r--r--Installation_Guide/de-DE/Kolab_Server_Appendix.po2
-rw-r--r--Installation_Guide/de-DE/Kolab_Server_Configuration.po2
-rw-r--r--Installation_Guide/de-DE/Kolab_Server_First_Login.po2
-rw-r--r--Installation_Guide/de-DE/Kolab_Server_Installation.po2
-rw-r--r--Installation_Guide/de-DE/Kolab_Server_Overview.po2
-rw-r--r--Installation_Guide/de-DE/Kolab_Server_on_Enterprise_Linux.po2
-rw-r--r--Installation_Guide/de-DE/Kolab_Systems_Software_Repositories.po2
-rw-r--r--Installation_Guide/de-DE/Kontact.po23
-rw-r--r--Installation_Guide/de-DE/Outlook.po2
-rw-r--r--Installation_Guide/de-DE/Preface.po2
-rw-r--r--Installation_Guide/de-DE/Preparing_the_System.po2
-rw-r--r--Installation_Guide/de-DE/Revision_History.po2
-rw-r--r--Installation_Guide/de-DE/Server_Client_Appendix.po2
-rw-r--r--Installation_Guide/de-DE/Server_Client_Horde.po2
-rw-r--r--Installation_Guide/de-DE/Server_Client_Roundcube.po2
-rw-r--r--Installation_Guide/de-DE/Thunderbird.po11
-rw-r--r--Installation_Guide/de-DE/part-Kolab_Clients.po2
-rw-r--r--Installation_Guide/de-DE/part-Kolab_Server.po2
-rw-r--r--Installation_Guide/de-DE/part-Kolab_Server_Clients.po2
-rw-r--r--Installation_Guide/de-DE/sect-About_Kolab_Groupware.po2
-rw-r--r--Installation_Guide/de-DE/sect-Feedback.po2
-rw-r--r--Installation_Guide/de-DE/sect-Kolab_Product_Series.po2
-rw-r--r--Installation_Guide/de-DE/sect-Repository_Configuration-Installation_with_APT_Packages.po2
-rw-r--r--Installation_Guide/de-DE/sect-Repository_Configuration-Installation_with_RPM_Packages.po2
-rw-r--r--Installation_Guide/de-DE/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Installation_Guide/en-US/sect-Repository_Configuration-Installation_with_APT_Packages.xml4
-rw-r--r--Installation_Guide/es-ES/Cyrus_IMAP.po2
-rw-r--r--Installation_Guide/es-ES/Kolab_Server_Appendix.po2
-rw-r--r--Installation_Guide/es-ES/Kolab_Server_Configuration.po2
-rw-r--r--Installation_Guide/es-ES/Kolab_Server_First_Login.po2
-rw-r--r--Installation_Guide/es-ES/Kolab_Server_Installation.po2
-rw-r--r--Installation_Guide/es-ES/Kolab_Server_Overview.po2
-rw-r--r--Installation_Guide/es-ES/Kolab_Server_on_Enterprise_Linux.po51
-rw-r--r--Installation_Guide/es-ES/Kolab_Systems_Software_Repositories.po2
-rw-r--r--Installation_Guide/es-ES/Kontact.po2
-rw-r--r--Installation_Guide/es-ES/Outlook.po2
-rw-r--r--Installation_Guide/es-ES/Preface.po2
-rw-r--r--Installation_Guide/es-ES/Preparing_the_System.po2
-rw-r--r--Installation_Guide/es-ES/Revision_History.po2
-rw-r--r--Installation_Guide/es-ES/Server_Client_Appendix.po9
-rw-r--r--Installation_Guide/es-ES/Server_Client_Horde.po2
-rw-r--r--Installation_Guide/es-ES/Server_Client_Roundcube.po2
-rw-r--r--Installation_Guide/es-ES/Thunderbird.po2
-rw-r--r--Installation_Guide/es-ES/part-Kolab_Clients.po2
-rw-r--r--Installation_Guide/es-ES/part-Kolab_Server.po9
-rw-r--r--Installation_Guide/es-ES/part-Kolab_Server_Clients.po2
-rw-r--r--Installation_Guide/es-ES/sect-About_Kolab_Groupware.po2
-rw-r--r--Installation_Guide/es-ES/sect-Feedback.po2
-rw-r--r--Installation_Guide/es-ES/sect-Kolab_Product_Series.po2
-rw-r--r--Installation_Guide/es-ES/sect-Repository_Configuration-Installation_with_APT_Packages.po2
-rw-r--r--Installation_Guide/es-ES/sect-Repository_Configuration-Installation_with_RPM_Packages.po2
-rw-r--r--Installation_Guide/es-ES/sect-Supported_Platforms_and_System_Requirements.po20
-rw-r--r--Installation_Guide/ja-JP/Author_Group.po6
-rw-r--r--Installation_Guide/ja-JP/Book_Info.po6
-rw-r--r--Installation_Guide/ja-JP/Community_Installation_Guide.po6
-rw-r--r--Installation_Guide/ja-JP/Cyrus_IMAP.po141
-rw-r--r--Installation_Guide/ja-JP/Enterprise_Installation_Guide.po6
-rw-r--r--Installation_Guide/ja-JP/Kolab_Server_Appendix.po37
-rw-r--r--Installation_Guide/ja-JP/Kolab_Server_Configuration.po271
-rw-r--r--Installation_Guide/ja-JP/Kolab_Server_First_Login.po159
-rw-r--r--Installation_Guide/ja-JP/Kolab_Server_Installation.po124
-rw-r--r--Installation_Guide/ja-JP/Kolab_Server_Overview.po84
-rw-r--r--Installation_Guide/ja-JP/Kolab_Server_on_Enterprise_Linux.po80
-rw-r--r--Installation_Guide/ja-JP/Kolab_Systems_Software_Repositories.po63
-rw-r--r--Installation_Guide/ja-JP/Kontact.po39
-rw-r--r--Installation_Guide/ja-JP/Outlook.po18
-rw-r--r--Installation_Guide/ja-JP/Preface.po18
-rw-r--r--Installation_Guide/ja-JP/Preparing_the_System.po147
-rw-r--r--Installation_Guide/ja-JP/Revision_History.po18
-rw-r--r--Installation_Guide/ja-JP/Server_Client_Appendix.po67
-rw-r--r--Installation_Guide/ja-JP/Server_Client_Horde.po38
-rw-r--r--Installation_Guide/ja-JP/Server_Client_Roundcube.po87
-rw-r--r--Installation_Guide/ja-JP/Thunderbird.po18
-rw-r--r--Installation_Guide/ja-JP/part-Kolab_Clients.po18
-rw-r--r--Installation_Guide/ja-JP/part-Kolab_Server.po18
-rw-r--r--Installation_Guide/ja-JP/part-Kolab_Server_Clients.po18
-rw-r--r--Installation_Guide/ja-JP/sect-About_Kolab_Groupware.po48
-rw-r--r--Installation_Guide/ja-JP/sect-Feedback.po92
-rw-r--r--Installation_Guide/ja-JP/sect-Kolab_Product_Series.po104
-rw-r--r--Installation_Guide/ja-JP/sect-Repository_Configuration-Installation_with_APT_Packages.po22
-rw-r--r--Installation_Guide/ja-JP/sect-Repository_Configuration-Installation_with_RPM_Packages.po245
-rw-r--r--Installation_Guide/ja-JP/sect-Supported_Platforms_and_System_Requirements.po36
-rw-r--r--Installation_Guide/nl-NL/Cyrus_IMAP.po2
-rw-r--r--Installation_Guide/nl-NL/Kolab_Server_Appendix.po2
-rw-r--r--Installation_Guide/nl-NL/Kolab_Server_Configuration.po2
-rw-r--r--Installation_Guide/nl-NL/Kolab_Server_First_Login.po2
-rw-r--r--Installation_Guide/nl-NL/Kolab_Server_Installation.po2
-rw-r--r--Installation_Guide/nl-NL/Kolab_Server_Overview.po2
-rw-r--r--Installation_Guide/nl-NL/Kolab_Server_on_Enterprise_Linux.po2
-rw-r--r--Installation_Guide/nl-NL/Kolab_Systems_Software_Repositories.po2
-rw-r--r--Installation_Guide/nl-NL/Kontact.po2
-rw-r--r--Installation_Guide/nl-NL/Outlook.po2
-rw-r--r--Installation_Guide/nl-NL/Preface.po2
-rw-r--r--Installation_Guide/nl-NL/Preparing_the_System.po2
-rw-r--r--Installation_Guide/nl-NL/Revision_History.po2
-rw-r--r--Installation_Guide/nl-NL/Server_Client_Appendix.po2
-rw-r--r--Installation_Guide/nl-NL/Server_Client_Horde.po2
-rw-r--r--Installation_Guide/nl-NL/Server_Client_Roundcube.po2
-rw-r--r--Installation_Guide/nl-NL/Thunderbird.po2
-rw-r--r--Installation_Guide/nl-NL/part-Kolab_Clients.po2
-rw-r--r--Installation_Guide/nl-NL/part-Kolab_Server.po2
-rw-r--r--Installation_Guide/nl-NL/part-Kolab_Server_Clients.po2
-rw-r--r--Installation_Guide/nl-NL/sect-About_Kolab_Groupware.po2
-rw-r--r--Installation_Guide/nl-NL/sect-Feedback.po2
-rw-r--r--Installation_Guide/nl-NL/sect-Kolab_Product_Series.po2
-rw-r--r--Installation_Guide/nl-NL/sect-Repository_Configuration-Installation_with_APT_Packages.po2
-rw-r--r--Installation_Guide/nl-NL/sect-Repository_Configuration-Installation_with_RPM_Packages.po2
-rw-r--r--Installation_Guide/nl-NL/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Installation_Guide/pot/Author_Group.pot4
-rw-r--r--Installation_Guide/pot/Book_Info.pot4
-rw-r--r--Installation_Guide/pot/Community_Installation_Guide.pot4
-rw-r--r--Installation_Guide/pot/Cyrus_IMAP.pot4
-rw-r--r--Installation_Guide/pot/Enterprise_Installation_Guide.pot4
-rw-r--r--Installation_Guide/pot/Kolab_Server_Appendix.pot4
-rw-r--r--Installation_Guide/pot/Kolab_Server_Configuration.pot4
-rw-r--r--Installation_Guide/pot/Kolab_Server_First_Login.pot4
-rw-r--r--Installation_Guide/pot/Kolab_Server_Installation.pot4
-rw-r--r--Installation_Guide/pot/Kolab_Server_Overview.pot4
-rw-r--r--Installation_Guide/pot/Kolab_Server_on_Enterprise_Linux.pot4
-rw-r--r--Installation_Guide/pot/Kolab_Systems_Software_Repositories.pot4
-rw-r--r--Installation_Guide/pot/Kontact.pot4
-rw-r--r--Installation_Guide/pot/Outlook.pot4
-rw-r--r--Installation_Guide/pot/Preface.pot4
-rw-r--r--Installation_Guide/pot/Preparing_the_System.pot4
-rw-r--r--Installation_Guide/pot/Revision_History.pot4
-rw-r--r--Installation_Guide/pot/Server_Client_Appendix.pot4
-rw-r--r--Installation_Guide/pot/Server_Client_Horde.pot4
-rw-r--r--Installation_Guide/pot/Server_Client_Roundcube.pot4
-rw-r--r--Installation_Guide/pot/Thunderbird.pot4
-rw-r--r--Installation_Guide/pot/part-Kolab_Clients.pot4
-rw-r--r--Installation_Guide/pot/part-Kolab_Server.pot4
-rw-r--r--Installation_Guide/pot/part-Kolab_Server_Clients.pot4
-rw-r--r--Installation_Guide/pot/sect-About_Kolab_Groupware.pot4
-rw-r--r--Installation_Guide/pot/sect-Feedback.pot4
-rw-r--r--Installation_Guide/pot/sect-Kolab_Product_Series.pot4
-rw-r--r--Installation_Guide/pot/sect-Repository_Configuration-Installation_with_APT_Packages.pot4
-rw-r--r--Installation_Guide/pot/sect-Repository_Configuration-Installation_with_RPM_Packages.pot4
-rw-r--r--Installation_Guide/pot/sect-Supported_Platforms_and_System_Requirements.pot4
-rw-r--r--Makefile.common14
-rw-r--r--Release_Notes/.tx/config2
-rw-r--r--Release_Notes/de-DE/Article_Info.po2
-rw-r--r--Release_Notes/de-DE/Version_Matrix_Debian_Lenny.po2
-rw-r--r--Release_Notes/de-DE/Version_Matrix_Debian_Squeeze.po2
-rw-r--r--Release_Notes/de-DE/Version_Matrix_Enterprise_Linux_5.po2
-rw-r--r--Release_Notes/de-DE/Version_Matrix_Enterprise_Linux_6.po2
-rw-r--r--Release_Notes/de-DE/sect-About_Kolab_Groupware.po2
-rw-r--r--Release_Notes/de-DE/sect-Feedback.po2
-rw-r--r--Release_Notes/de-DE/sect-Kolab_Product_Series.po2
-rw-r--r--Release_Notes/de-DE/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Release_Notes/es-ES/Article_Info.po2
-rw-r--r--Release_Notes/es-ES/Version_Matrix_Debian_Lenny.po2
-rw-r--r--Release_Notes/es-ES/Version_Matrix_Debian_Squeeze.po2
-rw-r--r--Release_Notes/es-ES/Version_Matrix_Enterprise_Linux_5.po2
-rw-r--r--Release_Notes/es-ES/Version_Matrix_Enterprise_Linux_6.po2
-rw-r--r--Release_Notes/es-ES/sect-About_Kolab_Groupware.po2
-rw-r--r--Release_Notes/es-ES/sect-Feedback.po2
-rw-r--r--Release_Notes/es-ES/sect-Kolab_Product_Series.po2
-rw-r--r--Release_Notes/es-ES/sect-Supported_Platforms_and_System_Requirements.po20
-rw-r--r--Release_Notes/ja-JP/Article_Info.po24
-rw-r--r--Release_Notes/ja-JP/Author_Group.po6
-rw-r--r--Release_Notes/ja-JP/Release_Notes.po25
-rw-r--r--Release_Notes/ja-JP/Version_Matrix_Debian_Lenny.po101
-rw-r--r--Release_Notes/ja-JP/Version_Matrix_Debian_Squeeze.po103
-rw-r--r--Release_Notes/ja-JP/Version_Matrix_Enterprise_Linux_5.po107
-rw-r--r--Release_Notes/ja-JP/Version_Matrix_Enterprise_Linux_6.po107
-rw-r--r--Release_Notes/ja-JP/sect-About_Kolab_Groupware.po48
-rw-r--r--Release_Notes/ja-JP/sect-Feedback.po92
-rw-r--r--Release_Notes/ja-JP/sect-Kolab_Product_Series.po104
-rw-r--r--Release_Notes/ja-JP/sect-Supported_Platforms_and_System_Requirements.po36
-rw-r--r--Release_Notes/nl-NL/Article_Info.po2
-rw-r--r--Release_Notes/nl-NL/Version_Matrix_Debian_Lenny.po2
-rw-r--r--Release_Notes/nl-NL/Version_Matrix_Debian_Squeeze.po2
-rw-r--r--Release_Notes/nl-NL/Version_Matrix_Enterprise_Linux_5.po2
-rw-r--r--Release_Notes/nl-NL/Version_Matrix_Enterprise_Linux_6.po2
-rw-r--r--Release_Notes/nl-NL/sect-About_Kolab_Groupware.po2
-rw-r--r--Release_Notes/nl-NL/sect-Feedback.po2
-rw-r--r--Release_Notes/nl-NL/sect-Kolab_Product_Series.po2
-rw-r--r--Release_Notes/nl-NL/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Release_Notes/pot/Article_Info.pot4
-rw-r--r--Release_Notes/pot/Author_Group.pot4
-rw-r--r--Release_Notes/pot/Release_Notes.pot4
-rw-r--r--Release_Notes/pot/Version_Matrix_Debian_Lenny.pot4
-rw-r--r--Release_Notes/pot/Version_Matrix_Debian_Squeeze.pot4
-rw-r--r--Release_Notes/pot/Version_Matrix_Enterprise_Linux_5.pot4
-rw-r--r--Release_Notes/pot/Version_Matrix_Enterprise_Linux_6.pot4
-rw-r--r--Release_Notes/pot/sect-About_Kolab_Groupware.pot4
-rw-r--r--Release_Notes/pot/sect-Feedback.pot4
-rw-r--r--Release_Notes/pot/sect-Kolab_Product_Series.pot4
-rw-r--r--Release_Notes/pot/sect-Supported_Platforms_and_System_Requirements.pot4
-rw-r--r--Testing_Reference/.tx/config2
-rw-r--r--Testing_Reference/de-DE/Introduction.po2
-rw-r--r--Testing_Reference/de-DE/Preface.po2
-rw-r--r--Testing_Reference/de-DE/Revision_History.po2
-rw-r--r--Testing_Reference/de-DE/Test_Suite_000-Overview.po2
-rw-r--r--Testing_Reference/de-DE/Test_Suite_001-Overview.po2
-rw-r--r--Testing_Reference/de-DE/Test_Suite_002-Overview.po2
-rw-r--r--Testing_Reference/de-DE/part-Test_Suite_000.po2
-rw-r--r--Testing_Reference/de-DE/part-Test_Suite_001.po2
-rw-r--r--Testing_Reference/de-DE/part-Test_Suite_002.po2
-rw-r--r--Testing_Reference/de-DE/sect-About_Kolab_Groupware.po2
-rw-r--r--Testing_Reference/de-DE/sect-Feedback.po2
-rw-r--r--Testing_Reference/de-DE/sect-Kolab_Product_Series.po2
-rw-r--r--Testing_Reference/de-DE/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Testing_Reference/es-ES/Introduction.po2
-rw-r--r--Testing_Reference/es-ES/Preface.po2
-rw-r--r--Testing_Reference/es-ES/Revision_History.po2
-rw-r--r--Testing_Reference/es-ES/Test_Suite_000-Overview.po2
-rw-r--r--Testing_Reference/es-ES/Test_Suite_001-Overview.po2
-rw-r--r--Testing_Reference/es-ES/Test_Suite_002-Overview.po2
-rw-r--r--Testing_Reference/es-ES/part-Test_Suite_000.po2
-rw-r--r--Testing_Reference/es-ES/part-Test_Suite_001.po2
-rw-r--r--Testing_Reference/es-ES/part-Test_Suite_002.po2
-rw-r--r--Testing_Reference/es-ES/sect-About_Kolab_Groupware.po2
-rw-r--r--Testing_Reference/es-ES/sect-Feedback.po2
-rw-r--r--Testing_Reference/es-ES/sect-Kolab_Product_Series.po2
-rw-r--r--Testing_Reference/es-ES/sect-Supported_Platforms_and_System_Requirements.po20
-rw-r--r--Testing_Reference/ja-JP/Author_Group.po6
-rw-r--r--Testing_Reference/ja-JP/Book_Info.po6
-rw-r--r--Testing_Reference/ja-JP/Introduction.po107
-rw-r--r--Testing_Reference/ja-JP/Preface.po18
-rw-r--r--Testing_Reference/ja-JP/Revision_History.po18
-rw-r--r--Testing_Reference/ja-JP/Test_Suite_000-Overview.po59
-rw-r--r--Testing_Reference/ja-JP/Test_Suite_001-Overview.po24
-rw-r--r--Testing_Reference/ja-JP/Test_Suite_002-Overview.po22
-rw-r--r--Testing_Reference/ja-JP/Testing_Reference.po6
-rw-r--r--Testing_Reference/ja-JP/part-Test_Suite_000.po18
-rw-r--r--Testing_Reference/ja-JP/part-Test_Suite_001.po18
-rw-r--r--Testing_Reference/ja-JP/part-Test_Suite_002.po18
-rw-r--r--Testing_Reference/ja-JP/sect-About_Kolab_Groupware.po48
-rw-r--r--Testing_Reference/ja-JP/sect-Feedback.po92
-rw-r--r--Testing_Reference/ja-JP/sect-Kolab_Product_Series.po104
-rw-r--r--Testing_Reference/ja-JP/sect-Supported_Platforms_and_System_Requirements.po36
-rw-r--r--Testing_Reference/nl-NL/Introduction.po2
-rw-r--r--Testing_Reference/nl-NL/Preface.po2
-rw-r--r--Testing_Reference/nl-NL/Revision_History.po2
-rw-r--r--Testing_Reference/nl-NL/Test_Suite_000-Overview.po2
-rw-r--r--Testing_Reference/nl-NL/Test_Suite_001-Overview.po2
-rw-r--r--Testing_Reference/nl-NL/Test_Suite_002-Overview.po2
-rw-r--r--Testing_Reference/nl-NL/part-Test_Suite_000.po2
-rw-r--r--Testing_Reference/nl-NL/part-Test_Suite_001.po2
-rw-r--r--Testing_Reference/nl-NL/part-Test_Suite_002.po2
-rw-r--r--Testing_Reference/nl-NL/sect-About_Kolab_Groupware.po2
-rw-r--r--Testing_Reference/nl-NL/sect-Feedback.po2
-rw-r--r--Testing_Reference/nl-NL/sect-Kolab_Product_Series.po2
-rw-r--r--Testing_Reference/nl-NL/sect-Supported_Platforms_and_System_Requirements.po4
-rw-r--r--Testing_Reference/pot/Author_Group.pot4
-rw-r--r--Testing_Reference/pot/Book_Info.pot4
-rw-r--r--Testing_Reference/pot/Introduction.pot4
-rw-r--r--Testing_Reference/pot/Preface.pot4
-rw-r--r--Testing_Reference/pot/Revision_History.pot4
-rw-r--r--Testing_Reference/pot/Test_Suite_000-Overview.pot4
-rw-r--r--Testing_Reference/pot/Test_Suite_001-Overview.pot4
-rw-r--r--Testing_Reference/pot/Test_Suite_002-Overview.pot4
-rw-r--r--Testing_Reference/pot/Testing_Reference.pot4
-rw-r--r--Testing_Reference/pot/part-Test_Suite_000.pot4
-rw-r--r--Testing_Reference/pot/part-Test_Suite_001.pot4
-rw-r--r--Testing_Reference/pot/part-Test_Suite_002.pot4
-rw-r--r--Testing_Reference/pot/sect-About_Kolab_Groupware.pot4
-rw-r--r--Testing_Reference/pot/sect-Feedback.pot4
-rw-r--r--Testing_Reference/pot/sect-Kolab_Product_Series.pot4
-rw-r--r--Testing_Reference/pot/sect-Supported_Platforms_and_System_Requirements.pot4
739 files changed, 12591 insertions, 6494 deletions
diff --git a/About_Kolab_Groupware/.tx/config b/About_Kolab_Groupware/.tx/config
index c9af3ca..af75547 100644
--- a/About_Kolab_Groupware/.tx/config
+++ b/About_Kolab_Groupware/.tx/config
@@ -1,6 +1,6 @@
[main]
host = https://www.transifex.net
-lang_map = de: de-DE, es: es-ES, fr: fr-FR, nl: nl-NL
+lang_map = de: de-DE, es: es-ES, fr: fr-FR, ja: ja-JP, nl: nl-NL
type = PO
[kolab.About_Kolab_Groupware-Article_Info]
diff --git a/About_Kolab_Groupware/de-DE/About_Kolab_Groupware.po b/About_Kolab_Groupware/de-DE/About_Kolab_Groupware.po
index ff3911d..fd98f9d 100644
--- a/About_Kolab_Groupware/de-DE/About_Kolab_Groupware.po
+++ b/About_Kolab_Groupware/de-DE/About_Kolab_Groupware.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/About_Kolab_Groupware/de-DE/Article_Info.po b/About_Kolab_Groupware/de-DE/Article_Info.po
index 627be62..daa4d8c 100644
--- a/About_Kolab_Groupware/de-DE/Article_Info.po
+++ b/About_Kolab_Groupware/de-DE/Article_Info.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/About_Kolab_Groupware/de-DE/Revision_History.po b/About_Kolab_Groupware/de-DE/Revision_History.po
index 30ad49a..b2720e6 100644
--- a/About_Kolab_Groupware/de-DE/Revision_History.po
+++ b/About_Kolab_Groupware/de-DE/Revision_History.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/About_Kolab_Groupware/de-DE/sect-About_Kolab_Groupware.po b/About_Kolab_Groupware/de-DE/sect-About_Kolab_Groupware.po
index dc9f904..e93453b 100644
--- a/About_Kolab_Groupware/de-DE/sect-About_Kolab_Groupware.po
+++ b/About_Kolab_Groupware/de-DE/sect-About_Kolab_Groupware.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/About_Kolab_Groupware/de-DE/sect-Feedback.po b/About_Kolab_Groupware/de-DE/sect-Feedback.po
index 047d58b..f5c6611 100644
--- a/About_Kolab_Groupware/de-DE/sect-Feedback.po
+++ b/About_Kolab_Groupware/de-DE/sect-Feedback.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/About_Kolab_Groupware/de-DE/sect-Kolab_Product_Series.po b/About_Kolab_Groupware/de-DE/sect-Kolab_Product_Series.po
index 4e5651a..ac8613e 100644
--- a/About_Kolab_Groupware/de-DE/sect-Kolab_Product_Series.po
+++ b/About_Kolab_Groupware/de-DE/sect-Kolab_Product_Series.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/About_Kolab_Groupware/de-DE/sect-Supported_Platforms_and_System_Requirements.po b/About_Kolab_Groupware/de-DE/sect-Supported_Platforms_and_System_Requirements.po
index 2802b9c..87d9063 100644
--- a/About_Kolab_Groupware/de-DE/sect-Supported_Platforms_and_System_Requirements.po
+++ b/About_Kolab_Groupware/de-DE/sect-Supported_Platforms_and_System_Requirements.po
@@ -5,8 +5,8 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15 22:06+0000\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03 11:14+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
"MIME-Version: 1.0\n"
diff --git a/About_Kolab_Groupware/es-ES/About_Kolab_Groupware.po b/About_Kolab_Groupware/es-ES/About_Kolab_Groupware.po
index 0902d26..1fb7a57 100644
--- a/About_Kolab_Groupware/es-ES/About_Kolab_Groupware.po
+++ b/About_Kolab_Groupware/es-ES/About_Kolab_Groupware.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/About_Kolab_Groupware/es-ES/Article_Info.po b/About_Kolab_Groupware/es-ES/Article_Info.po
index f0ffaf2..71e58fd 100644
--- a/About_Kolab_Groupware/es-ES/Article_Info.po
+++ b/About_Kolab_Groupware/es-ES/Article_Info.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/About_Kolab_Groupware/es-ES/Revision_History.po b/About_Kolab_Groupware/es-ES/Revision_History.po
index 4e1f372..a5f466e 100644
--- a/About_Kolab_Groupware/es-ES/Revision_History.po
+++ b/About_Kolab_Groupware/es-ES/Revision_History.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/About_Kolab_Groupware/es-ES/sect-About_Kolab_Groupware.po b/About_Kolab_Groupware/es-ES/sect-About_Kolab_Groupware.po
index 47a14c9..0503a2c 100644
--- a/About_Kolab_Groupware/es-ES/sect-About_Kolab_Groupware.po
+++ b/About_Kolab_Groupware/es-ES/sect-About_Kolab_Groupware.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/About_Kolab_Groupware/es-ES/sect-Feedback.po b/About_Kolab_Groupware/es-ES/sect-Feedback.po
index fde1efb..5861ace 100644
--- a/About_Kolab_Groupware/es-ES/sect-Feedback.po
+++ b/About_Kolab_Groupware/es-ES/sect-Feedback.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/About_Kolab_Groupware/es-ES/sect-Kolab_Product_Series.po b/About_Kolab_Groupware/es-ES/sect-Kolab_Product_Series.po
index c366c57..5a49f56 100644
--- a/About_Kolab_Groupware/es-ES/sect-Kolab_Product_Series.po
+++ b/About_Kolab_Groupware/es-ES/sect-Kolab_Product_Series.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/About_Kolab_Groupware/es-ES/sect-Supported_Platforms_and_System_Requirements.po b/About_Kolab_Groupware/es-ES/sect-Supported_Platforms_and_System_Requirements.po
index 8b50c6a..8e3b615 100644
--- a/About_Kolab_Groupware/es-ES/sect-Supported_Platforms_and_System_Requirements.po
+++ b/About_Kolab_Groupware/es-ES/sect-Supported_Platforms_and_System_Requirements.po
@@ -5,8 +5,8 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15 22:06+0000\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03 11:14+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
"MIME-Version: 1.0\n"
@@ -18,12 +18,12 @@ msgstr ""
#. Tag: title
#, no-c-format
msgid "Supported Platforms and System Requirements"
-msgstr ""
+msgstr "Plataformas compatibles y requisitos del sistema"
#. Tag: para
#, no-c-format
msgid "Kolab Groupware is supported on the following platforms;"
-msgstr ""
+msgstr "Kolab Groupware es compatible con las siguientes plataformas;"
#. Tag: para
#, no-c-format
@@ -33,34 +33,34 @@ msgid ""
" to keep up with the latest distribution release ear-marked stable. </para> "
"</footnote>, including but not limited to the following distributions, in no"
" particular order other then alphabetic;"
-msgstr ""
+msgstr "Todas las versiones razonablemente recientes de Linux\n<footnote> <para> Por versiones razonablemente recientes de Linux, debemos indicar que el proyecto Kolab puede llegar a mantenerse al día con la última versión estable de la distribución.</para> </footnote>, incluyendo pero no limitado a las siguientes distribuciones, sin ningún otro orden en particular, que el alfabético;"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"http://centos.org\">CentOS</ulink>"
-msgstr ""
+msgstr "<ulink url=\"http://centos.org\">CentOS</ulink>"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"http://debian.org\">Debian</ulink>"
-msgstr ""
+msgstr "<ulink url=\"http://debian.org\">Debian</ulink>"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"http://fedoraproject.org\">Fedora</ulink>"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org\">Fedora</ulink>"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"http://redhat.com\">Red Hat Enterprise Linux</ulink>"
-msgstr ""
+msgstr "<ulink url=\"http://redhat.com\">Red Hat Enterprise Linux</ulink>"
#. Tag: para
#, no-c-format
msgid ""
"<ulink url=\"http://www.univention.de/index.php?id=964&amp;L=1\">Univention "
"Corporate Server</ulink>"
-msgstr ""
+msgstr "<ulink url=\"http://www.univention.de/index.php?id=964&amp;L=1\">Univention Corporate Server</ulink>"
#. Tag: para
#, no-c-format
diff --git a/About_Kolab_Groupware/ja-JP/About_Kolab_Groupware.po b/About_Kolab_Groupware/ja-JP/About_Kolab_Groupware.po
index 2beab65..12283f7 100644
--- a/About_Kolab_Groupware/ja-JP/About_Kolab_Groupware.po
+++ b/About_Kolab_Groupware/ja-JP/About_Kolab_Groupware.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:44\n"
-"PO-Revision-Date: 2012-08-24T15:34:44\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -19,16 +22,26 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Kolab is a groupware solution for Email communications, Events &amp; Appointments, Contacts and more. It supports <emphasis>mixed client environments</emphasis> because of an <emphasis>open storage format</emphasis>, and the use of well-established, standard protocols such as IMAP and SMTP."
+msgid ""
+"Kolab is a groupware solution for Email communications, Events &amp; "
+"Appointments, Contacts and more. It supports <emphasis>mixed client "
+"environments</emphasis> because of an <emphasis>open storage "
+"format</emphasis>, and the use of well-established, standard protocols such "
+"as IMAP and SMTP."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For the full Kolab experience, you need a Kolab server, and one or more Kolab clients. What makes Kolab a unique groupware solution is its focus on security, scalability, data ownership and the use of proven components and protocols."
+msgid ""
+"For the full Kolab experience, you need a Kolab server, and one or more "
+"Kolab clients. What makes Kolab a unique groupware solution is its focus on "
+"security, scalability, data ownership and the use of proven components and "
+"protocols."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Kolab Groupware is an award-winning Free and Open Source Software <acronym>FOSS</acronym> solution."
+msgid ""
+"Kolab Groupware is an award-winning Free and Open Source Software "
+"<acronym>FOSS</acronym> solution."
msgstr ""
-
diff --git a/About_Kolab_Groupware/ja-JP/Article_Info.po b/About_Kolab_Groupware/ja-JP/Article_Info.po
index 4fe057b..c4d240c 100644
--- a/About_Kolab_Groupware/ja-JP/Article_Info.po
+++ b/About_Kolab_Groupware/ja-JP/Article_Info.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:44\n"
-"PO-Revision-Date: 2012-08-24T15:34:44\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -26,4 +29,3 @@ msgstr ""
#, no-c-format
msgid "Kolab Groupware"
msgstr ""
-
diff --git a/About_Kolab_Groupware/ja-JP/Author_Group.po b/About_Kolab_Groupware/ja-JP/Author_Group.po
index 7a2607c..b3d3f2f 100644
--- a/About_Kolab_Groupware/ja-JP/Author_Group.po
+++ b/About_Kolab_Groupware/ja-JP/Author_Group.po
@@ -1,13 +1,14 @@
-#
+#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:44\n"
+"POT-Creation-Date: 2012-08-24T15:35:42\n"
"PO-Revision-Date: 2012-08-24T15:34:44\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@@ -46,4 +47,3 @@ msgstr ""
#, no-c-format
msgid "Systems Architect"
msgstr ""
-
diff --git a/About_Kolab_Groupware/ja-JP/Revision_History.po b/About_Kolab_Groupware/ja-JP/Revision_History.po
index 25f3c4c..5ef6fe4 100644
--- a/About_Kolab_Groupware/ja-JP/Revision_History.po
+++ b/About_Kolab_Groupware/ja-JP/Revision_History.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:44\n"
-"PO-Revision-Date: 2012-08-24T15:34:44\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -31,4 +34,3 @@ msgstr ""
#, no-c-format
msgid "Initial creation of book by publican"
msgstr ""
-
diff --git a/About_Kolab_Groupware/ja-JP/sect-About_Kolab_Groupware.po b/About_Kolab_Groupware/ja-JP/sect-About_Kolab_Groupware.po
index 706c087..09009f3 100644
--- a/About_Kolab_Groupware/ja-JP/sect-About_Kolab_Groupware.po
+++ b/About_Kolab_Groupware/ja-JP/sect-About_Kolab_Groupware.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:44\n"
-"PO-Revision-Date: 2012-08-24T15:34:44\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -19,12 +22,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Kolab Groupware is a highly scalable, flexible, mutli-platform solution for Emails, Appointments, Contacts and more. It supports mixed client environments (Outlook/KDE) because of a well-defined, interoperable and open storage format. Any email client speaking standard protocols can be served."
+msgid ""
+"Kolab Groupware is a highly scalable, flexible, mutli-platform solution for "
+"Emails, Appointments, Contacts and more. It supports mixed client "
+"environments (Outlook/KDE) because of a well-defined, interoperable and open"
+" storage format. Any email client speaking standard protocols can be served."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Kolab Groupware solution consists of many Free Software components, integrated by Kolab in order to build a groupware solution."
+msgid ""
+"The Kolab Groupware solution consists of many Free Software components, "
+"integrated by Kolab in order to build a groupware solution."
msgstr ""
#. Tag: title
@@ -44,7 +53,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Postfix attempts to be fast, easy to administer, and secure. The outside has a definite Sendmail-ish flavor, but the inside is completely different."
+msgid ""
+"Postfix attempts to be fast, easy to administer, and secure. The outside has"
+" a definite Sendmail-ish flavor, but the inside is completely different."
msgstr ""
#. Tag: para
@@ -59,7 +70,11 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Cyrus IMAP is a highly scalable enterprise mail system designed for use in enterprise environments of various sizes using standards based technologies. Cyrus IMAP technologies scale from independent use in email departments to a system centrally managed in a large enterprise."
+msgid ""
+"Cyrus IMAP is a highly scalable enterprise mail system designed for use in "
+"enterprise environments of various sizes using standards based technologies."
+" Cyrus IMAP technologies scale from independent use in email departments to "
+"a system centrally managed in a large enterprise."
msgstr ""
#. Tag: para
@@ -74,7 +89,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "OpenLDAP Software is an open source implementation of the Lightweight Directory Access Protocol."
+msgid ""
+"OpenLDAP Software is an open source implementation of the Lightweight "
+"Directory Access Protocol."
msgstr ""
#. Tag: para
@@ -89,11 +106,14 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Roundcube webmail is a browser-based multilingual IMAP client with an application-like user interface. It provides full functionality you expect from an e-mail client, including MIME support, address book, folder manipulation, message searching and spell checking."
+msgid ""
+"Roundcube webmail is a browser-based multilingual IMAP client with an "
+"application-like user interface. It provides full functionality you expect "
+"from an e-mail client, including MIME support, address book, folder "
+"manipulation, message searching and spell checking."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Website: <ulink url=\"http://www.roundcube.net/\" />"
msgstr ""
-
diff --git a/About_Kolab_Groupware/ja-JP/sect-Feedback.po b/About_Kolab_Groupware/ja-JP/sect-Feedback.po
index 51c1c45..ac03bc6 100644
--- a/About_Kolab_Groupware/ja-JP/sect-Feedback.po
+++ b/About_Kolab_Groupware/ja-JP/sect-Feedback.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:44\n"
-"PO-Revision-Date: 2012-08-24T15:34:44\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -19,12 +22,16 @@ msgstr ""
#. Tag: indexterm
#, no-c-format
-msgid "<primary>feedback</primary> <secondary>contact information for this manual</secondary>"
+msgid ""
+"<primary>feedback</primary> <secondary>contact information for this "
+"manual</secondary>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We value feedback on our software as well as our documentation. Please find ways to contact us in this section."
+msgid ""
+"We value feedback on our software as well as our documentation. Please find "
+"ways to contact us in this section."
msgstr ""
#. Tag: title
@@ -34,22 +41,30 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bug reports can be logged in our <ulink url=\"https://bugzilla.kolabsys.com\">Bugzilla issue tracker</ulink>. Please bear in mind registration is required to log bugs."
+msgid ""
+"Bug reports can be logged in our <ulink "
+"url=\"https://bugzilla.kolabsys.com\">Bugzilla issue tracker</ulink>. Please"
+" bear in mind registration is required to log bugs."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Before reporting a bug, please search the issue tracker for existing bugs that may report the same problem."
+msgid ""
+"Before reporting a bug, please search the issue tracker for existing bugs "
+"that may report the same problem."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When reporting a bug, please prepare to provide the following information;"
+msgid ""
+"When reporting a bug, please prepare to provide the following information;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Your platform, and if applicable, your distribution and the distribution version."
+msgid ""
+"Your platform, and if applicable, your distribution and the distribution "
+"version."
msgstr ""
#. Tag: para
@@ -59,7 +74,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a custom version is used, any options that may have specified during the build process."
+msgid ""
+"If a custom version is used, any options that may have specified during the "
+"build process."
msgstr ""
#. Tag: title
@@ -69,7 +86,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Mailing lists are a quick way to get in touch with a large number of subscribers, who may know the answer to your question or can provide you with additional insight."
+msgid ""
+"Mailing lists are a quick way to get in touch with a large number of "
+"subscribers, who may know the answer to your question or can provide you "
+"with additional insight."
msgstr ""
#. Tag: title
@@ -79,7 +99,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Kolab Groupware administrators and developers are strongly encouraged to subscribe to the moderated, low-volume announcement mailing list, to which important release announcements are submitted. We have the announcement mailing list available at <ulink url=\"https://lists.kolab.org/mailman/listinfo/kolab-announce\" />. To subscribe to the list, either click the aforementioned link and fill out the information requested, or send an email to <ulink url=\"mailto:kolab-announce-subscribe@kolab.org\">kolab-announce-subscribe@kolab.org</ulink>."
+msgid ""
+"Kolab Groupware administrators and developers are strongly encouraged to "
+"subscribe to the moderated, low-volume announcement mailing list, to which "
+"important release announcements are submitted. We have the announcement "
+"mailing list available at <ulink "
+"url=\"https://lists.kolab.org/mailman/listinfo/kolab-announce\" />. To "
+"subscribe to the list, either click the aforementioned link and fill out the"
+" information requested, or send an email to <ulink url=\"mailto:kolab-"
+"announce-subscribe@kolab.org\">kolab-announce-subscribe@kolab.org</ulink>."
msgstr ""
#. Tag: title
@@ -89,7 +117,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For users of Kolab software, we run a public mailing list at <ulink url=\"https://lists.kolab.org/mailman/listinfo/kolab-users\" />. To subscribe to the list, either click the aforementioned link and fill out the information requested, or send an email to <ulink url=\"mailto:kolab-users-subscribe@kolab.org\">kolab-users-subscribe@kolab.org</ulink>."
+msgid ""
+"For users of Kolab software, we run a public mailing list at <ulink "
+"url=\"https://lists.kolab.org/mailman/listinfo/kolab-users\" />. To "
+"subscribe to the list, either click the aforementioned link and fill out the"
+" information requested, or send an email to <ulink url=\"mailto:kolab-users-"
+"subscribe@kolab.org\">kolab-users-subscribe@kolab.org</ulink>."
msgstr ""
#. Tag: title
@@ -99,7 +132,13 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For developers of Kolab software, as well as general discussion on bugs and patches, we run a public mailing list at <ulink url=\"https://lists.kolab.org/mailman/listinfo/kolab-devel\" />. To subscribe to the list and fill out the information requested, or send an email to <ulink url=\"mailto:kolab-devel-subscribe@kolab.org\">kolab-devel-subscribe@kolab.org</ulink>."
+msgid ""
+"For developers of Kolab software, as well as general discussion on bugs and "
+"patches, we run a public mailing list at <ulink "
+"url=\"https://lists.kolab.org/mailman/listinfo/kolab-devel\" />. To "
+"subscribe to the list and fill out the information requested, or send an "
+"email to <ulink url=\"mailto:kolab-devel-subscribe@kolab.org\">kolab-devel-"
+"subscribe@kolab.org</ulink>."
msgstr ""
#. Tag: title
@@ -109,7 +148,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The archives of the announcement, user support and development discussion mailing lists are available through web archives."
+msgid ""
+"The archives of the announcement, user support and development discussion "
+"mailing lists are available through web archives."
msgstr ""
#. Tag: title
@@ -119,11 +160,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Internet Relay Chat (IRC) is another way to get in touch with some of the people that develop and use Kolab Groupware. Use your favorite IRC client to connect to the <ulink url=\"http://freenode.net\">FreeNode IRC Network</ulink>, or use the <ulink url=\"http://webchat.freenode.net?channels=kolab&amp;uio=d4\">web-based chat</ulink>."
+msgid ""
+"Internet Relay Chat (IRC) is another way to get in touch with some of the "
+"people that develop and use Kolab Groupware. Use your favorite IRC client to"
+" connect to the <ulink url=\"http://freenode.net\">FreeNode IRC "
+"Network</ulink>, or use the <ulink "
+"url=\"http://webchat.freenode.net?channels=kolab&amp;uio=d4\">web-based "
+"chat</ulink>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Once connected, join us in <ulink url=\"irc://irc.freenode.net/kolab\">the #kolab IRC channel</ulink>."
+msgid ""
+"Once connected, join us in <ulink url=\"irc://irc.freenode.net/kolab\">the "
+"#kolab IRC channel</ulink>."
msgstr ""
-
diff --git a/About_Kolab_Groupware/ja-JP/sect-Kolab_Product_Series.po b/About_Kolab_Groupware/ja-JP/sect-Kolab_Product_Series.po
index fd9bc55..e359197 100644
--- a/About_Kolab_Groupware/ja-JP/sect-Kolab_Product_Series.po
+++ b/About_Kolab_Groupware/ja-JP/sect-Kolab_Product_Series.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:44\n"
-"PO-Revision-Date: 2012-08-24T15:34:44\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -19,27 +22,45 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Kolab Groupware consists of free software components, each of which are available from various upstream development and support project organizations, including Linux distributions."
+msgid ""
+"Kolab Groupware consists of free software components, each of which are "
+"available from various upstream development and support project "
+"organizations, including Linux distributions."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Kolab Groupware developers, community members and Kolab Systems engineering and support staff maintain many of the packages related to Kolab with the Linux distributions through which those packages are available."
+msgid ""
+"The Kolab Groupware developers, community members and Kolab Systems "
+"engineering and support staff maintain many of the packages related to Kolab"
+" with the Linux distributions through which those packages are available."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Kolab software repositories can therefor include only those software components, or those specific versions of software components, that differentiate from what is available through the upstream Linux distribution software repositories, and possibly recommended or required additional software repositories."
+msgid ""
+"The Kolab software repositories can therefor include only those software "
+"components, or those specific versions of software components, that "
+"differentiate from what is available through the upstream Linux distribution"
+" software repositories, and possibly recommended or required additional "
+"software repositories."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Product series are versioned, each of them created to provide a sustainable stream of updates to the individual software components included in that product serie."
+msgid ""
+"Product series are versioned, each of them created to provide a sustainable "
+"stream of updates to the individual software components included in that "
+"product serie."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The convention for <emphasis>Server Product Versioning</emphasis> is subject to the guidelines proposed and accepted as <ulink url=\"http://wiki.kolab.org/KEP:5\">Kolab Enhancement Proposal #5</ulink> (KEP #5 for short)."
+msgid ""
+"The convention for <emphasis>Server Product Versioning</emphasis> is subject"
+" to the guidelines proposed and accepted as <ulink "
+"url=\"http://wiki.kolab.org/KEP:5\">Kolab Enhancement Proposal #5</ulink> "
+"(KEP #5 for short)."
msgstr ""
#. Tag: title
@@ -49,47 +70,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Two different product streams exist, a <literal>community</literal> edition and an <literal>enterprise</literal> edition."
+msgid ""
+"Two different product streams exist, a <literal>community</literal> edition "
+"and an <literal>enterprise</literal> edition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The differences between the community edition and the enterprise edition are as follows:"
+msgid ""
+"The differences between the community edition and the enterprise edition are"
+" as follows:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "No debuginfo sub-packages are made available through the repositories for the community edition. You typically need debuginfo sub-paclages in case stack traces need to be generated for binary compiled programs such as mysql, openldap, cyrus-imapd, php and others."
+msgid ""
+"No debuginfo sub-packages are made available through the repositories for "
+"the community edition. You typically need debuginfo sub-paclages in case "
+"stack traces need to be generated for binary compiled programs such as "
+"mysql, openldap, cyrus-imapd, php and others."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The packages available through the repositories for the community edition are not signed with a PGP key, and therefor the authenticity of the packages cannot be verified."
+msgid ""
+"The packages available through the repositories for the community edition "
+"are not signed with a PGP key, and therefor the authenticity of the packages"
+" cannot be verified."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The repositories for the community edition are made available through HTTP only, while the enterprise edition's repositories are available over HTTPS only. For the community edition, the the authenticity cannot be verified."
+msgid ""
+"The repositories for the community edition are made available through HTTP "
+"only, while the enterprise edition's repositories are available over HTTPS "
+"only. For the community edition, the the authenticity cannot be verified."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the repositories for the community edition, no package builds other then the latest are made available. Rolling back a software update foo-1.0-2.el5 to a previously installed software version foo-1.0-1.el5 after a failed update is therefor not possible unless a copy of foo-1.0-1.el5 had been preserved."
+msgid ""
+"In the repositories for the community edition, no package builds other then "
+"the latest are made available. Rolling back a software update foo-1.0-2.el5 "
+"to a previously installed software version foo-1.0-1.el5 after a failed "
+"update is therefor not possible unless a copy of foo-1.0-1.el5 had been "
+"preserved."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For the community edition, no security errata &ndash;other then for critical security issues&ndash; is sent out."
+msgid ""
+"For the community edition, no security errata &ndash;other then for critical"
+" security issues&ndash; is sent out."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The enterprise edition is supported for a longer term than the community edition."
+msgid ""
+"The enterprise edition is supported for a longer term than the community "
+"edition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The software available in the enterprise edition is subjected to thorough quality assurance and certification before being made available."
+msgid ""
+"The software available in the enterprise edition is subjected to thorough "
+"quality assurance and certification before being made available."
msgstr ""
#. Tag: title
@@ -99,16 +145,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "4 different repository stages exist, each of them indicating the expected level of stability, and point-in-time release."
+msgid ""
+"4 different repository stages exist, each of them indicating the expected "
+"level of stability, and point-in-time release."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <literal>release</literal> and <literal>updates</literal> repositories contain the most stable software (community edition) which is supported (professionally in the enterprise edition)."
+msgid ""
+"The <literal>release</literal> and <literal>updates</literal> repositories "
+"contain the most stable software (community edition) which is supported "
+"(professionally in the enterprise edition)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <literal>updates-testing</literal> repositories contain software that is being stabilized (through the collection of community feedback for the community edition) before being submitted to the <literal>updates</literal> repository."
+msgid ""
+"The <literal>updates-testing</literal> repositories contain software that is"
+" being stabilized (through the collection of community feedback for the "
+"community edition) before being submitted to the <literal>updates</literal> "
+"repository."
msgstr ""
-
diff --git a/About_Kolab_Groupware/ja-JP/sect-Supported_Platforms_and_System_Requirements.po b/About_Kolab_Groupware/ja-JP/sect-Supported_Platforms_and_System_Requirements.po
index c2196e2..a93d78b 100644
--- a/About_Kolab_Groupware/ja-JP/sect-Supported_Platforms_and_System_Requirements.po
+++ b/About_Kolab_Groupware/ja-JP/sect-Supported_Platforms_and_System_Requirements.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:44\n"
-"PO-Revision-Date: 2012-08-24T15:34:44\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03 11:14+0000\n"
+"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -24,7 +27,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "All reasonably recent versions of Linux<footnote> <para> By reasonably recent versions of Linux, we intend to indicate the Kolab project can manage to keep up with the latest distribution release ear-marked stable. </para> </footnote>, including but not limited to the following distributions, in no particular order other then alphabetic;"
+msgid ""
+"All reasonably recent versions of Linux<footnote> <para> By reasonably "
+"recent versions of Linux, we intend to indicate the Kolab project can manage"
+" to keep up with the latest distribution release ear-marked stable. </para> "
+"</footnote>, including but not limited to the following distributions, in no"
+" particular order other then alphabetic;"
msgstr ""
#. Tag: para
@@ -49,11 +57,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<ulink url=\"http://www.univention.de/index.php?id=964&amp;L=1\">Univention Corporate Server</ulink>"
+msgid ""
+"<ulink url=\"http://www.univention.de/index.php?id=964&amp;L=1\">Univention "
+"Corporate Server</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Should your Linux distribution or platform not be listed here, please refer to <xref linkend=\"sect-About_Kolab_Groupware-Feedback\" /> for ways of contacting the Kolab Development team."
+msgid ""
+"Should your Linux distribution or platform not be listed here, please refer "
+"to <xref linkend=\"sect-About_Kolab_Groupware-Feedback\" /> for ways of "
+"contacting the Kolab Development team."
msgstr ""
-
diff --git a/About_Kolab_Groupware/nl-NL/About_Kolab_Groupware.po b/About_Kolab_Groupware/nl-NL/About_Kolab_Groupware.po
index 4773bbe..e8838f8 100644
--- a/About_Kolab_Groupware/nl-NL/About_Kolab_Groupware.po
+++ b/About_Kolab_Groupware/nl-NL/About_Kolab_Groupware.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 15:47+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: Dutch (http://www.transifex.com/projects/p/kolab/language/nl/)\n"
diff --git a/About_Kolab_Groupware/nl-NL/Article_Info.po b/About_Kolab_Groupware/nl-NL/Article_Info.po
index cb70aa1..b9dc008 100644
--- a/About_Kolab_Groupware/nl-NL/Article_Info.po
+++ b/About_Kolab_Groupware/nl-NL/Article_Info.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Dutch (http://www.transifex.com/projects/p/kolab/language/nl/)\n"
diff --git a/About_Kolab_Groupware/nl-NL/Revision_History.po b/About_Kolab_Groupware/nl-NL/Revision_History.po
index 192b3e0..739edb8 100644
--- a/About_Kolab_Groupware/nl-NL/Revision_History.po
+++ b/About_Kolab_Groupware/nl-NL/Revision_History.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:14+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Dutch (http://www.transifex.com/projects/p/kolab/language/nl/)\n"
diff --git a/About_Kolab_Groupware/nl-NL/sect-About_Kolab_Groupware.po b/About_Kolab_Groupware/nl-NL/sect-About_Kolab_Groupware.po
index 3cdee20..ecf7423 100644
--- a/About_Kolab_Groupware/nl-NL/sect-About_Kolab_Groupware.po
+++ b/About_Kolab_Groupware/nl-NL/sect-About_Kolab_Groupware.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Dutch (http://www.transifex.com/projects/p/kolab/language/nl/)\n"
diff --git a/About_Kolab_Groupware/nl-NL/sect-Feedback.po b/About_Kolab_Groupware/nl-NL/sect-Feedback.po
index f372f54..bf03d5a 100644
--- a/About_Kolab_Groupware/nl-NL/sect-Feedback.po
+++ b/About_Kolab_Groupware/nl-NL/sect-Feedback.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-14 01:10+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: Dutch (http://www.transifex.com/projects/p/kolab/language/nl/)\n"
diff --git a/About_Kolab_Groupware/nl-NL/sect-Kolab_Product_Series.po b/About_Kolab_Groupware/nl-NL/sect-Kolab_Product_Series.po
index c640d5c..b994159 100644
--- a/About_Kolab_Groupware/nl-NL/sect-Kolab_Product_Series.po
+++ b/About_Kolab_Groupware/nl-NL/sect-Kolab_Product_Series.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Dutch (http://www.transifex.com/projects/p/kolab/language/nl/)\n"
diff --git a/About_Kolab_Groupware/nl-NL/sect-Supported_Platforms_and_System_Requirements.po b/About_Kolab_Groupware/nl-NL/sect-Supported_Platforms_and_System_Requirements.po
index 31cc10e..692ae57 100644
--- a/About_Kolab_Groupware/nl-NL/sect-Supported_Platforms_and_System_Requirements.po
+++ b/About_Kolab_Groupware/nl-NL/sect-Supported_Platforms_and_System_Requirements.po
@@ -5,8 +5,8 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15 22:06+0000\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03 11:14+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: Dutch (http://www.transifex.com/projects/p/kolab/language/nl/)\n"
"MIME-Version: 1.0\n"
diff --git a/About_Kolab_Groupware/pot/About_Kolab_Groupware.pot b/About_Kolab_Groupware/pot/About_Kolab_Groupware.pot
index ae026f9..74b08a8 100644
--- a/About_Kolab_Groupware/pot/About_Kolab_Groupware.pot
+++ b/About_Kolab_Groupware/pot/About_Kolab_Groupware.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03T11:14:06\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/About_Kolab_Groupware/pot/Article_Info.pot b/About_Kolab_Groupware/pot/Article_Info.pot
index c233b23..e86aa28 100644
--- a/About_Kolab_Groupware/pot/Article_Info.pot
+++ b/About_Kolab_Groupware/pot/Article_Info.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03T11:14:06\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/About_Kolab_Groupware/pot/Author_Group.pot b/About_Kolab_Groupware/pot/Author_Group.pot
index b1cb638..1c4bbf9 100644
--- a/About_Kolab_Groupware/pot/Author_Group.pot
+++ b/About_Kolab_Groupware/pot/Author_Group.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03T11:14:06\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/About_Kolab_Groupware/pot/Revision_History.pot b/About_Kolab_Groupware/pot/Revision_History.pot
index f6df477..b84dc85 100644
--- a/About_Kolab_Groupware/pot/Revision_History.pot
+++ b/About_Kolab_Groupware/pot/Revision_History.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03T11:14:06\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/About_Kolab_Groupware/pot/sect-About_Kolab_Groupware.pot b/About_Kolab_Groupware/pot/sect-About_Kolab_Groupware.pot
index 00727e7..2ab25eb 100644
--- a/About_Kolab_Groupware/pot/sect-About_Kolab_Groupware.pot
+++ b/About_Kolab_Groupware/pot/sect-About_Kolab_Groupware.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03T11:14:06\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/About_Kolab_Groupware/pot/sect-Feedback.pot b/About_Kolab_Groupware/pot/sect-Feedback.pot
index b9ad92e..7604a94 100644
--- a/About_Kolab_Groupware/pot/sect-Feedback.pot
+++ b/About_Kolab_Groupware/pot/sect-Feedback.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03T11:14:06\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/About_Kolab_Groupware/pot/sect-Kolab_Product_Series.pot b/About_Kolab_Groupware/pot/sect-Kolab_Product_Series.pot
index f2d1f09..80a64aa 100644
--- a/About_Kolab_Groupware/pot/sect-Kolab_Product_Series.pot
+++ b/About_Kolab_Groupware/pot/sect-Kolab_Product_Series.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03T11:14:06\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/About_Kolab_Groupware/pot/sect-Supported_Platforms_and_System_Requirements.pot b/About_Kolab_Groupware/pot/sect-Supported_Platforms_and_System_Requirements.pot
index 0953eed..929b28b 100644
--- a/About_Kolab_Groupware/pot/sect-Supported_Platforms_and_System_Requirements.pot
+++ b/About_Kolab_Groupware/pot/sect-Supported_Platforms_and_System_Requirements.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-15T22:06:03\n"
-"PO-Revision-Date: 2012-08-15T22:06:03\n"
+"POT-Creation-Date: 2012-09-03T11:14:06\n"
+"PO-Revision-Date: 2012-09-03T11:14:06\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/Administrator_Guide/.tx/config b/Administrator_Guide/.tx/config
index c2310f5..2d17190 100644
--- a/Administrator_Guide/.tx/config
+++ b/Administrator_Guide/.tx/config
@@ -1,6 +1,6 @@
[main]
host = https://www.transifex.net
-lang_map = de: de-DE, es: es-ES, fr: fr-FR, nl: nl-NL
+lang_map = de: de-DE, es: es-ES, fr: fr-FR, ja: ja-JP, nl: nl-NL
type = PO
[kolab.Administrator_Guide-step-select-all-mailboxes]
diff --git a/Administrator_Guide/de-DE/Combating_Spam.po b/Administrator_Guide/de-DE/Combating_Spam.po
index 84922f4..4065c02 100644
--- a/Administrator_Guide/de-DE/Combating_Spam.po
+++ b/Administrator_Guide/de-DE/Combating_Spam.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:16+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Configuring_the_Kolab_Server.po b/Administrator_Guide/de-DE/Configuring_the_Kolab_Server.po
index 1fa4ee2..e480e87 100644
--- a/Administrator_Guide/de-DE/Configuring_the_Kolab_Server.po
+++ b/Administrator_Guide/de-DE/Configuring_the_Kolab_Server.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Detailed_Kolab_Server_Overview.po b/Administrator_Guide/de-DE/Detailed_Kolab_Server_Overview.po
index b72846f..a92677f 100644
--- a/Administrator_Guide/de-DE/Detailed_Kolab_Server_Overview.po
+++ b/Administrator_Guide/de-DE/Detailed_Kolab_Server_Overview.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Kolab_Web_Administration_Panel.po b/Administrator_Guide/de-DE/Kolab_Web_Administration_Panel.po
index a040466..d4db28d 100644
--- a/Administrator_Guide/de-DE/Kolab_Web_Administration_Panel.po
+++ b/Administrator_Guide/de-DE/Kolab_Web_Administration_Panel.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Preface.po b/Administrator_Guide/de-DE/Preface.po
index 2462872..553e077 100644
--- a/Administrator_Guide/de-DE/Preface.po
+++ b/Administrator_Guide/de-DE/Preface.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Revision_History.po b/Administrator_Guide/de-DE/Revision_History.po
index ff00e17..ffab20f 100644
--- a/Administrator_Guide/de-DE/Revision_History.po
+++ b/Administrator_Guide/de-DE/Revision_History.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:19+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Tweaking_Tips_for_389_Directory_Server.po b/Administrator_Guide/de-DE/Tweaking_Tips_for_389_Directory_Server.po
index e9e1936..8f73797 100644
--- a/Administrator_Guide/de-DE/Tweaking_Tips_for_389_Directory_Server.po
+++ b/Administrator_Guide/de-DE/Tweaking_Tips_for_389_Directory_Server.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Tweaking_Tips_for_Cyrus_IMAP.po b/Administrator_Guide/de-DE/Tweaking_Tips_for_Cyrus_IMAP.po
index 38bcfb6..566ef6e 100644
--- a/Administrator_Guide/de-DE/Tweaking_Tips_for_Cyrus_IMAP.po
+++ b/Administrator_Guide/de-DE/Tweaking_Tips_for_Cyrus_IMAP.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Tweaking_Tips_for_Postfix.po b/Administrator_Guide/de-DE/Tweaking_Tips_for_Postfix.po
index 1d1278b..2ecb103 100644
--- a/Administrator_Guide/de-DE/Tweaking_Tips_for_Postfix.po
+++ b/Administrator_Guide/de-DE/Tweaking_Tips_for_Postfix.po
@@ -5,9 +5,9 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
-"PO-Revision-Date: 2012-08-13 13:16+0000\n"
-"Last-Translator: Automatically generated\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
+"PO-Revision-Date: 2012-08-24 15:42+0000\n"
+"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -24,3 +24,66 @@ msgstr ""
#, no-c-format
msgid "para"
msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Large Kolab Distribution Groups"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you have Kolab distribution groups with many members, you may see the "
+"following message occur in log file <filename>/var/log/maillog</filename>:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"Aug 17 10:21:59 kolab postfix/cleanup[5916]: warning: 398194A151: "
+"unreasonable virtual_alias_maps map expansion size for kolab-"
+"users@example.org"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The setting <literal>virtual_alias_expansion_limit</literal> controls the "
+"maximum number of recipient address that are produced from a single original"
+" recipient address. The default depends on your installation."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To get the default value, execute:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"# <userinput>postconf -d virtual_alias_expansion_limit</userinput>\n"
+"1000"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To get the current value, execute:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"# <userinput>postconf virtual_alias_expansion_limit</userinput>\n"
+"1000"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To set a new value, execute:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"# <userinput>postconf -e virtual_alias_expansion_limit=10000</userinput>"
+msgstr ""
diff --git a/Administrator_Guide/de-DE/Tweaking_Tips_for_Roundcube.po b/Administrator_Guide/de-DE/Tweaking_Tips_for_Roundcube.po
index 5669c3a..4a3f9da 100644
--- a/Administrator_Guide/de-DE/Tweaking_Tips_for_Roundcube.po
+++ b/Administrator_Guide/de-DE/Tweaking_Tips_for_Roundcube.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Upgrading_Accounts_from_Kolab_Format_version_2.po b/Administrator_Guide/de-DE/Upgrading_Accounts_from_Kolab_Format_version_2.po
index 75cdb19..ca877e2 100644
--- a/Administrator_Guide/de-DE/Upgrading_Accounts_from_Kolab_Format_version_2.po
+++ b/Administrator_Guide/de-DE/Upgrading_Accounts_from_Kolab_Format_version_2.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/Upgrading_from_Kolab_2_on_OpenPKG.po b/Administrator_Guide/de-DE/Upgrading_from_Kolab_2_on_OpenPKG.po
index ddc7169..ac27750 100644
--- a/Administrator_Guide/de-DE/Upgrading_from_Kolab_2_on_OpenPKG.po
+++ b/Administrator_Guide/de-DE/Upgrading_from_Kolab_2_on_OpenPKG.po
@@ -5,8 +5,8 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
-"PO-Revision-Date: 2012-08-15 22:09+0000\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
+"PO-Revision-Date: 2012-08-24 15:43+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
"MIME-Version: 1.0\n"
@@ -463,9 +463,9 @@ msgid ""
"&gt;&nbsp;&nbsp;&nbsp;<userinput>sed -e 's/user\\///g' | \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;<userinput>while read user; do</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>kolab-formatupgrade \\</userinput>\n"
-"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--user cyrus-admin \\</userinput>\n"
+"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--user \"${user}\" \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--password <replaceable>$password</replaceable> \\</userinput>\n"
-"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--proxyauth \"${user}\" \\</userinput>\n"
+"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--proxyauth cyrus-admin \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--port 143 \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--encrypt TLS \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput><replaceable>localhost</replaceable></userinput>\n"
diff --git a/Administrator_Guide/de-DE/Verifying_the_Installation.po b/Administrator_Guide/de-DE/Verifying_the_Installation.po
index 9ec0490..9fee2b3 100644
--- a/Administrator_Guide/de-DE/Verifying_the_Installation.po
+++ b/Administrator_Guide/de-DE/Verifying_the_Installation.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/chap-About_Kolab_Groupware.po b/Administrator_Guide/de-DE/chap-About_Kolab_Groupware.po
index 301853c..473d43d 100644
--- a/Administrator_Guide/de-DE/chap-About_Kolab_Groupware.po
+++ b/Administrator_Guide/de-DE/chap-About_Kolab_Groupware.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/part-Clients.po b/Administrator_Guide/de-DE/part-Clients.po
index d281755..e7db9be 100644
--- a/Administrator_Guide/de-DE/part-Clients.po
+++ b/Administrator_Guide/de-DE/part-Clients.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/part-Kolab_Server.po b/Administrator_Guide/de-DE/part-Kolab_Server.po
index 675c43c..3d5ada6 100644
--- a/Administrator_Guide/de-DE/part-Kolab_Server.po
+++ b/Administrator_Guide/de-DE/part-Kolab_Server.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/sect-About_Kolab_Groupware.po b/Administrator_Guide/de-DE/sect-About_Kolab_Groupware.po
index 61b6bba..aca3c48 100644
--- a/Administrator_Guide/de-DE/sect-About_Kolab_Groupware.po
+++ b/Administrator_Guide/de-DE/sect-About_Kolab_Groupware.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/sect-Feedback.po b/Administrator_Guide/de-DE/sect-Feedback.po
index 61fdf4a..80720e0 100644
--- a/Administrator_Guide/de-DE/sect-Feedback.po
+++ b/Administrator_Guide/de-DE/sect-Feedback.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/sect-Kolab_Product_Series.po b/Administrator_Guide/de-DE/sect-Kolab_Product_Series.po
index 155660a..04d35c0 100644
--- a/Administrator_Guide/de-DE/sect-Kolab_Product_Series.po
+++ b/Administrator_Guide/de-DE/sect-Kolab_Product_Series.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/sect-Supported_Platforms_and_System_Requirements.po b/Administrator_Guide/de-DE/sect-Supported_Platforms_and_System_Requirements.po
index 1d8b761..9e2b618 100644
--- a/Administrator_Guide/de-DE/sect-Supported_Platforms_and_System_Requirements.po
+++ b/Administrator_Guide/de-DE/sect-Supported_Platforms_and_System_Requirements.po
@@ -5,8 +5,8 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
-"PO-Revision-Date: 2012-08-15 22:09+0000\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
+"PO-Revision-Date: 2012-08-24 15:44+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
"MIME-Version: 1.0\n"
diff --git a/Administrator_Guide/de-DE/step-convert-seen-databases.po b/Administrator_Guide/de-DE/step-convert-seen-databases.po
index df02c6c..ed8c63f 100644
--- a/Administrator_Guide/de-DE/step-convert-seen-databases.po
+++ b/Administrator_Guide/de-DE/step-convert-seen-databases.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/de-DE/step-select-all-mailboxes.po b/Administrator_Guide/de-DE/step-select-all-mailboxes.po
index 0ffa101..78f0656 100644
--- a/Administrator_Guide/de-DE/step-select-all-mailboxes.po
+++ b/Administrator_Guide/de-DE/step-select-all-mailboxes.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-15 22:08+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: German (http://www.transifex.com/projects/p/kolab/language/de/)\n"
diff --git a/Administrator_Guide/en-US/Administrator_Guide.xml b/Administrator_Guide/en-US/Administrator_Guide.xml
index 6fe4f69..bad0d1a 100644
--- a/Administrator_Guide/en-US/Administrator_Guide.xml
+++ b/Administrator_Guide/en-US/Administrator_Guide.xml
@@ -4,10 +4,10 @@
%BOOK_ENTITIES;
]>
<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="part-Kolab_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <!-- <xi:include href="part-Kolab_Clients.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <index />
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="part-Kolab_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!-- <xi:include href="part-Kolab_Clients.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <index />
</book>
diff --git a/Administrator_Guide/en-US/Book_Info.xml b/Administrator_Guide/en-US/Book_Info.xml
index 6376136..2816fc4 100644
--- a/Administrator_Guide/en-US/Book_Info.xml
+++ b/Administrator_Guide/en-US/Book_Info.xml
@@ -4,28 +4,28 @@
%BOOK_ENTITIES;
]>
<bookinfo id="book-Administrator_Guide-Administrator_Guide">
- <title>Administrator Guide</title>
- <subtitle>short description</subtitle>
- <productname>Kolab Groupware</productname>
- <productnumber>3.0</productnumber>
- <edition>0</edition>
- <pubsnumber>0</pubsnumber>
- <abstract>
- <para>
- A short overview and summary of the book's subject and purpose, traditionally no more than one paragraph long. Note: the abstract will appear in the front matter of your book and will also be placed in the description field of the book's RPM spec file.
- </para>
+ <title>Administrator Guide</title>
+ <subtitle>short description</subtitle>
+ <productname>Kolab Groupware</productname>
+ <productnumber>3.0</productnumber>
+ <edition>0</edition>
+ <pubsnumber>0</pubsnumber>
+ <abstract>
+ <para>
+ A short overview and summary of the book's subject and purpose, traditionally no more than one paragraph long. Note: the abstract will appear in the front matter of your book and will also be placed in the description field of the book's RPM spec file.
+ </para>
- </abstract>
- <corpauthor>
- <inlinemediaobject>
- <imageobject>
- <imagedata fileref="images/title_logo.png" format="PNG" />
- </imageobject>
+ </abstract>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/title_logo.png" format="PNG" />
+ </imageobject>
- </inlinemediaobject>
+ </inlinemediaobject>
- </corpauthor>
- <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ </corpauthor>
+ <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</bookinfo>
diff --git a/Administrator_Guide/en-US/Combating_Spam.xml b/Administrator_Guide/en-US/Combating_Spam.xml
index cd00ca2..9942529 100644
--- a/Administrator_Guide/en-US/Combating_Spam.xml
+++ b/Administrator_Guide/en-US/Combating_Spam.xml
@@ -4,723 +4,723 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Combating_Spam">
- <title>Combating Spam</title>
- <para>
- Kolab Groupware includes <application>SpamAssassin</application>, a fast, well-established anti-spam solution with a large community of supporters contributing not only to the code, but to rulesets as well.
- </para>
- <para>
- Combating spam is always a tricky situation. On the organizational level, a strategy has to be formulated to combat spam in order to achieve the maximum flexibility and effectiveness for individual users, separate organizations, and the deployment as a whole.
- </para>
- <para>
- A common deployment is to define deployment-wide user preferences and to use a single, deployment-wide set of rules for <application>SpamAssassin</application> to operate with -including Bayes database(s).
- </para>
- <para>
- The problems start when individual users mark legitimate email as spam, most notably the company newsletter or correspondation they have opted in some time ago, but wish to no longer receive. Users tend to ignore the long-term effects of marking these message as spam, if at all they are aware of any, and just want such messages out of their way.
- </para>
- <para>
- Common examples of the sort of messages that are often marked as spam while being legitimate traffic include:
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- Newsletters, where users, rather then unsubscribe, mark legitimate messages as spam,
- </para>
-
- </listitem>
- <listitem>
- <para>
- Notifications from social networks such as from Google+, Facebook, Twitter, etc., where users, rather then adjust their notification preferences, mark legitimate messages as spam,
- </para>
-
- </listitem>
- <listitem>
- <para>
- Notifications from forums and/or services,
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
- <para>
- If enough users mark these messages as spam, the system will start to recognize these messages as spam, and other users may be prevented from receiving the same or similar messages in their INBOX.
- </para>
- <para>
- <application>Amavis</application>, the default content filter performing anti-virus and anti-spam, wraps around <application>SpamAssassin</application> to achieve this flexibility.
- </para>
- <para>
- Separate Bayes database(s) can be created on a per-recipient and per-policy-bank <application>SpamAssassin</application> configuration files and SQL Bayes usernames.
- </para>
- <para>
- Without over-complicating things, a common scenario sufficiently serving the anti-spam effort, includes the following aspects;
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- A <code>shared/Spam</code> folder is created, with permissions for all users to lookup, read, and insert messages. It is the intention users move or copy messages they think are spam into this folder.
- </para>
- <note>
- <para>
- Note that, optionally, the permissions for users to maintain the 'seen' state of messages could not be granted, which in combination with <literal>sharedseen</literal> could provide a mechanism that would allow users to view which messages have been learned as spam in the past.
- </para>
-
- </note>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
- <section id="sect-Administrator_Guide-Combating_Spam-Learning_About_New_Spam">
- <title>Learning About New Spam</title>
- <para>
- Optionally, find all folders named "Spam" or "Junk":
- </para>
- <para>
-
+ <title>Combating Spam</title>
+ <para>
+ Kolab Groupware includes <application>SpamAssassin</application>, a fast, well-established anti-spam solution with a large community of supporters contributing not only to the code, but to rulesets as well.
+ </para>
+ <para>
+ Combating spam is always a tricky situation. On the organizational level, a strategy has to be formulated to combat spam in order to achieve the maximum flexibility and effectiveness for individual users, separate organizations, and the deployment as a whole.
+ </para>
+ <para>
+ A common deployment is to define deployment-wide user preferences and to use a single, deployment-wide set of rules for <application>SpamAssassin</application> to operate with -including Bayes database(s).
+ </para>
+ <para>
+ The problems start when individual users mark legitimate email as spam, most notably the company newsletter or correspondation they have opted in some time ago, but wish to no longer receive. Users tend to ignore the long-term effects of marking these message as spam, if at all they are aware of any, and just want such messages out of their way.
+ </para>
+ <para>
+ Common examples of the sort of messages that are often marked as spam while being legitimate traffic include:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Newsletters, where users, rather then unsubscribe, mark legitimate messages as spam,
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Notifications from social networks such as from Google+, Facebook, Twitter, etc., where users, rather then adjust their notification preferences, mark legitimate messages as spam,
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Notifications from forums and/or services,
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+ <para>
+ If enough users mark these messages as spam, the system will start to recognize these messages as spam, and other users may be prevented from receiving the same or similar messages in their INBOX.
+ </para>
+ <para>
+ <application>Amavis</application>, the default content filter performing anti-virus and anti-spam, wraps around <application>SpamAssassin</application> to achieve this flexibility.
+ </para>
+ <para>
+ Separate Bayes database(s) can be created on a per-recipient and per-policy-bank <application>SpamAssassin</application> configuration files and SQL Bayes usernames.
+ </para>
+ <para>
+ Without over-complicating things, a common scenario sufficiently serving the anti-spam effort, includes the following aspects;
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ A <code>shared/Spam</code> folder is created, with permissions for all users to lookup, read, and insert messages. It is the intention users move or copy messages they think are spam into this folder.
+ </para>
+ <note>
+ <para>
+ Note that, optionally, the permissions for users to maintain the 'seen' state of messages could not be granted, which in combination with <literal>sharedseen</literal> could provide a mechanism that would allow users to view which messages have been learned as spam in the past.
+ </para>
+
+ </note>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+ <section id="sect-Administrator_Guide-Combating_Spam-Learning_About_New_Spam">
+ <title>Learning About New Spam</title>
+ <para>
+ Optionally, find all folders named "Spam" or "Junk":
+ </para>
+ <para>
+
<screen>$ <userinput>find /var/spool/imap/ -type d -name "Spam" -o -name "Junk"</userinput></screen>
- </para>
- <note>
- <para>
- Finding all folders called "Spam" or "Junk" can potentially take a long time, depending on the size of the spool.
- </para>
-
- </note>
- <remark> We would like to do the very same through IMAP, with annotations / SPECIAL-USE. </remark>
- <para>
+ </para>
+ <note>
+ <para>
+ Finding all folders called "Spam" or "Junk" can potentially take a long time, depending on the size of the spool.
+ </para>
+ </note>
+ <remark> We would like to do the very same through IMAP, with annotations / SPECIAL-USE. </remark>
+ <para>
+
<screen>$ <userinput>sa-learn --spam /path/to/folder/[0-9]*.</userinput></screen>
- </para>
- <note>
- <para>
- <application>SpamAssassin</application> will not learn about messages it has learned about before. There's no requirement of purging or deleting the messages that <application>SpamAssassin</application> has learned about already, and purging or deleting those messages only helps to speed up the learning process run.
- </para>
-
- </note>
- <warning>
- <para>
- Do NOT delete the messages from the filesystem directly. Please refer to <xref linkend="sect-Administrator_Guide-Combating_Spam-Expiring_Messages_from_SpamHam_Shared_Folders" /> for ways to purge, expire and/or delete messages from spam folders in a sustainable way.
- </para>
-
- </warning>
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Preseeding_the_Bayes_Database">
- <title>Preseeding the Bayes Database</title>
- <para>
- As Bayes is only effective after it has learned about 200 messages, it is recommended to preseed the Bayes database with some high-quality ham and spam. Preseeding the Bayes database with some ham, and some spam, is done using the <emphasis>SpamAssassin Public Corpus</emphasis>. The public corpus consists of many messages qualified as ham and spam, collected from a variety of sources.
- </para>
- <para>
- The SpamAssassin Public Corpus can be found at <ulink url="http://spamassassin.apache.org/publiccorpus/" />.
- </para>
- <procedure id="proc-Administrator_Guide-Preseeding_the_Bayes_Database-Preseeding_the_Bayes_Database_using_SpamAssassin_Public_Corpus">
- <title>Preseeding the Bayes Database using SpamAssassin Public Corpus</title>
- <step>
- <para>
- Obtain the ham and spam archives:
- </para>
- <para>
-
+ </para>
+ <note>
+ <para>
+ <application>SpamAssassin</application> will not learn about messages it has learned about before. There's no requirement of purging or deleting the messages that <application>SpamAssassin</application> has learned about already, and purging or deleting those messages only helps to speed up the learning process run.
+ </para>
+
+ </note>
+ <warning>
+ <para>
+ Do NOT delete the messages from the filesystem directly. Please refer to <xref linkend="sect-Administrator_Guide-Combating_Spam-Expiring_Messages_from_SpamHam_Shared_Folders" /> for ways to purge, expire and/or delete messages from spam folders in a sustainable way.
+ </para>
+
+ </warning>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Preseeding_the_Bayes_Database">
+ <title>Preseeding the Bayes Database</title>
+ <para>
+ As Bayes is only effective after it has learned about 200 messages, it is recommended to preseed the Bayes database with some high-quality ham and spam. Preseeding the Bayes database with some ham, and some spam, is done using the <emphasis>SpamAssassin Public Corpus</emphasis>. The public corpus consists of many messages qualified as ham and spam, collected from a variety of sources.
+ </para>
+ <para>
+ The SpamAssassin Public Corpus can be found at <ulink url="http://spamassassin.apache.org/publiccorpus/" />.
+ </para>
+ <procedure id="proc-Administrator_Guide-Preseeding_the_Bayes_Database-Preseeding_the_Bayes_Database_using_SpamAssassin_Public_Corpus">
+ <title>Preseeding the Bayes Database using SpamAssassin Public Corpus</title>
+ <step>
+ <para>
+ Obtain the ham and spam archives:
+ </para>
+ <para>
+
<screen># mkdir -p /tmp/salearn
# cd /tmp/salearn
# wget --recursive --timestamping --no-directories --level=1 --reject=gif,png,html,=A,=D http://spamassassin.apache.org/publiccorpus/</screen>
- </para>
-
- </step>
- <step>
- <para>
- Extract the archives:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Extract the archives:
+ </para>
+ <para>
+
<screen># for archive in `ls -1 *.tar.bz2`; do tar jxf $archive; done</screen>
- </para>
-
- </step>
- <step>
- <para>
- For all files in the ham directories, learn those messages as ham:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ For all files in the ham directories, learn those messages as ham:
+ </para>
+ <para>
+
<screen># sa-learn --progress --ham *ham*/*</screen>
- </para>
- <note>
- <para>
- The total number of messages is about 7000. Learning about all of them may take quite a while. We recommend running the command in a screen.
- </para>
-
- </note>
-
- </step>
- <step>
- <para>
- For all files in the spam directories, learn those messages as spam:
- </para>
- <para>
-
+ </para>
+ <note>
+ <para>
+ The total number of messages is about 7000. Learning about all of them may take quite a while. We recommend running the command in a screen.
+ </para>
+
+ </note>
+
+ </step>
+ <step>
+ <para>
+ For all files in the spam directories, learn those messages as spam:
+ </para>
+ <para>
+
<screen># sa-learn --progress --spam *spam*/*</screen>
- </para>
- <note>
- <para>
- The total number of messages is about 2500. Learning about all of them may take quite a while. We recommend running the command in a screen.
- </para>
-
- </note>
-
- </step>
-
- </procedure>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Trapping_Massive_Amounts_of_Spam">
- <title>Trapping Massive Amounts of Spam</title>
- <para>
- To learn about spam quickly, allow the Cyrus IMAP postuser to post into a shared folder that will be included in the regular <command>sa-learn</command> run.
- </para>
- <procedure id="proc-Administrator_Guide-Trapping_Massive_Amounts_of_Spam-Setting_a_Trap_for_Spam">
- <title>Setting a Trap for Spam</title>
- <step>
- <para>
- Set up the Cyrus IMAP postuser, using the <literal>postuser</literal> setting in <filename>/etc/imapd.conf</filename>.
- </para>
- <para>
- If, for example, the <literal>postuser</literal> is set to <literal>bb</literal>, the mail to <literal>bb+shared.blah</literal> will be delivered to the <literal>shared.blah</literal> folder.
- </para>
-
- </step>
- <step>
- <para>
- Create a folder such as <literal>shared/Spam</literal>
- </para>
-
- </step>
- <step>
- <para>
- Set permissions:
- </para>
- <para>
-
+ </para>
+ <note>
+ <para>
+ The total number of messages is about 2500. Learning about all of them may take quite a while. We recommend running the command in a screen.
+ </para>
+
+ </note>
+
+ </step>
+
+ </procedure>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Trapping_Massive_Amounts_of_Spam">
+ <title>Trapping Massive Amounts of Spam</title>
+ <para>
+ To learn about spam quickly, allow the Cyrus IMAP postuser to post into a shared folder that will be included in the regular <command>sa-learn</command> run.
+ </para>
+ <procedure id="proc-Administrator_Guide-Trapping_Massive_Amounts_of_Spam-Setting_a_Trap_for_Spam">
+ <title>Setting a Trap for Spam</title>
+ <step>
+ <para>
+ Set up the Cyrus IMAP postuser, using the <literal>postuser</literal> setting in <filename>/etc/imapd.conf</filename>.
+ </para>
+ <para>
+ If, for example, the <literal>postuser</literal> is set to <literal>bb</literal>, the mail to <literal>bb+shared.blah</literal> will be delivered to the <literal>shared.blah</literal> folder.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Create a folder such as <literal>shared/Spam</literal>
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Set permissions:
+ </para>
+ <para>
+
<screen>cyradm&gt; sam shared/Spam &lt;postuser&gt; p</screen>
- </para>
-
- </step>
- <step>
- <para>
- Submit / subscribe to known spam aggregators (search Google for "free email offers")
- </para>
-
- </step>
- <step>
- <para>
- Optionally, set the <literal>luser_relay</literal> option in Postfix, to trap all messages sent to non-existent recipients.
- </para>
-
- </step>
-
- </procedure>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Tweaking_Bayes_Scores">
- <title>Tweaking Bayes' Scores</title>
- <para>
- Bayes' score is dependent on the probability Bayes attaches of a message being spam. The rules used to match a message's probability of being spam are systematically prefixed with <literal>BAYES_</literal>, followed by the percentage of likelihood of the message being spam.
- </para>
- <para>
- Because there is rarely a 100% certainty of a message being spam, the highest percentage is 99%. By default, the configuration attaches a 3.5 score to this probability. Depending on the configuration value for <literal>$sa_tag2_level_deflt</literal> supplied in the Amavis configuration file, <literal>6.31</literal> by default, it is unlikely spam will reach the cut-off point of actually being marked as spam solely on the basis of Bayes' probability score.
- </para>
- <para>
- It is therefor recommended to increase the score attached to messages with a 99% probability of being spam to at least <literal>6.308</literal>, if not simply <literal>6.31</literal>. Using <literal>6.308</literal>, you configure spam to be tagged not solely on the basis of Bayes' 99% probability score, but request that in addition the message is recognized to be in HTML (and HTML only), and perhaps uses a big font &ndash;or similar patterns with a very small <literal>0.01</literal> score.
- </para>
- <para>
- Some spam has been submitted through systems listed at <ulink url="http://dnswl.org" />, a collaborative false positive protection mechanism, a default score of 1 is substracted from the total score. If this spam reaches you, consider increasing the score on <literal>BAYES_99</literal> with another one point.
- </para>
- <procedure id="proc-Administrator_Guide-Tweaking_Bayes_Scores-Adjusting_the_Score_for_BAYES_99">
- <title>Adjusting the Score for <literal>BAYES_99</literal></title>
- <step>
- <para>
- Edit <filename>/etc/mail/spamassassin/local.cf</filename>, and make sure the following line is present:
- </para>
- <para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Submit / subscribe to known spam aggregators (search Google for "free email offers")
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Optionally, set the <literal>luser_relay</literal> option in Postfix, to trap all messages sent to non-existent recipients.
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Tweaking_Bayes_Scores">
+ <title>Tweaking Bayes' Scores</title>
+ <para>
+ Bayes' score is dependent on the probability Bayes attaches of a message being spam. The rules used to match a message's probability of being spam are systematically prefixed with <literal>BAYES_</literal>, followed by the percentage of likelihood of the message being spam.
+ </para>
+ <para>
+ Because there is rarely a 100% certainty of a message being spam, the highest percentage is 99%. By default, the configuration attaches a 3.5 score to this probability. Depending on the configuration value for <literal>$sa_tag2_level_deflt</literal> supplied in the Amavis configuration file, <literal>6.31</literal> by default, it is unlikely spam will reach the cut-off point of actually being marked as spam solely on the basis of Bayes' probability score.
+ </para>
+ <para>
+ It is therefor recommended to increase the score attached to messages with a 99% probability of being spam to at least <literal>6.308</literal>, if not simply <literal>6.31</literal>. Using <literal>6.308</literal>, you configure spam to be tagged not solely on the basis of Bayes' 99% probability score, but request that in addition the message is recognized to be in HTML (and HTML only), and perhaps uses a big font &ndash;or similar patterns with a very small <literal>0.01</literal> score.
+ </para>
+ <para>
+ Some spam has been submitted through systems listed at <ulink url="http://dnswl.org" />, a collaborative false positive protection mechanism, a default score of 1 is substracted from the total score. If this spam reaches you, consider increasing the score on <literal>BAYES_99</literal> with another one point.
+ </para>
+ <procedure id="proc-Administrator_Guide-Tweaking_Bayes_Scores-Adjusting_the_Score_for_BAYES_99">
+ <title>Adjusting the Score for <literal>BAYES_99</literal></title>
+ <step>
+ <para>
+ Edit <filename>/etc/mail/spamassassin/local.cf</filename>, and make sure the following line is present:
+ </para>
+ <para>
+
<screen>score BAYES_99 7.308</screen>
- </para>
-
- </step>
- <step>
- <para>
- Reload or restart the <literal>amavisd-new</literal> service:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Reload or restart the <literal>amavisd-new</literal> service:
+ </para>
+ <para>
+
<screen># service amavisd-new restart</screen>
- </para>
-
- </step>
-
- </procedure>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Learning_about_Ham">
- <title>Learning about Ham</title>
- <para>
- It is important to not just learn about spam, but learn about ham, legitimate email messages, as well. When not learning about ham, the anti-spam system will become heavily biased towards spam, and ultimately classify all email messages as such.
- </para>
- <para>
- Learning about ham follows a slightly different doctrine then learning about spam. Most importantly, ham is not to be posted to a shared folder that everyone else can read the contents from. It is most commonly a "Not Junk" or "Ham" folder in one's personal namespace users are instructed to copy or move messages to, that have been classified as spam but are actually ham.
- </para>
- <para>
- It is recommended users are both instructed to use ham folders, as well as create them by default &mdash;regardless whether they are called "Ham" or "Not Junk" or equivalent localized version of such.
- </para>
- <para>
- Alternatively, you could learn about ham from people's INBOX folders.
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Expiring_Messages_from_SpamHam_Shared_Folders">
- <title>Expiring Messages from Spam/Ham (Shared) Folders</title>
- <para>
- When you share folders to which users can move or copy ham and/or spam messages, it is sensible to purge the contents of those folders regularly, or the folder size continues to increase indefinitely. Run the expiry after <command>sa-learn</command> has been run.
- </para>
- <note>
- <para>
- Running <command>ipurge</command> to purge mail folder messages occurs independent from setting <literal>expunge_mode</literal>, and independent from the <literal>expire</literal> annotation as well.
- </para>
- <para>
- Using the <literal>expire</literal> annotation is sufficient to purge the contents of the folder, as, with or without the <literal>expunge_mode</literal> setting having been set to delayed, rather then immediate, the Bayes database will only be updated with messages Bayes has not learned about before.
- </para>
-
- </note>
- <para>
- To purge the contents of a mailfolder, run ipurge:
- </para>
- <para>
-
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Learning_about_Ham">
+ <title>Learning about Ham</title>
+ <para>
+ It is important to not just learn about spam, but learn about ham, legitimate email messages, as well. When not learning about ham, the anti-spam system will become heavily biased towards spam, and ultimately classify all email messages as such.
+ </para>
+ <para>
+ Learning about ham follows a slightly different doctrine then learning about spam. Most importantly, ham is not to be posted to a shared folder that everyone else can read the contents from. It is most commonly a "Not Junk" or "Ham" folder in one's personal namespace users are instructed to copy or move messages to, that have been classified as spam but are actually ham.
+ </para>
+ <para>
+ It is recommended users are both instructed to use ham folders, as well as create them by default &mdash;regardless whether they are called "Ham" or "Not Junk" or equivalent localized version of such.
+ </para>
+ <para>
+ Alternatively, you could learn about ham from people's INBOX folders.
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Expiring_Messages_from_SpamHam_Shared_Folders">
+ <title>Expiring Messages from Spam/Ham (Shared) Folders</title>
+ <para>
+ When you share folders to which users can move or copy ham and/or spam messages, it is sensible to purge the contents of those folders regularly, or the folder size continues to increase indefinitely. Run the expiry after <command>sa-learn</command> has been run.
+ </para>
+ <note>
+ <para>
+ Running <command>ipurge</command> to purge mail folder messages occurs independent from setting <literal>expunge_mode</literal>, and independent from the <literal>expire</literal> annotation as well.
+ </para>
+ <para>
+ Using the <literal>expire</literal> annotation is sufficient to purge the contents of the folder, as, with or without the <literal>expunge_mode</literal> setting having been set to delayed, rather then immediate, the Bayes database will only be updated with messages Bayes has not learned about before.
+ </para>
+
+ </note>
+ <para>
+ To purge the contents of a mailfolder, run ipurge:
+ </para>
+ <para>
+
<screen>$ <userinput>/usr/lib/cyrus-imapd/ipurge -d 1 user/folder/name@domain.tld</userinput>
(...output abbreviated...)
$ <userinput>/usr/lib/cyrus-imapd/ipurge -i -d 1 user/folder/name@domain.tld</userinput></screen>
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Updating_the_Spam_Rules">
- <title>Updating the Spam Rules</title>
- <para>
- As part of the <application>SpamAssasin</application> package, a utility is provided to update the rulesets from channels configured.
- </para>
- <para>
- For systems on which either of the SpamAssassin daemon or Amavis daemon is running, the software packages automatically install a nightly cronjob to ensure the rules are updated frequently.
- </para>
- <para>
- The spam rulesets are updated using the <command>sa-update</command> command, supplying one or more <literal>--channel</literal> options specifying the names of the ruleset channels to update, and (optionally) one or more <literal>--gpgkey</literal> options specifying the Pretty Good Privacy keys to allow signatures on the rulesets to have been signed with.
- </para>
- <para>
- The cronjob that is installed by default, executes <command>sa-update</command> for all channels defined in <filename>/etc/mail/spamassassin/channels.d/</filename> with one file per channel.
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Bayes_SQL_Database_for_Distributed_Systems">
- <title>Bayes SQL Database for Distributed Systems</title>
- <para>
- If more then one system needs to make use of the Bayes database, consider using a network SQL Bayes database.
- </para>
- <procedure id="proc-Administrator_Guide-Bayes_SQL_Database_for_Distributed_Systems-Setting_Up_the_Bayes_Database">
- <title>Setting Up the Bayes Database</title>
- <step>
- <para>
- Create the database:
- </para>
- <para>
-
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Updating_the_Spam_Rules">
+ <title>Updating the Spam Rules</title>
+ <para>
+ As part of the <application>SpamAssasin</application> package, a utility is provided to update the rulesets from channels configured.
+ </para>
+ <para>
+ For systems on which either of the SpamAssassin daemon or Amavis daemon is running, the software packages automatically install a nightly cronjob to ensure the rules are updated frequently.
+ </para>
+ <para>
+ The spam rulesets are updated using the <command>sa-update</command> command, supplying one or more <literal>--channel</literal> options specifying the names of the ruleset channels to update, and (optionally) one or more <literal>--gpgkey</literal> options specifying the Pretty Good Privacy keys to allow signatures on the rulesets to have been signed with.
+ </para>
+ <para>
+ The cronjob that is installed by default, executes <command>sa-update</command> for all channels defined in <filename>/etc/mail/spamassassin/channels.d/</filename> with one file per channel.
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Bayes_SQL_Database_for_Distributed_Systems">
+ <title>Bayes SQL Database for Distributed Systems</title>
+ <para>
+ If more then one system needs to make use of the Bayes database, consider using a network SQL Bayes database.
+ </para>
+ <procedure id="proc-Administrator_Guide-Bayes_SQL_Database_for_Distributed_Systems-Setting_Up_the_Bayes_Database">
+ <title>Setting Up the Bayes Database</title>
+ <step>
+ <para>
+ Create the database:
+ </para>
+ <para>
+
<screen># mysql -e 'create database <emphasis>kolab_bayes</emphasis><footnote> <para>
- Replace with desired database name
- </para>
- </footnote>;'</screen>
-
- </para>
-
- </step>
- <step>
- <para>
- Create a user and grant the appropriate privileges:
- </para>
- <para>
-
+ Replace with desired database name
+ </para>
+ </footnote>;'</screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Create a user and grant the appropriate privileges:
+ </para>
+ <para>
+
<screen># mysql -e "CREATE USER '<emphasis>kolab_bayes</emphasis><footnote> <para>
- Replace with desired username
- </para>
- </footnote>'@'%' IDENTIFIED BY PASSWORD '<emphasis>Welcome2KolabSystems</emphasis><footnote> <para>
- Replace with desired password
- </para>
- </footnote>';"</screen>
-
- </para>
-
- </step>
- <step>
- <para>
- Grant the appropriate privileges:
- </para>
- <para>
-
+ Replace with desired username
+ </para>
+ </footnote>'@'%' IDENTIFIED BY PASSWORD '<emphasis>Welcome2KolabSystems</emphasis><footnote> <para>
+ Replace with desired password
+ </para>
+ </footnote>';"</screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Grant the appropriate privileges:
+ </para>
+ <para>
+
<screen># mysql -e "GRANT USAGE ON * . * TO '<emphasis>kolab_bayes</emphasis><footnote> <para>
- Replace with desired username
- </para>
- </footnote>'@'%' IDENTIFIED BY PASSWORD '<emphasis>Welcome2KolabSystems</emphasis><footnote> <para>
- Replace with desired password
- </para>
- </footnote>' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0;"
+ Replace with desired username
+ </para>
+ </footnote>'@'%' IDENTIFIED BY PASSWORD '<emphasis>Welcome2KolabSystems</emphasis><footnote> <para>
+ Replace with desired password
+ </para>
+ </footnote>' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0;"
# mysql -e "GRANT ALL PRIVILEGES on `<emphasis>kolab_bayes</emphasis><footnote> <para>
- Replace with desired database name
- </para>
- </footnote>` . * TO '<emphasis>kolab_bayes</emphasis><footnote> <para>
- Replace with desired username
- </para>
- </footnote>'@'%';"</screen>
-
- </para>
-
- </step>
- <step>
- <para>
- Reload the privileges:
- </para>
- <para>
-
+ Replace with desired database name
+ </para>
+ </footnote>` . * TO '<emphasis>kolab_bayes</emphasis><footnote> <para>
+ Replace with desired username
+ </para>
+ </footnote>'@'%';"</screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Reload the privileges:
+ </para>
+ <para>
+
<screen># mysql -e 'FLUSH PRIVILEGES;'</screen>
- </para>
-
- </step>
- <step>
- <para>
- Download the latest Bayes Database SQL schema file from <ulink url="http://svn.apache.org/repos/asf/spamassassin/trunk/sql/bayes_mysql.sql">bayes_mysql.sql</ulink> (when using MySQL):
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Download the latest Bayes Database SQL schema file from <ulink url="http://svn.apache.org/repos/asf/spamassassin/trunk/sql/bayes_mysql.sql">bayes_mysql.sql</ulink> (when using MySQL):
+ </para>
+ <para>
+
<screen># wget <ulink url="http://svn.apache.org/repos/asf/spamassassin/trunk/sql/bayes_mysql.sql" /></screen>
- </para>
-
- </step>
- <step>
- <para>
- Insert this schema into the database:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Insert this schema into the database:
+ </para>
+ <para>
+
<screen># mysql <emphasis>kolab_bayes</emphasis><footnote> <para>
- Replace with database name used.
- </para>
- </footnote> &lt; bayes_mysql.sql</screen>
-
- </para>
-
- </step>
-
- </procedure>
-
- <procedure id="proc-Administrator_Guide-Bayes_SQL_Database_for_Distributed_Systems-Migrating_Existing_Bayes_Databases">
- <title>Migrating Existing Bayes Database(s)</title>
- <step>
- <para>
- First, export any existing Bayes databases, run the following command (on each server with a Bayes database):
- </para>
- <para>
-
+ Replace with database name used.
+ </para>
+ </footnote> &lt; bayes_mysql.sql</screen>
+
+ </para>
+
+ </step>
+
+ </procedure>
+
+ <procedure id="proc-Administrator_Guide-Bayes_SQL_Database_for_Distributed_Systems-Migrating_Existing_Bayes_Databases">
+ <title>Migrating Existing Bayes Database(s)</title>
+ <step>
+ <para>
+ First, export any existing Bayes databases, run the following command (on each server with a Bayes database):
+ </para>
+ <para>
+
<screen># sa-learn --backup &gt; <filename>/path/to/sa_backup.txt</filename></screen>
- </para>
-
- </step>
- <step>
- <para>
- A recommended step, but completely optional, is to expire the current copy of the database:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ A recommended step, but completely optional, is to expire the current copy of the database:
+ </para>
+ <para>
+
<screen># sa-learn --clear</screen>
- </para>
-
- </step>
- <step>
- <para>
- Modify <filename>/etc/mail/spamassassin/local.cf</filename> to contain the following settings:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Modify <filename>/etc/mail/spamassassin/local.cf</filename> to contain the following settings:
+ </para>
+ <para>
+
<screen>bayes_store_module Mail::SpamAssassin::BayesStore::SQL
bayes_sql_dsn DBI:mysql:<emphasis>kolab_bayes</emphasis><footnote> <para>
- Replace with database name
- </para>
- </footnote>:<emphasis>mysql.domain.tld</emphasis><footnote> <para>
- Replace with MySQL server host address
- </para>
- </footnote>
+ Replace with database name
+ </para>
+ </footnote>:<emphasis>mysql.domain.tld</emphasis><footnote> <para>
+ Replace with MySQL server host address
+ </para>
+ </footnote>
bayes_sql_username <emphasis>kolab_bayes</emphasis><footnote> <para>
- Replace with the username for database access
- </para>
- </footnote>
+ Replace with the username for database access
+ </para>
+ </footnote>
bayes_sql_password <emphasis>Welcome2KolabSystems</emphasis><footnote> <para>
- Replace with the user password
- </para>
- </footnote>
+ Replace with the user password
+ </para>
+ </footnote>
bayes_sql_override_username root</screen>
- </para>
-
- </step>
- <step>
- <para>
- Import the exported Bayes database(s):
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Import the exported Bayes database(s):
+ </para>
+ <para>
+
<screen># sa-learn --restore <filename>/path/to/sa_backup.txt</filename></screen>
- </para>
-
- </step>
-
- </procedure>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Ensuring_Availability_of_Messages_Spam_Score">
- <title>Ensuring Availability of Messages' Spam Score</title>
- <para>
- For the purpose of troubleshooting, or in deployments with clients that have spam filtering capabilities, it is sensible to always insert the spam headers into email messages, both to avoid clients scanning the message again, as well as troubleshooting why mail may or may not have been filtered.
- </para>
- <para>
- To always insert the spam score into the message headers, find the line in <filename>/etc/amavisd/amavisd.conf</filename> that starts with <literal>$sa_tag_level_deflt</literal> and replace it with:
- </para>
- <para>
-
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Ensuring_Availability_of_Messages_Spam_Score">
+ <title>Ensuring Availability of Messages' Spam Score</title>
+ <para>
+ For the purpose of troubleshooting, or in deployments with clients that have spam filtering capabilities, it is sensible to always insert the spam headers into email messages, both to avoid clients scanning the message again, as well as troubleshooting why mail may or may not have been filtered.
+ </para>
+ <para>
+ To always insert the spam score into the message headers, find the line in <filename>/etc/amavisd/amavisd.conf</filename> that starts with <literal>$sa_tag_level_deflt</literal> and replace it with:
+ </para>
+ <para>
+
<screen>$sa_tag_level_deflt = -10;</screen>
- </para>
- <para>
- While the score is available from the log files should the level of logging verbosity have been increased, in some scenarios it is necessary to include the spam score regardless of the traffic being inbound or outbound. An example is a mail gateway for an unknown number of, or regularly changing, or dynamic, or large list of domain name spaces with both inbound and outbound traffic, which needs to be protected senders as well as receivers from spam.
- </para>
- <para>
- Normally only inbound traffic is tagged &ndash;if at all&ndash;, by recognizing the recipient domain name space as local. The setting <literal>@local_domains</literal> or, in later versions of Amavis, <literal>@local_domains_acl</literal> is used.
- </para>
- <para>
- In a default Kolab Groupware installation, the recipients are looked up in LDAP, and if an entry is found, Amavisd will also classify the domain as local &ndash; regardless of any <literal>@local_domains</literal> and/or <literal>@local_domains_acl</literal> setting.
- </para>
- <section id="sect-Administrator_Guide-Ensuring_Availability_of_Messages_Spam_Score-Adding_Spam_Headers_to_All_Messages">
- <title>Adding Spam Headers to All Messages</title>
- <para>
- To recognize all domain name spaces as local, edit <filename>/etc/amavisd/amavisd.conf</filename> and make sure the following settings are not configured:
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <literal>@local_domains</literal>,
- </para>
-
- </listitem>
- <listitem>
- <para>
- <literal>@local_domains_acl</literal>, and
- </para>
-
- </listitem>
- <listitem>
- <para>
- any <literal>read_hash(\%local_domains)</literal> setting.
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
- <para>
- Ensure that the following setting is configured like so:
- </para>
- <para>
-
+ </para>
+ <para>
+ While the score is available from the log files should the level of logging verbosity have been increased, in some scenarios it is necessary to include the spam score regardless of the traffic being inbound or outbound. An example is a mail gateway for an unknown number of, or regularly changing, or dynamic, or large list of domain name spaces with both inbound and outbound traffic, which needs to be protected senders as well as receivers from spam.
+ </para>
+ <para>
+ Normally only inbound traffic is tagged &ndash;if at all&ndash;, by recognizing the recipient domain name space as local. The setting <literal>@local_domains</literal> or, in later versions of Amavis, <literal>@local_domains_acl</literal> is used.
+ </para>
+ <para>
+ In a default Kolab Groupware installation, the recipients are looked up in LDAP, and if an entry is found, Amavisd will also classify the domain as local &ndash; regardless of any <literal>@local_domains</literal> and/or <literal>@local_domains_acl</literal> setting.
+ </para>
+ <section id="sect-Administrator_Guide-Ensuring_Availability_of_Messages_Spam_Score-Adding_Spam_Headers_to_All_Messages">
+ <title>Adding Spam Headers to All Messages</title>
+ <para>
+ To recognize all domain name spaces as local, edit <filename>/etc/amavisd/amavisd.conf</filename> and make sure the following settings are not configured:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>@local_domains</literal>,
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <literal>@local_domains_acl</literal>, and
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ any <literal>read_hash(\%local_domains)</literal> setting.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+ <para>
+ Ensure that the following setting is configured like so:
+ </para>
+ <para>
+
<screen language="Perl">$local_domains_re = new_RE( qr'.*' );</screen>
- </para>
- <para>
- Also disable the LDAP lookups, by removing the following settings:
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <literal>$enable_ldap</literal>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <literal>$default_ldap</literal>
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </section>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Default_Amavisd_Behaviour">
- <title>Default Amavisd Behaviour</title>
- <para>
- The default behaviour shown in a Kolab Groupware deployment depends on the default settings that come with the packages delivered mostly through native, distribution-specific software repositories. This chapter documents various aspects of the behaviour Kolab Groupware will show referring to the appropriate settings that will allow a system administrator to modify the behaviour.
- </para>
- <formalpara id="form-Administrator_Guide-Default_Amavisd_Behaviour-Adding_Spam_Information_Headers">
- <title>Adding Spam Information Headers</title>
- <para>
- Amavisd, by default, adds spam information headers only to messages that;
- </para>
-
- </formalpara>
- <para>
- <orderedlist>
- <listitem>
- <para>
- Are intended for delivery to local recipients,
- </para>
-
- </listitem>
- <listitem>
- <para>
- Get a spam score over <literal>2.0</literal> from <application>SpamAssassin</application>.
- </para>
- <para>
- The related setting is <literal>$sa_tag_level_deflt</literal> in <filename>/etc/amavisd/amavisd.conf</filename>.
- </para>
-
- </listitem>
-
- </orderedlist>
-
- </para>
- <formalpara id="form-Administrator_Guide-Default_Amavisd_Behaviour-Spam_Kill_Level">
- <title>Spam Kill Level</title>
- <para>
- The spam kill level controls which score spam must have been marked with before Amavisd considers the message to not be delivered to the intended recipient(s).
- </para>
-
- </formalpara>
- <para>
- Depending on your platform, the default for this score is <literal>6.31</literal> or <literal>6.9</literal>. When a message is marked with a spam score higher than or equal to this level, Amavisd will take "evasive action". See <xref linkend="sect-Administrator_Guide-Combating_Spam-Configuring_Amavis_Evasive_Action" /> for more information on configuring evasive actions.
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Combating_Spam-Configuring_Amavis_Evasive_Action">
- <title>Configuring Amavis Evasive Action</title>
- <para>
- You can control what "evasive action" Amavisd takes using the <literal>$final_spam_destiny</literal> and <literal>$final_virus_destiny</literal> settings in <filename>/etc/amavisd/amavisd.conf</filename>. The default is usually to discard the message, but the following options are available:
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-D_PASS">
- <title>D_PASS</title>
- <para>
- The message is accepted for delivery to the intended recipient(s), despite having been scored passed the kill or cutoff level, and regardless of bad content.
- </para>
-
- </formalpara>
- <para>
- If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
- </para>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-D_BOUNCE">
- <title>D_BOUNCE</title>
- <para>
- The message is not accepted for delivery to the intended recipient(s). A Delivery Status Notification stating delivery failure is sent out to the sender.
- </para>
-
- </formalpara>
- <para>
- If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
- </para>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-D_REJECT">
- <title>D_REJECT</title>
- <para>
- The message is rejected by Amavisd, and while Amavisd sends out a 550 SMTP response to the Mail Transfer Agent, said Mail Transfer Agent is responsible for sending out the Delivery Status Notification, if any.
- </para>
-
- </formalpara>
- <para>
- If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
- </para>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-D_DISCARD">
- <title>D_DISCARD</title>
- <para>
- The message is simply discarded by Amavisd. The sending Mail Transfer Agent will receive a positive SMTP delivery response, and Amavisd sends out no Delivery Status Notification, nor does it forward the message for delivery to the intended recipients.
- </para>
-
- </formalpara>
- <para>
- If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
- <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine">
- <title>Configuring Quarantine</title>
- <para>
- Two separate quarantine forwarding addresses can be configured. One is for messages labeled as spam, another for messages suspected to contain a virus.
- </para>
-
- </formalpara>
- <para>
- A catchall address for spam can be configured by setting the <literal>$spam_quarantine_to</literal> setting to a valid recipient address in <filename>/etc/amavisd/amavisd.conf</filename>
- </para>
- <para>
- A catchall address for messages suspected of containing a virus can be configured by setting the <literal>$virus_quarantine_to</literal> setting to a valid recipient address in <filename>/etc/amavisd/amavisd.conf</filename>.
- </para>
-
- </section>
-
+ </para>
+ <para>
+ Also disable the LDAP lookups, by removing the following settings:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>$enable_ldap</literal>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <literal>$default_ldap</literal>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </section>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Default_Amavisd_Behaviour">
+ <title>Default Amavisd Behaviour</title>
+ <para>
+ The default behaviour shown in a Kolab Groupware deployment depends on the default settings that come with the packages delivered mostly through native, distribution-specific software repositories. This chapter documents various aspects of the behaviour Kolab Groupware will show referring to the appropriate settings that will allow a system administrator to modify the behaviour.
+ </para>
+ <formalpara id="form-Administrator_Guide-Default_Amavisd_Behaviour-Adding_Spam_Information_Headers">
+ <title>Adding Spam Information Headers</title>
+ <para>
+ Amavisd, by default, adds spam information headers only to messages that;
+ </para>
+
+ </formalpara>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Are intended for delivery to local recipients,
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Get a spam score over <literal>2.0</literal> from <application>SpamAssassin</application>.
+ </para>
+ <para>
+ The related setting is <literal>$sa_tag_level_deflt</literal> in <filename>/etc/amavisd/amavisd.conf</filename>.
+ </para>
+
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+ <formalpara id="form-Administrator_Guide-Default_Amavisd_Behaviour-Spam_Kill_Level">
+ <title>Spam Kill Level</title>
+ <para>
+ The spam kill level controls which score spam must have been marked with before Amavisd considers the message to not be delivered to the intended recipient(s).
+ </para>
+
+ </formalpara>
+ <para>
+ Depending on your platform, the default for this score is <literal>6.31</literal> or <literal>6.9</literal>. When a message is marked with a spam score higher than or equal to this level, Amavisd will take "evasive action". See <xref linkend="sect-Administrator_Guide-Combating_Spam-Configuring_Amavis_Evasive_Action" /> for more information on configuring evasive actions.
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Combating_Spam-Configuring_Amavis_Evasive_Action">
+ <title>Configuring Amavis Evasive Action</title>
+ <para>
+ You can control what "evasive action" Amavisd takes using the <literal>$final_spam_destiny</literal> and <literal>$final_virus_destiny</literal> settings in <filename>/etc/amavisd/amavisd.conf</filename>. The default is usually to discard the message, but the following options are available:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-D_PASS">
+ <title>D_PASS</title>
+ <para>
+ The message is accepted for delivery to the intended recipient(s), despite having been scored passed the kill or cutoff level, and regardless of bad content.
+ </para>
+
+ </formalpara>
+ <para>
+ If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
+ </para>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-D_BOUNCE">
+ <title>D_BOUNCE</title>
+ <para>
+ The message is not accepted for delivery to the intended recipient(s). A Delivery Status Notification stating delivery failure is sent out to the sender.
+ </para>
+
+ </formalpara>
+ <para>
+ If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
+ </para>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-D_REJECT">
+ <title>D_REJECT</title>
+ <para>
+ The message is rejected by Amavisd, and while Amavisd sends out a 550 SMTP response to the Mail Transfer Agent, said Mail Transfer Agent is responsible for sending out the Delivery Status Notification, if any.
+ </para>
+
+ </formalpara>
+ <para>
+ If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
+ </para>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-D_DISCARD">
+ <title>D_DISCARD</title>
+ <para>
+ The message is simply discarded by Amavisd. The sending Mail Transfer Agent will receive a positive SMTP delivery response, and Amavisd sends out no Delivery Status Notification, nor does it forward the message for delivery to the intended recipients.
+ </para>
+
+ </formalpara>
+ <para>
+ If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+ <formalpara id="form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine">
+ <title>Configuring Quarantine</title>
+ <para>
+ Two separate quarantine forwarding addresses can be configured. One is for messages labeled as spam, another for messages suspected to contain a virus.
+ </para>
+
+ </formalpara>
+ <para>
+ A catchall address for spam can be configured by setting the <literal>$spam_quarantine_to</literal> setting to a valid recipient address in <filename>/etc/amavisd/amavisd.conf</filename>
+ </para>
+ <para>
+ A catchall address for messages suspected of containing a virus can be configured by setting the <literal>$virus_quarantine_to</literal> setting to a valid recipient address in <filename>/etc/amavisd/amavisd.conf</filename>.
+ </para>
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Configuring_the_Kolab_Server.xml b/Administrator_Guide/en-US/Configuring_the_Kolab_Server.xml
index ceee91b..96d86d6 100644
--- a/Administrator_Guide/en-US/Configuring_the_Kolab_Server.xml
+++ b/Administrator_Guide/en-US/Configuring_the_Kolab_Server.xml
@@ -4,104 +4,105 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Configuring_the_Kolab_Server">
- <title>Configuring the Kolab Server</title>
- <para>
- para
- </para>
- <section id="sect-Administrator_Guide-Configuring_the_Kolab_Server-Optimizing_the_Web_Server">
- <title>Optimizing the Web Server</title>
- <section id="sect-Administrator_Guide-Optimizing_the_Web_Server-Accelerating_PHP_with_APC">
- <title>Accelerating PHP with APC</title>
- <para>
- Web server performance is greatly improved by caching the interpreted bytecode for the PHP applications using the Alternative PHP Cache (APC) extension from PECL. With APC enabled, PHP source code is compiled only once (per retention interval), and subsequent inclusions for or execution of said PHP source code is obtained directly from cache.
- </para>
- <para>
- To enable APC, install the <application>php-pecl-apc</application> package:
- </para>
- <para>
-
+ <title>Configuring the Kolab Server</title>
+ <para>
+ This chapter outlines some of the most common Kolab Groupware configuration topics found in real life.
+ </para>
+ <xi:include href="sect-Kolab_Recipient_Policy_and_Web_Administration_Panel.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <section id="sect-Administrator_Guide-Configuring_the_Kolab_Server-Optimizing_the_Web_Server">
+ <title>Optimizing the Web Server</title>
+ <section id="sect-Administrator_Guide-Optimizing_the_Web_Server-Accelerating_PHP_with_APC">
+ <title>Accelerating PHP with APC</title>
+ <para>
+ Web server performance is greatly improved by caching the interpreted bytecode for the PHP applications using the Alternative PHP Cache (APC) extension from PECL. With APC enabled, PHP source code is compiled only once (per retention interval), and subsequent inclusions for or execution of said PHP source code is obtained directly from cache.
+ </para>
+ <para>
+ To enable APC, install the <application>php-pecl-apc</application> package:
+ </para>
+ <para>
+
<screen># <userinput>yum -y install php-pecl-apc</userinput></screen>
- </para>
- <para>
- Then, edit <filename>/etc/php.d/apc.ini</filename> and set or consider setting any of the following options;
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <formalpara id="form-Administrator_Guide-Accelerating_PHP_with_APC-apc.enabled1">
- <title><literal>apc.enabled=1</literal></title>
- <para>
- Enable APC (1), or disable APC (0)
- </para>
-
- </formalpara>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Accelerating_PHP_with_APC-apc.stat0">
- <title><literal>apc.stat=0</literal></title>
- <para>
- Issue a <literal>stat()</literal> call to see if the file with PHP source code has changed since the last binary compilation. Disabling the <literal>stat()</literal> call is recommended for production environments, as calling <literal>stat()</literal> includes a write call to update the file's last access time (atime). Note that the update write call for the last access time can be prevented by mounting the relevant filesystem with the <literal>noatime</literal> option.
- </para>
-
- </formalpara>
- <note>
- <title>Changes to PHP Source Code Files with APC <literal>stat()</literal> Disabled</title>
- <para>
- Note that when APC is configured to not issue a <literal>stat()</literal> call to see if a PHP source code file is changed, changes to PHP source code files will only be included in subsequent execution after the APC cache has been cleared. The APC cache is cleared upon web server service reload, restart or using the PHP call <literal>apc_clear_cache()</literal>.
- </para>
-
- </note>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Accelerating_PHP_with_APC-apc.stat_ctime1">
- <title><literal>apc.stat_ctime=1</literal></title>
- <para>
- When issuing a <literal>stat()</literal> call to see if the file with PHP source code has changed, use the file's change time attribute as opposed to the default, the file's modification time attribute.
- </para>
-
- </formalpara>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Accelerating_PHP_with_APC-apc.include_once_override0">
- <title><literal>apc.include_once_override=0</literal></title>
- <para>
- While overriding the expensive system calls issued during an <literal>include_once()</literal> or <literal>require_once()</literal> call be the PHP source code, this option MUST NOT be enabled. See <ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=113" /> for more information.
- </para>
-
- </formalpara>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </section>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Configuring_the_Kolab_Server-Using_the_Kolab_Perl_Libraries_on_a_non_Kolab_System">
- <title>Using the Kolab Perl Libraries on a non-Kolab System</title>
- <para>
- When using the <application>perl-Kolab</application> libraries on a system that is not a Kolab server itself, please be aware the perl-Kolab libraries expect and/or require certain settings to be available that are not really relevant for normal operations. This section explains which settings are expected and/or required, how to configure them and what the implications are.
- </para>
- <para>
- An example use-case scenario &ndash;to install and use the Kolab perl libraries on a system that is not a Kolab server&ndash; is, where user provisioning scripts are executed outside of Kolab, and require interfacing with Kolab's IMAP server components to manage user or shared mailboxes.
- </para>
- <formalpara id="form-Administrator_Guide-Using_the_Kolab_Perl_Libraries_on_a_non_Kolab_System-Recommended_Settings">
- <title>Recommended Settings</title>
- <para>
- The following is a snippet of the configuration file <filename>/etc/kolab/kolab.conf</filename> that prevents perl errors from being printed to <code>stderr</code>;
- </para>
-
- </formalpara>
- <para>
-
+ </para>
+ <para>
+ Then, edit <filename>/etc/php.d/apc.ini</filename> and set or consider setting any of the following options;
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Accelerating_PHP_with_APC-apc.enabled1">
+ <title><literal>apc.enabled=1</literal></title>
+ <para>
+ Enable APC (1), or disable APC (0)
+ </para>
+
+ </formalpara>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Accelerating_PHP_with_APC-apc.stat0">
+ <title><literal>apc.stat=0</literal></title>
+ <para>
+ Issue a <literal>stat()</literal> call to see if the file with PHP source code has changed since the last binary compilation. Disabling the <literal>stat()</literal> call is recommended for production environments, as calling <literal>stat()</literal> includes a write call to update the file's last access time (atime). Note that the update write call for the last access time can be prevented by mounting the relevant filesystem with the <literal>noatime</literal> option.
+ </para>
+
+ </formalpara>
+ <note>
+ <title>Changes to PHP Source Code Files with APC <literal>stat()</literal> Disabled</title>
+ <para>
+ Note that when APC is configured to not issue a <literal>stat()</literal> call to see if a PHP source code file is changed, changes to PHP source code files will only be included in subsequent execution after the APC cache has been cleared. The APC cache is cleared upon web server service reload, restart or using the PHP call <literal>apc_clear_cache()</literal>.
+ </para>
+
+ </note>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Accelerating_PHP_with_APC-apc.stat_ctime1">
+ <title><literal>apc.stat_ctime=1</literal></title>
+ <para>
+ When issuing a <literal>stat()</literal> call to see if the file with PHP source code has changed, use the file's change time attribute as opposed to the default, the file's modification time attribute.
+ </para>
+
+ </formalpara>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Accelerating_PHP_with_APC-apc.include_once_override0">
+ <title><literal>apc.include_once_override=0</literal></title>
+ <para>
+ While overriding the expensive system calls issued during an <literal>include_once()</literal> or <literal>require_once()</literal> call be the PHP source code, this option MUST NOT be enabled. See <ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=113" /> for more information.
+ </para>
+
+ </formalpara>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </section>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Configuring_the_Kolab_Server-Using_the_Kolab_Perl_Libraries_on_a_non_Kolab_System">
+ <title>Using the Kolab Perl Libraries on a non-Kolab System</title>
+ <para>
+ When using the <application>perl-Kolab</application> libraries on a system that is not a Kolab server itself, please be aware the perl-Kolab libraries expect and/or require certain settings to be available that are not really relevant for normal operations. This section explains which settings are expected and/or required, how to configure them and what the implications are.
+ </para>
+ <para>
+ An example use-case scenario &ndash;to install and use the Kolab perl libraries on a system that is not a Kolab server&ndash; is, where user provisioning scripts are executed outside of Kolab, and require interfacing with Kolab's IMAP server components to manage user or shared mailboxes.
+ </para>
+ <formalpara id="form-Administrator_Guide-Using_the_Kolab_Perl_Libraries_on_a_non_Kolab_System-Recommended_Settings">
+ <title>Recommended Settings</title>
+ <para>
+ The following is a snippet of the configuration file <filename>/etc/kolab/kolab.conf</filename> that prevents perl errors from being printed to <code>stderr</code>;
+ </para>
+
+ </formalpara>
+ <para>
+
<screen>kolab_usr: kolab
kolab_musr: kolab
kolab_rusr: kolab
@@ -109,42 +110,42 @@ kolab_grp: kolab
kolab_mgrp: kolab
kolab_rgrp: kolab</screen>
- </para>
- <para>
- In a traditional Kolab deployment, these settings are used with the configuration management utilities. On a server that is not a Kolab server, naturally the configuration management does not apply. However, the Kolab perl libraries still require these settings to be available for errors to be suppressed.
- </para>
- <para>
- Please see <ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=114" /> for more information.
- </para>
- <formalpara id="form-Administrator_Guide-Using_the_Kolab_Perl_Libraries_on_a_non_Kolab_System-Required_Settings">
- <title>Required Settings</title>
- <para>
- The following are settings required;
- </para>
-
- </formalpara>
- <para>
- <itemizedlist>
- <listitem>
- <formalpara id="form-Administrator_Guide-Using_the_Kolab_Perl_Libraries_on_a_non_Kolab_System-connect_addr">
- <title><literal>connect_addr</literal></title>
- <para>
- The connection address for the Kolab perl libraries. Currently this is being used for IMAP connections.
- </para>
-
- </formalpara>
- <para>
- See <ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=112">Bugzilla #112: <emphasis>Use of connect_addr, local_addr, bind_addr and bind_any</emphasis></ulink> and <ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=115">Bugzilla #115: <emphasis>NEW</emphasis></ulink> for more information.
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </section>
-
+ </para>
+ <para>
+ In a traditional Kolab deployment, these settings are used with the configuration management utilities. On a server that is not a Kolab server, naturally the configuration management does not apply. However, the Kolab perl libraries still require these settings to be available for errors to be suppressed.
+ </para>
+ <para>
+ Please see <ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=114" /> for more information.
+ </para>
+ <formalpara id="form-Administrator_Guide-Using_the_Kolab_Perl_Libraries_on_a_non_Kolab_System-Required_Settings">
+ <title>Required Settings</title>
+ <para>
+ The following are settings required;
+ </para>
+
+ </formalpara>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Using_the_Kolab_Perl_Libraries_on_a_non_Kolab_System-connect_addr">
+ <title><literal>connect_addr</literal></title>
+ <para>
+ The connection address for the Kolab perl libraries. Currently this is being used for IMAP connections.
+ </para>
+
+ </formalpara>
+ <para>
+ See <ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=112">Bugzilla #112: <emphasis>Use of connect_addr, local_addr, bind_addr and bind_any</emphasis></ulink> and <ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=115">Bugzilla #115: <emphasis>NEW</emphasis></ulink> for more information.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Detailed_Kolab_Server_Overview.xml b/Administrator_Guide/en-US/Detailed_Kolab_Server_Overview.xml
index 1d80c8d..96c79bb 100755
--- a/Administrator_Guide/en-US/Detailed_Kolab_Server_Overview.xml
+++ b/Administrator_Guide/en-US/Detailed_Kolab_Server_Overview.xml
@@ -4,394 +4,394 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Detailed_Kolab_Server_Overview">
- <title>Detailed Kolab Server Overview</title>
- <para>
- The Kolab Server consists of various 3rd-party OpenSource components as well as some kolab specific components which provide the glue between those. Most of the 3rd-party components can be exchanged, such as the IMAP-Server.
- </para>
- <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-EMail_Directory_Service">
- <title>EMail-/Directory-Service</title>
- <section id="sect-Administrator_Guide-EMail_Directory_Service-Postfix">
- <title>Postfix</title>
- <para>
- Postfix is an <emphasis>MTA</emphasis> (Mail Transfer Agent), responsible for the transport and distribution of emails.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- URL: <ulink url="http://www.postfix.org">www.postfix.org</ulink>
- </para>
-
- </listitem>
- <listitem>
- <para>
- Documentation: <ulink url="http://www.postfix.org/documentation.html">Postfix Documentation</ulink>
- </para>
-
- </listitem>
-
- </itemizedlist>
- <formalpara id="form-Administrator_Guide-Postfix-Services">
- <title>Services:</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <application>postfix</application>
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </formalpara>
- <formalpara id="form-Administrator_Guide-Postfix-Configuration_files">
- <title>Configuration files:</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <filename>/etc/postfix/main.cf</filename>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <filename>/etc/postfix/master.cf</filename>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <filename>/etc/postfix/ldap/alias_maps.cf</filename>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <filename>/etc/postfix/ldap/local_recipient_maps.cf</filename>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <filename>/etc/postfix/ldap/mydestination.cf</filename>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <filename>/etc/postfix/ldap/virtual_alias_maps.cf</filename>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <filename>/etc/postfix/ldap/virtual_alias_maps_mailenabled_distgroups.cf</filename>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <filename>/etc/postfix/ldap/virtual_alias_maps_mailenabled_dynamic_distgroups.cf</filename>
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </formalpara>
- <formalpara id="form-Administrator_Guide-Postfix-Logfiles">
- <title>Logfiles</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <filename>/var/log/logfile</filename>
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </formalpara>
- <formalpara id="form-Administrator_Guide-Postfix-Commands">
- <title>Commands</title>
- <para>
- /etc/init.d/postfix restart
- </para>
-
- </formalpara>
-
- </section>
-
- <section id="sect-Administrator_Guide-EMail_Directory_Service-Cyrus_IMAP">
- <title>Cyrus-IMAP</title>
- <para>
- The <application>Cyrus-IMAP</application> server is a scalable, fast IMAP server.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- URL: <ulink url="http://www.cyrusimap.org/">www.cyrusimap.org/</ulink>
- </para>
-
- </listitem>
- <listitem>
- <para>
- Documentation: <ulink url="http://www.cyrusimap.org/docs/cyrus-imapd/">Cyrus Documentation</ulink>
- </para>
-
- </listitem>
-
- </itemizedlist>
- <formalpara id="form-Administrator_Guide-Cyrus_IMAP-Services">
- <title>Services:</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <application>imapd</application>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <application>pop3d TODO: remove?</application>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <application>/usr/lib/cyrus-impad/cyrus-master</application>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <application>idled</application>
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </formalpara>
-
- </section>
-
- <section id="sect-Administrator_Guide-EMail_Directory_Service-OpenLDAP">
- <title>OpenLDAP</title>
- <para>
- LDAP is the directory services used to store information about users as well as parts of the Kolab configuration. The service consists of the <application>slapd</application> deamon, which provides access to the directory. <application>slurpd</application> is a replication deamon for the LDAP database, allowing the system to be distributed over several machines which increases relaiability as well as availability. <application>slurpd</application> is replaced by <application>syncrepl</application> as of version 3.0.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- URL: <ulink url="http://www.openldap.org/">www.openldap.org/</ulink>
- </para>
-
- </listitem>
- <listitem>
- <para>
- Documentation: <ulink url="http://www.openldap.org/doc/admin24/">OpenLDAP admin guide</ulink>
- </para>
-
- </listitem>
-
- </itemizedlist>
- <formalpara id="form-Administrator_Guide-OpenLDAP-Services">
- <title>Services:</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <application>slapd</application>
- </para>
-
- </listitem>
- <listitem>
- <para>
- <application>slurpd</application>
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </formalpara>
-
- </section>
-
- <section id="sect-Administrator_Guide-EMail_Directory_Service-Cyrus_SASL_authentication">
- <title>Cyrus-SASL authentication</title>
- <para>
- SASL (Simple Authentication and Security Layer) is a method to add authentication support for connection based protocols. The authentication via SASL is used by Postfix and the IMAP-Server. <application>saslauthd</application> is the deamon providing the authentication, using the credentials stored in the LDAP database.
- </para>
- <formalpara id="form-Administrator_Guide-Cyrus_SASL_authentication-Services">
- <title>Services:</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <application>/usr/sbin/saslauthd</application>
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </formalpara>
-
- </section>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-Spam_Virus_Scanner">
- <title>Spam-/Virus-Scanner</title>
- <section id="sect-Administrator_Guide-Spam_Virus_Scanner-Amavisd">
- <title>Amavisd</title>
- <para>
- <application>Amavisd</application> is an emailscanner, which unpacks all messages (including attachments) and forwards them to virus scanners and spam filters.
- </para>
- <formalpara id="form-Administrator_Guide-Amavisd-Services">
- <title>Services:</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <application>amavisd</application>
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </formalpara>
-
- </section>
-
- <section id="sect-Administrator_Guide-Spam_Virus_Scanner-ClamAV">
- <title>ClamAV</title>
- <para>
- <application>ClamAV</application> is a virus scanner, suitable for Mailservers.
- </para>
- <para>
- <application>clamd.amavisd</application>
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Spam_Virus_Scanner-SpamAssassin">
- <title>SpamAssassin</title>
- <para>
- <application>SpamAssassin</application> is a spam filter.
- </para>
-
- </section>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-Kolab_Webclient">
- <title>Kolab-Webclient</title>
- <section id="sect-Administrator_Guide-Kolab_Webclient-Horde">
- <title>Horde</title>
- <para>
- <application>Horde</application> is the old webclient for Kolab.
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Kolab_Webclient-Roundcube">
- <title>Roundcube</title>
- <para>
- <application>Roundcube</application> is the new webclient for Kolab.
- </para>
-
- </section>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-General">
- <title>General</title>
- <section id="sect-Administrator_Guide-General-Apache">
- <title>Apache</title>
- <para>
- The infamous http server.
- </para>
- <formalpara id="form-Administrator_Guide-Apache-Services">
- <title>Services:</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <application>/usr/sbin/httpd</application>
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </formalpara>
-
- </section>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-Kolab_specific_Components">
- <title>Kolab specific Components</title>
- <para>
- Apart from the main components, consisting of proven 3rd-party OpenSource software, there are also some Kolab specific software components.
- </para>
- <section id="sect-Administrator_Guide-Kolab_specific_Components-kolabd">
- <title>kolabd</title>
- <para>
- The Kolab-Daemon is the central control unit between the various components. It is responsible for synchronizing the user accounts in the LDAP directory with the available IMAP folders. TODO: further responsabilites of kolabd
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Kolab_specific_Components-kolab_webadmin">
- <title>kolab-webadmin</title>
- <para>
- The Kolab-Webadin is an administrator webinterface.
- </para>
-
- </section>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-Component_Interaction">
- <title>Component Interaction</title>
- <para>
- The following diagram illustrates the interaction between the various components.
- </para>
- <para>
- <application>kolabd</application> is the central control instance of the kolab server, responsible to configure all components,
- </para>
-
- </section>
-
+ <title>Detailed Kolab Server Overview</title>
+ <para>
+ The Kolab Server consists of various 3rd-party OpenSource components as well as some kolab specific components which provide the glue between those. Most of the 3rd-party components can be exchanged, such as the IMAP-Server.
+ </para>
+ <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-EMail_Directory_Service">
+ <title>EMail-/Directory-Service</title>
+ <section id="sect-Administrator_Guide-EMail_Directory_Service-Postfix">
+ <title>Postfix</title>
+ <para>
+ Postfix is an <emphasis>MTA</emphasis> (Mail Transfer Agent), responsible for the transport and distribution of emails.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ URL: <ulink url="http://www.postfix.org">www.postfix.org</ulink>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Documentation: <ulink url="http://www.postfix.org/documentation.html">Postfix Documentation</ulink>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <formalpara id="form-Administrator_Guide-Postfix-Services">
+ <title>Services:</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <application>postfix</application>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </formalpara>
+ <formalpara id="form-Administrator_Guide-Postfix-Configuration_files">
+ <title>Configuration files:</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>/etc/postfix/main.cf</filename>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <filename>/etc/postfix/master.cf</filename>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <filename>/etc/postfix/ldap/alias_maps.cf</filename>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <filename>/etc/postfix/ldap/local_recipient_maps.cf</filename>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <filename>/etc/postfix/ldap/mydestination.cf</filename>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <filename>/etc/postfix/ldap/virtual_alias_maps.cf</filename>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <filename>/etc/postfix/ldap/virtual_alias_maps_mailenabled_distgroups.cf</filename>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <filename>/etc/postfix/ldap/virtual_alias_maps_mailenabled_dynamic_distgroups.cf</filename>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </formalpara>
+ <formalpara id="form-Administrator_Guide-Postfix-Logfiles">
+ <title>Logfiles</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>/var/log/logfile</filename>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </formalpara>
+ <formalpara id="form-Administrator_Guide-Postfix-Commands">
+ <title>Commands</title>
+ <para>
+ /etc/init.d/postfix restart
+ </para>
+
+ </formalpara>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-EMail_Directory_Service-Cyrus_IMAP">
+ <title>Cyrus-IMAP</title>
+ <para>
+ The <application>Cyrus-IMAP</application> server is a scalable, fast IMAP server.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ URL: <ulink url="http://www.cyrusimap.org/">www.cyrusimap.org/</ulink>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Documentation: <ulink url="http://www.cyrusimap.org/docs/cyrus-imapd/">Cyrus Documentation</ulink>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <formalpara id="form-Administrator_Guide-Cyrus_IMAP-Services">
+ <title>Services:</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <application>imapd</application>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <application>pop3d TODO: remove?</application>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <application>/usr/lib/cyrus-impad/cyrus-master</application>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <application>idled</application>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </formalpara>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-EMail_Directory_Service-OpenLDAP">
+ <title>OpenLDAP</title>
+ <para>
+ LDAP is the directory services used to store information about users as well as parts of the Kolab configuration. The service consists of the <application>slapd</application> deamon, which provides access to the directory. <application>slurpd</application> is a replication deamon for the LDAP database, allowing the system to be distributed over several machines which increases relaiability as well as availability. <application>slurpd</application> is replaced by <application>syncrepl</application> as of version 3.0.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ URL: <ulink url="http://www.openldap.org/">www.openldap.org/</ulink>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Documentation: <ulink url="http://www.openldap.org/doc/admin24/">OpenLDAP admin guide</ulink>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <formalpara id="form-Administrator_Guide-OpenLDAP-Services">
+ <title>Services:</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <application>slapd</application>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <application>slurpd</application>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </formalpara>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-EMail_Directory_Service-Cyrus_SASL_authentication">
+ <title>Cyrus-SASL authentication</title>
+ <para>
+ SASL (Simple Authentication and Security Layer) is a method to add authentication support for connection based protocols. The authentication via SASL is used by Postfix and the IMAP-Server. <application>saslauthd</application> is the deamon providing the authentication, using the credentials stored in the LDAP database.
+ </para>
+ <formalpara id="form-Administrator_Guide-Cyrus_SASL_authentication-Services">
+ <title>Services:</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <application>/usr/sbin/saslauthd</application>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </formalpara>
+
+ </section>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-Spam_Virus_Scanner">
+ <title>Spam-/Virus-Scanner</title>
+ <section id="sect-Administrator_Guide-Spam_Virus_Scanner-Amavisd">
+ <title>Amavisd</title>
+ <para>
+ <application>Amavisd</application> is an emailscanner, which unpacks all messages (including attachments) and forwards them to virus scanners and spam filters.
+ </para>
+ <formalpara id="form-Administrator_Guide-Amavisd-Services">
+ <title>Services:</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <application>amavisd</application>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </formalpara>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Spam_Virus_Scanner-ClamAV">
+ <title>ClamAV</title>
+ <para>
+ <application>ClamAV</application> is a virus scanner, suitable for Mailservers.
+ </para>
+ <para>
+ <application>clamd.amavisd</application>
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Spam_Virus_Scanner-SpamAssassin">
+ <title>SpamAssassin</title>
+ <para>
+ <application>SpamAssassin</application> is a spam filter.
+ </para>
+
+ </section>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-Kolab_Webclient">
+ <title>Kolab-Webclient</title>
+ <section id="sect-Administrator_Guide-Kolab_Webclient-Horde">
+ <title>Horde</title>
+ <para>
+ <application>Horde</application> is the old webclient for Kolab.
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Kolab_Webclient-Roundcube">
+ <title>Roundcube</title>
+ <para>
+ <application>Roundcube</application> is the new webclient for Kolab.
+ </para>
+
+ </section>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-General">
+ <title>General</title>
+ <section id="sect-Administrator_Guide-General-Apache">
+ <title>Apache</title>
+ <para>
+ The infamous http server.
+ </para>
+ <formalpara id="form-Administrator_Guide-Apache-Services">
+ <title>Services:</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <application>/usr/sbin/httpd</application>
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </formalpara>
+
+ </section>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-Kolab_specific_Components">
+ <title>Kolab specific Components</title>
+ <para>
+ Apart from the main components, consisting of proven 3rd-party OpenSource software, there are also some Kolab specific software components.
+ </para>
+ <section id="sect-Administrator_Guide-Kolab_specific_Components-kolabd">
+ <title>kolabd</title>
+ <para>
+ The Kolab-Daemon is the central control unit between the various components. It is responsible for synchronizing the user accounts in the LDAP directory with the available IMAP folders. TODO: further responsabilites of kolabd
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Kolab_specific_Components-kolab_webadmin">
+ <title>kolab-webadmin</title>
+ <para>
+ The Kolab-Webadin is an administrator webinterface.
+ </para>
+
+ </section>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Detailed_Kolab_Server_Overview-Component_Interaction">
+ <title>Component Interaction</title>
+ <para>
+ The following diagram illustrates the interaction between the various components.
+ </para>
+ <para>
+ <application>kolabd</application> is the central control instance of the kolab server, responsible to configure all components,
+ </para>
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Kolab_Web_Administration_Panel.xml b/Administrator_Guide/en-US/Kolab_Web_Administration_Panel.xml
index ce52972..de3bce3 100644
--- a/Administrator_Guide/en-US/Kolab_Web_Administration_Panel.xml
+++ b/Administrator_Guide/en-US/Kolab_Web_Administration_Panel.xml
@@ -4,182 +4,182 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Kolab_Web_Administration_Panel">
- <title>Kolab Web Administration Panel</title>
- <section id="sect-Administrator_Guide-Kolab_Web_Administration_Panel-Editing_user_types">
- <title>Editing <literal>user_types</literal></title>
- <para>
- The <literal>user_types</literal> table in the MySQL <literal>kolab</literal> database contains the following columns:
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <formalpara id="form-Administrator_Guide-Editing_user_types-id">
- <title>id</title>
- <para>
- A unique ID.
- </para>
-
- </formalpara>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Editing_user_types-key">
- <title>key</title>
- <para>
- A machine-readable key identifying the user type.
- </para>
-
- </formalpara>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Editing_user_types-name">
- <title>name</title>
- <para>
- A human-readable name.
- </para>
-
- </formalpara>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Editing_user_types-description">
- <title>description</title>
- <para>
- A description of the user type.
- </para>
-
- </formalpara>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Editing_user_types-attributes">
- <title>attributes</title>
- <para>
- The actual settings. Please see <xref linkend="sect-Administrator_Guide-Editing_user_types-Attributes_Reference" /> for a full reference, and <xref linkend="proc-Administrator_Guide-Editing_user_types-Manually_Changing_the_user_types_Available" /> for the procedure to edit these settings manually.
- </para>
-
- </formalpara>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
- <procedure id="proc-Administrator_Guide-Editing_user_types-Manually_Changing_the_user_types_Available">
- <title>Manually Changing the <literal>user_types</literal> Available</title>
- <step>
- <para>
- Sample scripts are provided as part of the <application>kolab-webadmin</application> package. Use the following command to locate these scripts, called <emphasis>sample-insert-user_types.php</emphasis>;
- </para>
- <para>
-
+ <title>Kolab Web Administration Panel</title>
+ <section id="sect-Administrator_Guide-Kolab_Web_Administration_Panel-Editing_user_types">
+ <title>Editing <literal>user_types</literal></title>
+ <para>
+ The <literal>user_types</literal> table in the MySQL <literal>kolab</literal> database contains the following columns:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Editing_user_types-id">
+ <title>id</title>
+ <para>
+ A unique ID.
+ </para>
+
+ </formalpara>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Editing_user_types-key">
+ <title>key</title>
+ <para>
+ A machine-readable key identifying the user type.
+ </para>
+
+ </formalpara>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Editing_user_types-name">
+ <title>name</title>
+ <para>
+ A human-readable name.
+ </para>
+
+ </formalpara>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Editing_user_types-description">
+ <title>description</title>
+ <para>
+ A description of the user type.
+ </para>
+
+ </formalpara>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Editing_user_types-attributes">
+ <title>attributes</title>
+ <para>
+ The actual settings. Please see <xref linkend="sect-Administrator_Guide-Editing_user_types-Attributes_Reference" /> for a full reference, and <xref linkend="proc-Administrator_Guide-Editing_user_types-Manually_Changing_the_user_types_Available" /> for the procedure to edit these settings manually.
+ </para>
+
+ </formalpara>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+ <procedure id="proc-Administrator_Guide-Editing_user_types-Manually_Changing_the_user_types_Available">
+ <title>Manually Changing the <literal>user_types</literal> Available</title>
+ <step>
+ <para>
+ Sample scripts are provided as part of the <application>kolab-webadmin</application> package. Use the following command to locate these scripts, called <emphasis>sample-insert-user_types.php</emphasis>;
+ </para>
+ <para>
+
<screen># <userinput>rpm -qld kolab-webadmin</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Copy the relevant example file to one directory above the <filename>public_html/</filename> directory, like so:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Copy the relevant example file to one directory above the <filename>public_html/</filename> directory, like so:
+ </para>
+ <para>
+
<screen># <userinput>cp -a /path/to/sample-insert-user_types.php \</userinput>
<userinput>/usr/share/kolab-webadmin/insert-user_types.php</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Edit the file to reflect your needs. For example, to avoid the <literal>mail</literal> attribute from being automatically generated, remove <literal>$attributes['auto_form_fields']['mail']</literal>.
- </para>
-
- </step>
- <step>
- <para>
- You may want to insert <literal>$attributes["form_fields"]["mail"]</literal> to insert back a form field that allows supplying a mail attribute value for the user type.
- </para>
-
- </step>
- <step>
- <para>
- Once done editing, check the syntax;
- </para>
- <para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Edit the file to reflect your needs. For example, to avoid the <literal>mail</literal> attribute from being automatically generated, remove <literal>$attributes['auto_form_fields']['mail']</literal>.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ You may want to insert <literal>$attributes["form_fields"]["mail"]</literal> to insert back a form field that allows supplying a mail attribute value for the user type.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Once done editing, check the syntax;
+ </para>
+ <para>
+
<screen># <userinput>php -l insert-user_types.php</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Execute the file to replace the user types currently in the database;
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Execute the file to replace the user types currently in the database;
+ </para>
+ <para>
+
<screen># <userinput>php insert-user_types.php</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Log out and log back in to the web admin.
- </para>
-
- </step>
-
- </procedure>
-
- <section id="sect-Administrator_Guide-Editing_user_types-Attributes_Reference">
- <title>Attributes Reference</title>
- <para>
- The attributes column for user types describes which form fields are to be offered to the <emphasis>add user</emphasis> dialog for each type of user available.
- </para>
- <para>
- It is an object consisting of three types of form fields, namely;
- </para>
- <para>
- <orderedlist>
- <listitem>
- <para>
- <literal>auto_form_fields</literal>, or form fields for which the value is generated automatically (from values that are entered in other form fields).
- </para>
- <para>
- Example form fields for which the value can be generated automatically include <literal>displayname</literal> and <literal>cn</literal>.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <literal>form_fields</literal>, for form fields to which the user or administrator is to provide input.
- </para>
- <para>
- Example form fields that users or administrators would provide input to include <literal>givenname</literal> and <literal>surname</literal>.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <literal>fields</literal>, for form fields that are hidden from plain sight, and cannot be edited by the user or administrator.
- </para>
- <para>
- Example fields that would be configured as immutable, or static, and therefore be hidden from the client interface include <literal>objectclass</literal>.
- </para>
-
- </listitem>
-
- </orderedlist>
-
- </para>
- <para>
- The structure of the <literal>attributes</literal> attribute value is:
- </para>
- <para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Log out and log back in to the web admin.
+ </para>
+
+ </step>
+
+ </procedure>
+
+ <section id="sect-Administrator_Guide-Editing_user_types-Attributes_Reference">
+ <title>Attributes Reference</title>
+ <para>
+ The attributes column for user types describes which form fields are to be offered to the <emphasis>add user</emphasis> dialog for each type of user available.
+ </para>
+ <para>
+ It is an object consisting of three types of form fields, namely;
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ <literal>auto_form_fields</literal>, or form fields for which the value is generated automatically (from values that are entered in other form fields).
+ </para>
+ <para>
+ Example form fields for which the value can be generated automatically include <literal>displayname</literal> and <literal>cn</literal>.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <literal>form_fields</literal>, for form fields to which the user or administrator is to provide input.
+ </para>
+ <para>
+ Example form fields that users or administrators would provide input to include <literal>givenname</literal> and <literal>surname</literal>.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <literal>fields</literal>, for form fields that are hidden from plain sight, and cannot be edited by the user or administrator.
+ </para>
+ <para>
+ Example fields that would be configured as immutable, or static, and therefore be hidden from the client interface include <literal>objectclass</literal>.
+ </para>
+
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+ <para>
+ The structure of the <literal>attributes</literal> attribute value is:
+ </para>
+ <para>
+
<screen language="PHP/PHP">Array(
"&lt;form_field_type&gt;" =&gt; Array(
"&lt;form_field_name&gt;" =&gt; Array(
@@ -198,39 +198,39 @@
)
)</screen>
- </para>
- <para>
- The <literal>attributes</literal> attribute to a <literal>user_type</literal> entry holds an array with any or all of the following <emphasis>&lt;form_field_type&gt;</emphasis> keys:
- </para>
- <important>
- <para>
- The reference implementation and general rule of thumb is to use the LDAP attribute name as the form field name.
- </para>
-
- </important>
- <para>
- <itemizedlist>
- <listitem>
- <formalpara id="form-Administrator_Guide-Attributes_Reference-auto_form_fields">
- <title><literal>auto_form_fields</literal></title>
- <para>
- The <literal>auto_form_fields</literal> key holds an array of form fields that correspond with attributes for which the value is to be generated automatically, using an API call.
- </para>
-
- </formalpara>
- <para>
- The key name for each key =&gt; value pair indicates the form field name for which the value is to be generated automatically.
- </para>
- <para>
- Each array key corresponds with a user attribute name, and it's value is an array containing the name of the form fields for which the value to submit as part of the API call.
- </para>
- <example id="exam-Administrator_Guide-Attributes_Reference-A_Users_displayname">
- <title>A User's <literal>displayname</literal></title>
- <para>
- Provided the user type's <literal>auto_form_fields</literal> contains an array key of <literal>displayname</literal>, the array value for this key could look as follows:
- </para>
- <para>
-
+ </para>
+ <para>
+ The <literal>attributes</literal> attribute to a <literal>user_type</literal> entry holds an array with any or all of the following <emphasis>&lt;form_field_type&gt;</emphasis> keys:
+ </para>
+ <important>
+ <para>
+ The reference implementation and general rule of thumb is to use the LDAP attribute name as the form field name.
+ </para>
+
+ </important>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Attributes_Reference-auto_form_fields">
+ <title><literal>auto_form_fields</literal></title>
+ <para>
+ The <literal>auto_form_fields</literal> key holds an array of form fields that correspond with attributes for which the value is to be generated automatically, using an API call.
+ </para>
+
+ </formalpara>
+ <para>
+ The key name for each key =&gt; value pair indicates the form field name for which the value is to be generated automatically.
+ </para>
+ <para>
+ Each array key corresponds with a user attribute name, and it's value is an array containing the name of the form fields for which the value to submit as part of the API call.
+ </para>
+ <example id="exam-Administrator_Guide-Attributes_Reference-A_Users_displayname">
+ <title>A User's <literal>displayname</literal></title>
+ <para>
+ Provided the user type's <literal>auto_form_fields</literal> contains an array key of <literal>displayname</literal>, the array value for this key could look as follows:
+ </para>
+ <para>
+
<screen language="PHP/PHP">Array(
'auto_form_fields' =&gt; Array(
'displayname' =&gt; Array(
@@ -244,119 +244,119 @@
(...)
);</screen>
- </para>
- <para>
- This indicates to the client that a form field named 'displayname' is to be populated with the information contained within the form fields named 'givenname' and 'sn'.
- </para>
- <para>
- If the client is capable of doing so, it should also update the form field named 'displayname' after the values for any of the form fields named 'givenname' or 'sn' have been changed.
- </para>
-
- </example>
- <para>
- With a JSON object payload containing the values of the form fields for which the names are contained within the 'data' key, if any, the client should submit a POST request on change of these form fields, and will be returned the new value for the automatically generated form field.
- </para>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Attributes_Reference-form_fields">
- <title><literal>form_fields</literal></title>
- <para>
- The <literal>form_fields</literal> key holds an array of form fields that require user input.
- </para>
-
- </formalpara>
- <para>
- The key name for each key =&gt; value pair indicates the form field name for which the value is to be supplied by the user.
- </para>
- <para>
- Because some attributes can be multi-valued, or have a limited list of options, each defined form field in <literal>form_fields</literal> can hold an array with additional key =&gt; value pairs illustrating the type of form field that should be used, and what format to expect the result value in.
- </para>
- <para>
- <itemizedlist id="item-Administrator_Guide-Attributes_Reference-Additional_Information_in_form_fields">
- <title>Additional Information in <literal>form_fields</literal></title>
- <listitem>
- <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-maxlength">
- <title><literal>maxlength</literal></title>
- <para>
- For a form field of type <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-text" /> or type <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-list" />, this value holds the maximum length for a given item.
- </para>
-
- </formalpara>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-type">
- <title><literal>type</literal></title>
- <para>
- The <literal>type</literal> is to indicate the type of form field. Options include;
- </para>
-
- </formalpara>
- <para>
- <itemizedlist>
- <listitem>
- <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-text">
- <title><literal>text</literal></title>
- <para>
- This is a regular input field of type text.
- </para>
-
- </formalpara>
- <para>
- This is the default.
- </para>
- <para>
- Additional parameters for a text form field include <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-maxlength" />.
- </para>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-list">
- <title><literal>list</literal></title>
- <para>
- A form field of type <literal>list</literal> is expecting a list of text input values.
- </para>
-
- </formalpara>
- <para>
- A client web interface could choose to display a textarea with the instructions to supply one item per line, or more advanced (better) equivalents, such as an add/delete widget.
- </para>
- <para>
- A client command-line interface could choose to prompt for input values until an empty value is supplied.
- </para>
- <para>
- Additional parameters for a list form field include <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-maxlength" />, which holds the maximum length of each text value in the list.
- </para>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-multiselect">
- <title><literal>multiselect</literal></title>
- <para>
- This form field is a select list, where multiple options may be selected (as opposed to a <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-select" /> list, where only one option may be selected).
- </para>
-
- </formalpara>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-select">
- <title><literal>select</literal></title>
- <para>
- This form field is a selection list, of which one option may be selected.
- </para>
-
- </formalpara>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </listitem>
- <!--
+ </para>
+ <para>
+ This indicates to the client that a form field named 'displayname' is to be populated with the information contained within the form fields named 'givenname' and 'sn'.
+ </para>
+ <para>
+ If the client is capable of doing so, it should also update the form field named 'displayname' after the values for any of the form fields named 'givenname' or 'sn' have been changed.
+ </para>
+
+ </example>
+ <para>
+ With a JSON object payload containing the values of the form fields for which the names are contained within the 'data' key, if any, the client should submit a POST request on change of these form fields, and will be returned the new value for the automatically generated form field.
+ </para>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Attributes_Reference-form_fields">
+ <title><literal>form_fields</literal></title>
+ <para>
+ The <literal>form_fields</literal> key holds an array of form fields that require user input.
+ </para>
+
+ </formalpara>
+ <para>
+ The key name for each key =&gt; value pair indicates the form field name for which the value is to be supplied by the user.
+ </para>
+ <para>
+ Because some attributes can be multi-valued, or have a limited list of options, each defined form field in <literal>form_fields</literal> can hold an array with additional key =&gt; value pairs illustrating the type of form field that should be used, and what format to expect the result value in.
+ </para>
+ <para>
+ <itemizedlist id="item-Administrator_Guide-Attributes_Reference-Additional_Information_in_form_fields">
+ <title>Additional Information in <literal>form_fields</literal></title>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-maxlength">
+ <title><literal>maxlength</literal></title>
+ <para>
+ For a form field of type <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-text" /> or type <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-list" />, this value holds the maximum length for a given item.
+ </para>
+
+ </formalpara>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-type">
+ <title><literal>type</literal></title>
+ <para>
+ The <literal>type</literal> is to indicate the type of form field. Options include;
+ </para>
+
+ </formalpara>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-text">
+ <title><literal>text</literal></title>
+ <para>
+ This is a regular input field of type text.
+ </para>
+
+ </formalpara>
+ <para>
+ This is the default.
+ </para>
+ <para>
+ Additional parameters for a text form field include <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-maxlength" />.
+ </para>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-list">
+ <title><literal>list</literal></title>
+ <para>
+ A form field of type <literal>list</literal> is expecting a list of text input values.
+ </para>
+
+ </formalpara>
+ <para>
+ A client web interface could choose to display a textarea with the instructions to supply one item per line, or more advanced (better) equivalents, such as an add/delete widget.
+ </para>
+ <para>
+ A client command-line interface could choose to prompt for input values until an empty value is supplied.
+ </para>
+ <para>
+ Additional parameters for a list form field include <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-maxlength" />, which holds the maximum length of each text value in the list.
+ </para>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-multiselect">
+ <title><literal>multiselect</literal></title>
+ <para>
+ This form field is a select list, where multiple options may be selected (as opposed to a <xref linkend="form-Administrator_Guide-Additional_Information_in_form_fields-select" /> list, where only one option may be selected).
+ </para>
+
+ </formalpara>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-select">
+ <title><literal>select</literal></title>
+ <para>
+ This form field is a selection list, of which one option may be selected.
+ </para>
+
+ </formalpara>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </listitem>
+ <!--
<listitem>
<formalpara id="form-Administrator_Guide-Additional_Information_in_form_fields-value_source">
<title><literal>value_source</literal></title>
@@ -377,32 +377,32 @@
</formalpara>
</listitem>
- // -->
- </itemizedlist>
-
- </para>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Attributes_Reference-fields">
- <title><literal>fields</literal></title>
- <para>
- The <literal>fields</literal> key holds an array of form fields and values for said form fields, that are static. One example of such form fields is <literal>objectclass</literal>.
- </para>
+ // -->
+ </itemizedlist>
- </formalpara>
+ </para>
- </listitem>
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Attributes_Reference-fields">
+ <title><literal>fields</literal></title>
+ <para>
+ The <literal>fields</literal> key holds an array of form fields and values for said form fields, that are static. One example of such form fields is <literal>objectclass</literal>.
+ </para>
- </itemizedlist>
+ </formalpara>
- </para>
+ </listitem>
- </section>
+ </itemizedlist>
+ </para>
- </section>
+ </section>
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Preface.xml b/Administrator_Guide/en-US/Preface.xml
index c9e647e..0b1e251 100644
--- a/Administrator_Guide/en-US/Preface.xml
+++ b/Administrator_Guide/en-US/Preface.xml
@@ -4,9 +4,9 @@
%BOOK_ENTITIES;
]>
<preface id="pref-Administrator_Guide-Preface">
- <title>Preface</title>
- <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="sect-Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="sect-About_Kolab_Groupware.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <title>Preface</title>
+ <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="sect-Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="sect-About_Kolab_Groupware.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</preface>
diff --git a/Administrator_Guide/en-US/Revision_History.xml b/Administrator_Guide/en-US/Revision_History.xml
index a75c98d..5d8b7ea 100644
--- a/Administrator_Guide/en-US/Revision_History.xml
+++ b/Administrator_Guide/en-US/Revision_History.xml
@@ -4,30 +4,30 @@
%BOOK_ENTITIES;
]>
<appendix id="appe-Administrator_Guide-Revision_History">
- <title>Revision History</title>
- <simpara>
- <revhistory>
- <revision>
- <revnumber>0-0</revnumber>
- <date>Mon Dec 13 2010</date>
- <author>
- <firstname>Dude</firstname>
- <surname>McPants</surname>
- <email>Dude.McPants@example.com</email>
+ <title>Revision History</title>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>0-0</revnumber>
+ <date>Mon Dec 13 2010</date>
+ <author>
+ <firstname>Dude</firstname>
+ <surname>McPants</surname>
+ <email>Dude.McPants@example.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Initial creation of book by publican</member>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Initial creation of book by publican</member>
- </simplelist>
+ </simplelist>
- </revdescription>
+ </revdescription>
- </revision>
+ </revision>
- </revhistory>
+ </revhistory>
- </simpara>
+ </simpara>
</appendix>
diff --git a/Administrator_Guide/en-US/Tweaking_Tips_for_389_Directory_Server.xml b/Administrator_Guide/en-US/Tweaking_Tips_for_389_Directory_Server.xml
index e5eae63..48c1ff5 100644
--- a/Administrator_Guide/en-US/Tweaking_Tips_for_389_Directory_Server.xml
+++ b/Administrator_Guide/en-US/Tweaking_Tips_for_389_Directory_Server.xml
@@ -4,66 +4,66 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server">
- <title>Tweaking Tips for 389 Directory Server</title>
- <para>
- para
- </para>
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Adjusting_Cache_Sizes">
- <title>Adjusting Cache Sizes</title>
- <para>
- para
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees">
- <title>Using Virtual List View Control for Larger Directory Information Trees</title>
- <para>
- A default deployment of Kolab Groupware includes a largely unmodified 389 Directory Server with not all too many tweaked settings. When deployments grow the size of their Directory Information Tree, such as would be the case with more than 2000 user, group and/or contact entries, regular bind credentials run out of bounds when querying the tree.
- </para>
- <para>
- Regular bind credentials include look-through, size and time limitations, usually causing a result set to be limited to 2000 entries (usually the first symptom), or causing the query to time out (larger trees, usually a later symptom).
- </para>
- <para>
- Because a variety of User Interfaces depend on listing users, groups and contacts, it may be necessary to seek aid in Virtual List View (VLV) capabilities. VLV consists of additional indexes that can be queried by enabling two server-side controls:
- </para>
- <para>
- <orderedlist>
- <listitem>
- <para>
- Virtual List View control, with corresponding Base DN, Filter and Scope
- </para>
-
- </listitem>
- <listitem>
- <para>
- Server-Side Sorting control (SSS), with a corresponding list of attributes to use when sorting result entries.
- </para>
-
- </listitem>
-
- </orderedlist>
-
- </para>
- <para>
- VLV along with SSS enables the pagination of search results, and circumvents the search limits for regular bind credentials.
- </para>
- <procedure id="proc-Administrator_Guide-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees-Configuring_VLV_and_SSS_on_389_Directory_Server">
- <title>Configuring VLV and SSS on 389 Directory Server</title>
- <step>
- <para>
- A version of these scripts can be downloaded from <ulink url="http://hosted.kolabsys.com/~vanmeeuwen/kolab-scripts.tar.gz" />.
- </para>
- <para>
- Inclusion into the <application>kolab</application> command-line utility is planned, so make sure to check <command>kolab help</command> to see if the commands have been included already.
- </para>
-
- </step>
- <step>
- <para>
- In the following few steps, the scripts refer to the variables outlined below (which are contained in <filename>./settings.sh</filename>).
- </para>
-
+ <title>Tweaking Tips for 389 Directory Server</title>
+ <para>
+ para
+ </para>
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Adjusting_Cache_Sizes">
+ <title>Adjusting Cache Sizes</title>
+ <para>
+ para
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees">
+ <title>Using Virtual List View Control for Larger Directory Information Trees</title>
+ <para>
+ A default deployment of Kolab Groupware includes a largely unmodified 389 Directory Server with not all too many tweaked settings. When deployments grow the size of their Directory Information Tree, such as would be the case with more than 2000 user, group and/or contact entries, regular bind credentials run out of bounds when querying the tree.
+ </para>
+ <para>
+ Regular bind credentials include look-through, size and time limitations, usually causing a result set to be limited to 2000 entries (usually the first symptom), or causing the query to time out (larger trees, usually a later symptom).
+ </para>
+ <para>
+ Because a variety of User Interfaces depend on listing users, groups and contacts, it may be necessary to seek aid in Virtual List View (VLV) capabilities. VLV consists of additional indexes that can be queried by enabling two server-side controls:
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Virtual List View control, with corresponding Base DN, Filter and Scope
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Server-Side Sorting control (SSS), with a corresponding list of attributes to use when sorting result entries.
+ </para>
+
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+ <para>
+ VLV along with SSS enables the pagination of search results, and circumvents the search limits for regular bind credentials.
+ </para>
+ <procedure id="proc-Administrator_Guide-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees-Configuring_VLV_and_SSS_on_389_Directory_Server">
+ <title>Configuring VLV and SSS on 389 Directory Server</title>
+ <step>
+ <para>
+ A version of these scripts can be downloaded from <ulink url="http://hosted.kolabsys.com/~vanmeeuwen/kolab-scripts.tar.gz" />.
+ </para>
+ <para>
+ Inclusion into the <application>kolab</application> command-line utility is planned, so make sure to check <command>kolab help</command> to see if the commands have been included already.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ In the following few steps, the scripts refer to the variables outlined below (which are contained in <filename>./settings.sh</filename>).
+ </para>
+
<programlisting language="Bash">#!/bin/bash
export rootdn="dc=example,dc=org"
@@ -73,12 +73,12 @@ export ldap_host="localhost"
export ldap_binddn="cn=Directory Manager"
export ldap_bindpw="VerySecret"</programlisting>
- </step>
- <step>
- <para>
- Add the VLV Search definitions:
- </para>
-
+ </step>
+ <step>
+ <para>
+ Add the VLV Search definitions:
+ </para>
+
<programlisting language="Bash">#!/bin/bash
. ./settings.sh
@@ -119,12 +119,12 @@ export ldap_bindpw="VerySecret"</programlisting>
echo ""
) | ldapadd -x -h ${ldap_host} -D "${ldap_binddn}" -w "${ldap_bindpw}" -c</programlisting>
- </step>
- <step>
- <para>
- Add the VLV Indexes:
- </para>
-
+ </step>
+ <step>
+ <para>
+ Add the VLV Indexes:
+ </para>
+
<programlisting language="Bash">#!/bin/bash
. ./settings.sh
@@ -159,12 +159,12 @@ export ldap_bindpw="VerySecret"</programlisting>
echo ""
) | ldapadd -x -h ${ldap_host} -D "${ldap_binddn}" -w "${ldap_bindpw}" -c</programlisting>
- </step>
- <step>
- <para>
- Execute the indexing tasks:
- </para>
-
+ </step>
+ <step>
+ <para>
+ Execute the indexing tasks:
+ </para>
+
<programlisting language="Bash">#!/bin/bash
. ./settings.sh
@@ -241,12 +241,12 @@ while [ ${ldap_complete} -ne 1 ]; do
fi
done</programlisting>
- </step>
- <step>
- <para>
- Test the VLV functioning with this detection and execution script:
- </para>
-
+ </step>
+ <step>
+ <para>
+ Test the VLV functioning with this detection and execution script:
+ </para>
+
<programlisting language="Bash">#!/bin/bash
. ./settings.sh
@@ -379,37 +379,37 @@ done</programlisting>
fi
done</programlisting>
- </step>
-
- </procedure>
-
- <section id="sect-Administrator_Guide-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees-Making_Use_of_VLV_and_SSS">
- <title>Making Use of VLV and SSS</title>
- <para>
- See <xref linkend="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Configuring_the_LDAP_Address_Book_for_Use_of_VLV_and_SSS" /> for instructions on configuring Roundcube to make use of VLV and SSS for its Global Address Book.
- </para>
-
- </section>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Enforcing_Global_Attribute_Uniqueness">
- <title>Enforcing (Global) Attribute Uniqueness</title>
- <para>
- para
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Enforcing_a_Password_Policy">
- <title>Enforcing a Password Policy</title>
- <para>
- para
- </para>
-
- </section>
-
+ </step>
+
+ </procedure>
+
+ <section id="sect-Administrator_Guide-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees-Making_Use_of_VLV_and_SSS">
+ <title>Making Use of VLV and SSS</title>
+ <para>
+ See <xref linkend="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Configuring_the_LDAP_Address_Book_for_Use_of_VLV_and_SSS" /> for instructions on configuring Roundcube to make use of VLV and SSS for its Global Address Book.
+ </para>
+
+ </section>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Enforcing_Global_Attribute_Uniqueness">
+ <title>Enforcing (Global) Attribute Uniqueness</title>
+ <para>
+ para
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Enforcing_a_Password_Policy">
+ <title>Enforcing a Password Policy</title>
+ <para>
+ para
+ </para>
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Tweaking_Tips_for_Cyrus_IMAP.xml b/Administrator_Guide/en-US/Tweaking_Tips_for_Cyrus_IMAP.xml
index 46bee2e..95ed08d 100644
--- a/Administrator_Guide/en-US/Tweaking_Tips_for_Cyrus_IMAP.xml
+++ b/Administrator_Guide/en-US/Tweaking_Tips_for_Cyrus_IMAP.xml
@@ -4,126 +4,126 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP">
- <title>Tweaking Tips for Cyrus IMAP</title>
- <para>
- A default Kolab Groupware environment includes most if not all features that Cyrus IMAP offers, which is not necessarily optimal for all deployments. The sections in this chapter address some of the various opportunities to tweak settings for your deployment.
- </para>
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-Flushing_Seen_State">
- <title>Flushing Seen State</title>
- <para>
- When users connect multiple clients to Cyrus IMAP, or when multiple users use the same mail folder that has shared seen state enabled, one client may be marking a message as \Seen, and another client may seem to take a while before it picks up on the message having been marked as read.
- </para>
- <para>
- In a default deployment scenario, Cyrus IMAP keeps the flagging of messages from being flushed to disk immediately, which saves on disk I/O, making Cyrus IMAP more efficient in most deployment scenarios. If, however, you have the aforementioned situation occurring in your deployment, you may need to flush the seen state of messages to disk at the first opportunity.
- </para>
- <para>
- In order to do so, execute
- </para>
- <procedure id="proc-Administrator_Guide-Flushing_Seen_State-Configuring_Cyrus_IMAP_to_Flush_the_Seen_State_to_Disk_Immediately">
- <title>Configuring Cyrus IMAP to Flush the Seen State to Disk Immediately</title>
- <step>
- <para>
- Open up /etc/imapd.conf in your favorite editor
- </para>
-
- </step>
- <step>
- <para>
- Set (add the setting if not available already) <literal>flushseenstate</literal> to <literal>1</literal>.
- </para>
-
- </step>
- <step>
- <para>
- Restart the Cyrus IMAP service
- </para>
-
- </step>
-
- </procedure>
-
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-Disabling_the_Shared_Folders_Namespace">
- <title>Disabling the "Shared Folders" Namespace</title>
- <para>
- para
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-Speeding_Up_Authentication">
- <title>Speeding Up Authentication</title>
- <para>
- para
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-Full_text_Indexing_of_Mail_Folders">
- <title>Full-text Indexing of Mail Folders</title>
- <para>
- para
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-IMAP_Single_Instance_Store">
- <title>IMAP Single Instance Store</title>
- <para>
- Cyrus IMAP allows for <emphasis>single instance store</emphasis> that de-duplicates messages being delivered to its mailboxes, but with a certain set of restrictions. This section addresses some of those restrictions and advises on parameters to tweak in Kolab to make optimal use of the feature.
- </para>
- <para>
- Single instance store requires delivery of the message (through LMTP) in one single shot (a single LMTP session). For deployments that expect to have significant numbers of emails be sent to significant numbers of users through Kolab Distribution Groups, tweaking the Postfix settings <literal>lmtp_destination_concurrency_limit</literal> and <literal>lmtp_destination_concurrency_limit</literal> may be necessary.
- </para>
- <procedure id="proc-Administrator_Guide-IMAP_Single_Instance_Store-Example_of_Single_Instance_Store">
- <title>Example of Single Instance Store</title>
- <para>
- The following example depicts a scenario in which single instance store can be shown in full force.
- </para>
- <step>
- <para>
- Set the destination concurrency and recipient limits for LMTP to 1 (from a default 20):
- </para>
- <para>
-
+ <title>Tweaking Tips for Cyrus IMAP</title>
+ <para>
+ A default Kolab Groupware environment includes most if not all features that Cyrus IMAP offers, which is not necessarily optimal for all deployments. The sections in this chapter address some of the various opportunities to tweak settings for your deployment.
+ </para>
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-Flushing_Seen_State">
+ <title>Flushing Seen State</title>
+ <para>
+ When users connect multiple clients to Cyrus IMAP, or when multiple users use the same mail folder that has shared seen state enabled, one client may be marking a message as \Seen, and another client may seem to take a while before it picks up on the message having been marked as read.
+ </para>
+ <para>
+ In a default deployment scenario, Cyrus IMAP keeps the flagging of messages from being flushed to disk immediately, which saves on disk I/O, making Cyrus IMAP more efficient in most deployment scenarios. If, however, you have the aforementioned situation occurring in your deployment, you may need to flush the seen state of messages to disk at the first opportunity.
+ </para>
+ <para>
+ In order to do so, execute
+ </para>
+ <procedure id="proc-Administrator_Guide-Flushing_Seen_State-Configuring_Cyrus_IMAP_to_Flush_the_Seen_State_to_Disk_Immediately">
+ <title>Configuring Cyrus IMAP to Flush the Seen State to Disk Immediately</title>
+ <step>
+ <para>
+ Open up /etc/imapd.conf in your favorite editor
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Set (add the setting if not available already) <literal>flushseenstate</literal> to <literal>1</literal>.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Restart the Cyrus IMAP service
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-Disabling_the_Shared_Folders_Namespace">
+ <title>Disabling the "Shared Folders" Namespace</title>
+ <para>
+ para
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-Speeding_Up_Authentication">
+ <title>Speeding Up Authentication</title>
+ <para>
+ para
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-Full_text_Indexing_of_Mail_Folders">
+ <title>Full-text Indexing of Mail Folders</title>
+ <para>
+ para
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Cyrus_IMAP-IMAP_Single_Instance_Store">
+ <title>IMAP Single Instance Store</title>
+ <para>
+ Cyrus IMAP allows for <emphasis>single instance store</emphasis> that de-duplicates messages being delivered to its mailboxes, but with a certain set of restrictions. This section addresses some of those restrictions and advises on parameters to tweak in Kolab to make optimal use of the feature.
+ </para>
+ <para>
+ Single instance store requires delivery of the message (through LMTP) in one single shot (a single LMTP session). For deployments that expect to have significant numbers of emails be sent to significant numbers of users through Kolab Distribution Groups, tweaking the Postfix settings <literal>lmtp_destination_concurrency_limit</literal> and <literal>lmtp_destination_concurrency_limit</literal> may be necessary.
+ </para>
+ <procedure id="proc-Administrator_Guide-IMAP_Single_Instance_Store-Example_of_Single_Instance_Store">
+ <title>Example of Single Instance Store</title>
+ <para>
+ The following example depicts a scenario in which single instance store can be shown in full force.
+ </para>
+ <step>
+ <para>
+ Set the destination concurrency and recipient limits for LMTP to 1 (from a default 20):
+ </para>
+ <para>
+
<screen># <userinput>postconf -e lmtp_destination_concurrency_limit=1</userinput>
# <userinput>postconf -e lmtp_destination_recipient_limit=1</userinput>
<userinput># service postfix reload</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Create a Kolab Distribution Group with 20 users.
- </para>
-
- </step>
- <step>
- <para>
- Send an email to the distribution group, such as:
- </para>
- <para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Create a Kolab Distribution Group with 20 users.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Send an email to the distribution group, such as:
+ </para>
+ <para>
+
<screen># <userinput>date | mail -s "single instance store test #1" kolab-users@example.org</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Await delivery of the mail message to all users.
- </para>
-
- </step>
- <step>
- <para>
- Examine the inode numbers (links) and the cumulative size on disk for the files.
- </para>
- <para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Await delivery of the mail message to all users.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Examine the inode numbers (links) and the cumulative size on disk for the files.
+ </para>
+ <para>
+
<screen># <userinput>cd /var/spool/imap/domain/e/example.org/</userinput>
# <userinput>files=$(grep -lr "^Subject: single instance store test #1" \</userinput>
&gt; <userinput>$(find . -type f -name "*.") | sort -u)</userinput>
@@ -181,45 +181,45 @@ Modify: 2012-08-06 11:04:06.000000000 +0200
Change: 2012-08-06 11:04:06.757235163 +0200
</screen>
- </para>
-
- </step>
- <step>
- <para>
- Set the destination concurrency and recipient limits for LMTP back to the default 20:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Set the destination concurrency and recipient limits for LMTP back to the default 20:
+ </para>
+ <para>
+
<screen># <userinput>postconf -e lmtp_destination_concurrency_limit=20</userinput>
# <userinput>postconf -e lmtp_destination_recipient_limit=20</userinput>
<userinput># service postfix reload</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Send an email to the distribution group, such as:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Send an email to the distribution group, such as:
+ </para>
+ <para>
+
<screen># <userinput>date | mail -s "single instance store test #2" kolab-users@example.org</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Await delivery of the mail message to all users.
- </para>
-
- </step>
- <step>
- <para>
- Examine the inode numbers (links) and the cumulative size on disk for the files.
- </para>
- <para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Await delivery of the mail message to all users.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Examine the inode numbers (links) and the cumulative size on disk for the files.
+ </para>
+ <para>
+
<screen># <userinput>cd /var/spool/imap/domain/e/example.org/</userinput>
# <userinput>files=$(grep -lr "^Subject: single instance store test #2" \</userinput>
&gt; <userinput>$(find . -type f -name "*.") | sort -u)</userinput>
@@ -257,15 +257,15 @@ Access: 2012-08-06 11:08:56.742891364 +0200
Modify: 2012-08-06 11:08:28.000000000 +0200
Change: 2012-08-06 11:08:28.760261876 +0200</screen>
- </para>
-
- </step>
-
- </procedure>
+ </para>
+ </step>
- </section>
+ </procedure>
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Tweaking_Tips_for_Postfix.xml b/Administrator_Guide/en-US/Tweaking_Tips_for_Postfix.xml
index 04ce9b4..1ce978b 100644
--- a/Administrator_Guide/en-US/Tweaking_Tips_for_Postfix.xml
+++ b/Administrator_Guide/en-US/Tweaking_Tips_for_Postfix.xml
@@ -4,48 +4,52 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Tweaking_Tips_for_Postfix">
- <title>Tweaking Tips for Postfix</title>
- <para>
- para
- </para>
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Postfix-Large_Kolab_Distribution_Groups">
- <title>Large Kolab Distribution Groups</title>
- <para>
- If you have Kolab distribution groups with many members, you may see the following message occur in log file <filename>/var/log/maillog</filename>:
- </para>
- <para>
-
+ <title>Tweaking Tips for Postfix</title>
+ <para>
+ para
+ </para>
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Postfix-Large_Kolab_Distribution_Groups">
+ <title>Large Kolab Distribution Groups</title>
+ <para>
+ If you have Kolab distribution groups with many members, you may see the following message occur in log file <filename>/var/log/maillog</filename>:
+ </para>
+ <para>
+
<screen>Aug 17 10:21:59 kolab postfix/cleanup[5916]: warning: 398194A151: unreasonable virtual_alias_maps map expansion size for kolab-users@example.org</screen>
- </para>
- <para>
- The setting <literal>virtual_alias_expansion_limit</literal> controls the maximum number of recipient address that are produced from a single original recipient address. The default depends on your installation.
- </para>
- <para>
- To get the default value, execute:
- </para>
- <para>
-
+ </para>
+ <para>
+ The setting <literal>virtual_alias_expansion_limit</literal> controls the maximum number of recipient address that are produced from a single original recipient address. The default depends on your installation.
+ </para>
+ <para>
+ To get the default value, execute:
+ </para>
+ <para>
+
<screen># <userinput>postconf -d virtual_alias_expansion_limit</userinput>
1000</screen>
- </para>
- <para>
- To get the current value, execute:
- </para>
- <para>
+ </para>
+ <para>
+ To get the current value, execute:
+ </para>
+ <para>
+
<screen># <userinput>postconf virtual_alias_expansion_limit</userinput>
1000</screen>
- </para>
- <para>
- To set a new value, execute:
- </para>
- <para>
+ </para>
+ <para>
+ To set a new value, execute:
+ </para>
+ <para>
+
<screen># <userinput>postconf -e virtual_alias_expansion_limit=10000</userinput></screen>
- </para>
- </section>
+ </para>
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Tweaking_Tips_for_Roundcube.xml b/Administrator_Guide/en-US/Tweaking_Tips_for_Roundcube.xml
index 89a1f97..6595358 100644
--- a/Administrator_Guide/en-US/Tweaking_Tips_for_Roundcube.xml
+++ b/Administrator_Guide/en-US/Tweaking_Tips_for_Roundcube.xml
@@ -4,180 +4,180 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Tweaking_Tips_for_Roundcube">
- <title>Tweaking Tips for Roundcube</title>
- <para>
- para
- </para>
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Setting_the_Maximum_Upload_Size">
- <title>Setting the Maximum Upload Size</title>
- <para>
- para
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Using_Memcached_for_Session_Storage">
- <title>Using Memcached for Session Storage</title>
- <para>
- para
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Using_APC_to_Accelerate_PHP">
- <title>Using APC to Accelerate PHP</title>
- <para>
- para
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Configuring_the_LDAP_Address_Book_for_Use_of_VLV_and_SSS">
- <title>Configuring the LDAP Address Book for Use of VLV and SSS</title>
- <para>
- With a large directory information tree (as described in <xref linkend="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees" />), having set up VLV and SSS (see <xref linkend="proc-Administrator_Guide-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees-Configuring_VLV_and_SSS_on_389_Directory_Server" />), Roundcube must still be configured to make use of the new settings.
- </para>
- <procedure id="proc-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_Use_of_VLV_and_SSS-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS">
- <title>Configuring the LDAP Address Book for VLV and SSS</title>
- <step>
- <para>
- Relevant settings are contained within the <literal>$rcmail_config['ldap_public']['kolab_addressbook']</literal> setting in <filename>/etc/roundcubemail/main.inc.php</filename>. Working from a default Kolab Groupware installation, we are going to verify and/or change the relevant settings one by one.
- </para>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-base_dn">
- <title><literal>base_dn</literal></title>
- <para>
- The <literal>base_dn</literal> configured in the address book should match the Base DN configured for the People VLV Search.
- </para>
-
- </formalpara>
- <para>
- Should you not have modified the configuration deployed by default too much, then the likely appropriate value for this setting is <literal>ou=People,${rootdn}</literal>
- </para>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-filter">
- <title><literal>filter</literal></title>
- <para>
- The <literal>filter</literal> configured in the address book should match the search filter configured for the People VLV Search.
- </para>
-
- </formalpara>
- <para>
- By default, all LDAP entries with object class <literal>inetOrgPerson</literal> are included.
- </para>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-scope">
- <title><literal>scope</literal></title>
- <para>
- The <literal>scope</literal> configured in the address book should match the search scope configured for the People VLV Search.
- </para>
-
- </formalpara>
- <para>
- para
- </para>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-sort">
- <title><literal>sort</literal></title>
- <para>
- The <literal>sort</literal> setting is an array, that must contain the exact list of elements configured in the vlv sort configured for the People VLV Index.
- </para>
-
- </formalpara>
- <para>
- para
- </para>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-vlv">
- <title><literal>vlv</literal></title>
- <para>
- This setting controls whether VLV is to be used at all. Set it to <literal>true</literal>.
- </para>
-
- </formalpara>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-vlv_search">
- <title><literal>vlv_search</literal></title>
- <para>
- This setting controls whether searches are to use VLV and SSS as well. More specifically, this influences auto-completion such as during the composition of new messages, adding participants to events, and adding ACL entries in folder management.
- </para>
-
- </formalpara>
- <para>
- para
- </para>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-groups_Array_base_dn">
- <title><literal>groups</literal> Array <literal>base_dn</literal></title>
- <para>
- para
- </para>
-
- </formalpara>
- <para>
- para
- </para>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-groups_Array_filter">
- <title><literal>groups</literal> Array <literal>filter</literal></title>
- <para>
- para
- </para>
-
- </formalpara>
- <para>
- para
- </para>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-groups_Array_scope">
- <title><literal>groups</literal> Array <literal>scope</literal></title>
- <para>
- para
- </para>
-
- </formalpara>
- <para>
- para
- </para>
-
- </step>
- <step>
- <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-groups_Array_sort">
- <title><literal>groups</literal> Array <literal>sort</literal></title>
- <para>
- para
- </para>
-
- </formalpara>
- <para>
- para
- </para>
-
- </step>
-
- </procedure>
-
-
- </section>
-
+ <title>Tweaking Tips for Roundcube</title>
+ <para>
+ para
+ </para>
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Setting_the_Maximum_Upload_Size">
+ <title>Setting the Maximum Upload Size</title>
+ <para>
+ para
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Using_Memcached_for_Session_Storage">
+ <title>Using Memcached for Session Storage</title>
+ <para>
+ para
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Using_APC_to_Accelerate_PHP">
+ <title>Using APC to Accelerate PHP</title>
+ <para>
+ para
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Tweaking_Tips_for_Roundcube-Configuring_the_LDAP_Address_Book_for_Use_of_VLV_and_SSS">
+ <title>Configuring the LDAP Address Book for Use of VLV and SSS</title>
+ <para>
+ With a large directory information tree (as described in <xref linkend="sect-Administrator_Guide-Tweaking_Tips_for_389_Directory_Server-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees" />), having set up VLV and SSS (see <xref linkend="proc-Administrator_Guide-Using_Virtual_List_View_Control_for_Larger_Directory_Information_Trees-Configuring_VLV_and_SSS_on_389_Directory_Server" />), Roundcube must still be configured to make use of the new settings.
+ </para>
+ <procedure id="proc-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_Use_of_VLV_and_SSS-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS">
+ <title>Configuring the LDAP Address Book for VLV and SSS</title>
+ <step>
+ <para>
+ Relevant settings are contained within the <literal>$rcmail_config['ldap_public']['kolab_addressbook']</literal> setting in <filename>/etc/roundcubemail/main.inc.php</filename>. Working from a default Kolab Groupware installation, we are going to verify and/or change the relevant settings one by one.
+ </para>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-base_dn">
+ <title><literal>base_dn</literal></title>
+ <para>
+ The <literal>base_dn</literal> configured in the address book should match the Base DN configured for the People VLV Search.
+ </para>
+
+ </formalpara>
+ <para>
+ Should you not have modified the configuration deployed by default too much, then the likely appropriate value for this setting is <literal>ou=People,${rootdn}</literal>
+ </para>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-filter">
+ <title><literal>filter</literal></title>
+ <para>
+ The <literal>filter</literal> configured in the address book should match the search filter configured for the People VLV Search.
+ </para>
+
+ </formalpara>
+ <para>
+ By default, all LDAP entries with object class <literal>inetOrgPerson</literal> are included.
+ </para>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-scope">
+ <title><literal>scope</literal></title>
+ <para>
+ The <literal>scope</literal> configured in the address book should match the search scope configured for the People VLV Search.
+ </para>
+
+ </formalpara>
+ <para>
+ para
+ </para>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-sort">
+ <title><literal>sort</literal></title>
+ <para>
+ The <literal>sort</literal> setting is an array, that must contain the exact list of elements configured in the vlv sort configured for the People VLV Index.
+ </para>
+
+ </formalpara>
+ <para>
+ para
+ </para>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-vlv">
+ <title><literal>vlv</literal></title>
+ <para>
+ This setting controls whether VLV is to be used at all. Set it to <literal>true</literal>.
+ </para>
+
+ </formalpara>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-vlv_search">
+ <title><literal>vlv_search</literal></title>
+ <para>
+ This setting controls whether searches are to use VLV and SSS as well. More specifically, this influences auto-completion such as during the composition of new messages, adding participants to events, and adding ACL entries in folder management.
+ </para>
+
+ </formalpara>
+ <para>
+ para
+ </para>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-groups_Array_base_dn">
+ <title><literal>groups</literal> Array <literal>base_dn</literal></title>
+ <para>
+ para
+ </para>
+
+ </formalpara>
+ <para>
+ para
+ </para>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-groups_Array_filter">
+ <title><literal>groups</literal> Array <literal>filter</literal></title>
+ <para>
+ para
+ </para>
+
+ </formalpara>
+ <para>
+ para
+ </para>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-groups_Array_scope">
+ <title><literal>groups</literal> Array <literal>scope</literal></title>
+ <para>
+ para
+ </para>
+
+ </formalpara>
+ <para>
+ para
+ </para>
+
+ </step>
+ <step>
+ <formalpara id="form-Administrator_Guide-Configuring_the_LDAP_Address_Book_for_VLV_and_SSS-groups_Array_sort">
+ <title><literal>groups</literal> Array <literal>sort</literal></title>
+ <para>
+ para
+ </para>
+
+ </formalpara>
+ <para>
+ para
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Upgrading_Accounts_from_Kolab_Format_version_2.xml b/Administrator_Guide/en-US/Upgrading_Accounts_from_Kolab_Format_version_2.xml
index c22bdc0..a7b7fb1 100644
--- a/Administrator_Guide/en-US/Upgrading_Accounts_from_Kolab_Format_version_2.xml
+++ b/Administrator_Guide/en-US/Upgrading_Accounts_from_Kolab_Format_version_2.xml
@@ -4,17 +4,17 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Upgrading_Accounts_from_Kolab_Format_version_2">
- <title>Upgrading Accounts from Kolab Format version 2</title>
- <para>
- Upgrading the existing accounts from a Kolab 2 server to a Kolab 3 server is a question of upgrading the server itself, but also upgrading the format from Kolab XML format version 2, to Kolab XML Format version 3.
- </para>
- <para>
- Upgrading the server itself is documented in a different chapter (TODO, link to that chapter). This chapter concerns the upgrading of IMAP Accounts from the Kolab v2 format to the Kolab v3 format.
- </para>
- <para>
- imapsync --host1 kolab2.example.org --tls1 --authuser1 john.doe@example.org --user1 cyrus-admin --proxyauth1 --password1 Welcome2KolabSystems --host2 kolab3.example.org --tls2 --authuser2 john.doe@example.org --user2 cyrus-admin --proxyauth2 --password2 Welcome2KolabSystems --include="INBOX"
- </para>
-
+ <title>Upgrading Accounts from Kolab Format version 2</title>
+ <para>
+ Upgrading the existing accounts from a Kolab 2 server to a Kolab 3 server is a question of upgrading the server itself, but also upgrading the format from Kolab XML format version 2, to Kolab XML Format version 3.
+ </para>
+ <para>
+ Upgrading the server itself is documented in a different chapter (TODO, link to that chapter). This chapter concerns the upgrading of IMAP Accounts from the Kolab v2 format to the Kolab v3 format.
+ </para>
+ <para>
+ imapsync --host1 kolab2.example.org --tls1 --authuser1 john.doe@example.org --user1 cyrus-admin --proxyauth1 --password1 Welcome2KolabSystems --host2 kolab3.example.org --tls2 --authuser2 john.doe@example.org --user2 cyrus-admin --proxyauth2 --password2 Welcome2KolabSystems --include="INBOX"
+ </para>
+
<programlisting language="Bash">#!/bin/bash
kolab -c /etc/kolab/kolab2.conf list-mailbox-acls user/*@example.org | \
@@ -33,36 +33,36 @@ kolab -c /etc/kolab/kolab2.conf list-mailbox-acls user/*@example.org | \
"${aci_permissions}"
fi
done</programlisting>
- <para>
- warning about --useuid
- </para>
- <para>
- rsync -aHvz --progress --partial --exclude="Archive/" --exclude="Administrativia/" --exclude="Bugzilla/" --exclude="Ham/" --exclude="Spam/" root@kolab.kolabsys.com:/kolab/var/imapd/spool/domain/k/kolabsys.com/v/user/vanmeeuwen/ /var/spool/imap/domain/k/kolabsys.com/v/user/vanmeeuwen/
- </para>
- <para>
- /kolab/var/imapd/domain/k/kolabsys.com/user/v/vanmeeuwen.seen
- </para>
- <para>
- /kolab/var/imapd/domain/k/kolabsys.com/user/v/vanmeeuwen.sub
- </para>
- <procedure id="proc-Administrator_Guide-Upgrading_Accounts_from_Kolab_Format_version_2-Synchronizing_IMAP_Accounts_using_Offlineimap">
- <title>Synchronizing IMAP Accounts using Offlineimap</title>
- <step>
- <para>
- Obtain the SSL certificate fingerprints needed with the following command:
- </para>
- <para>
-
+ <para>
+ warning about --useuid
+ </para>
+ <para>
+ rsync -aHvz --progress --partial --exclude="Archive/" --exclude="Administrativia/" --exclude="Bugzilla/" --exclude="Ham/" --exclude="Spam/" root@kolab.kolabsys.com:/kolab/var/imapd/spool/domain/k/kolabsys.com/v/user/vanmeeuwen/ /var/spool/imap/domain/k/kolabsys.com/v/user/vanmeeuwen/
+ </para>
+ <para>
+ /kolab/var/imapd/domain/k/kolabsys.com/user/v/vanmeeuwen.seen
+ </para>
+ <para>
+ /kolab/var/imapd/domain/k/kolabsys.com/user/v/vanmeeuwen.sub
+ </para>
+ <procedure id="proc-Administrator_Guide-Upgrading_Accounts_from_Kolab_Format_version_2-Synchronizing_IMAP_Accounts_using_Offlineimap">
+ <title>Synchronizing IMAP Accounts using Offlineimap</title>
+ <step>
+ <para>
+ Obtain the SSL certificate fingerprints needed with the following command:
+ </para>
+ <para>
+
<screen># <userinput>openssl x509 -fingerprint \</userinput>
&gt; <userinput>-in /etc/pki/cyrus-imapd/cyrus-imapd.pem | head -n 1</userinput></screen>
- </para>
-
- </step>
-
- </procedure>
+ </para>
+ </step>
+ </procedure>
+
+
<programlisting language="INI Files">[general]
metadata = ~/.offlineimap
accounts = kolab2to3
diff --git a/Administrator_Guide/en-US/Upgrading_Cyrus_IMAP_from_2.3_to_2.4.xml b/Administrator_Guide/en-US/Upgrading_Cyrus_IMAP_from_2.3_to_2.4.xml
index 3151c27..0bd1aa7 100644
--- a/Administrator_Guide/en-US/Upgrading_Cyrus_IMAP_from_2.3_to_2.4.xml
+++ b/Administrator_Guide/en-US/Upgrading_Cyrus_IMAP_from_2.3_to_2.4.xml
@@ -4,118 +4,118 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Upgrading_Cyrus_IMAP_from_2.3_to_2.4">
- <title>Upgrading Cyrus IMAP from 2.3 to 2.4</title>
- <para>
- As a seperate set of procedures, we have documented for you, the process of upgrading Cyrus IMAP 2.3 to Cyrus IMAP 2.4 on the same server system. This process involves getting some information out of Cyrus IMAP 2.3 before shutting it down and upgrading Cyrus IMAP 2.3 to 2.4.
- </para>
- <procedure id="proc-Administrator_Guide-Upgrading_Cyrus_IMAP_from_2.3_to_2.4-Preparations">
- <title>Preparations</title>
- <step>
- <para>
- During the migration, the Kolab 2 server cannot be allowed to;
- </para>
- <para>
- <orderedlist>
- <listitem>
- <para>
- Receive new email.
- </para>
-
- </listitem>
- <listitem>
- <para>
- Let users post/submit new data.
- </para>
-
- </listitem>
-
- </orderedlist>
-
- </para>
- <para>
- The easiest way to prevent any of this happening is to shut down the MTA and restrict access to the IMAP and POP services through firewalling.
- </para>
-
- </step>
- <step>
- <para>
- Remember to create a backup of the data.
- </para>
-
- </step>
-
- </procedure>
-
- <procedure id="proc-Administrator_Guide-Upgrading_Cyrus_IMAP_from_2.3_to_2.4-Upgrading_to_Cyrus_IMAP_2.4">
- <title>Upgrading to Cyrus IMAP 2.4</title>
- <step>
- <para>
- List the existing folder annotations, and save them to a file:
- </para>
- <para>
-
+ <title>Upgrading Cyrus IMAP from 2.3 to 2.4</title>
+ <para>
+ As a seperate set of procedures, we have documented for you, the process of upgrading Cyrus IMAP 2.3 to Cyrus IMAP 2.4 on the same server system. This process involves getting some information out of Cyrus IMAP 2.3 before shutting it down and upgrading Cyrus IMAP 2.3 to 2.4.
+ </para>
+ <procedure id="proc-Administrator_Guide-Upgrading_Cyrus_IMAP_from_2.3_to_2.4-Preparations">
+ <title>Preparations</title>
+ <step>
+ <para>
+ During the migration, the Kolab 2 server cannot be allowed to;
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Receive new email.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Let users post/submit new data.
+ </para>
+
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+ <para>
+ The easiest way to prevent any of this happening is to shut down the MTA and restrict access to the IMAP and POP services through firewalling.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Remember to create a backup of the data.
+ </para>
+
+ </step>
+
+ </procedure>
+
+ <procedure id="proc-Administrator_Guide-Upgrading_Cyrus_IMAP_from_2.3_to_2.4-Upgrading_to_Cyrus_IMAP_2.4">
+ <title>Upgrading to Cyrus IMAP 2.4</title>
+ <step>
+ <para>
+ List the existing folder annotations, and save them to a file:
+ </para>
+ <para>
+
<screen># <userinput>kolab list-mailbox-metadata \</userinput>
&gt; <userinput>"user/*@example.org" &gt; metadata.txt</userinput>
# <userinput>kolab list-mailbox-metadata \</userinput>
&gt; <userinput>"shared/*@example.org" &gt;&gt; metadata.txt</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Stop the Cyrus IMAP 2.3 service.
- </para>
-
- </step>
- <step>
- <para>
- Convert the annotations database to flat. This example converts the database from skiplist:
- </para>
- <para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Stop the Cyrus IMAP 2.3 service.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Convert the annotations database to flat. This example converts the database from skiplist:
+ </para>
+ <para>
+
<screen># <userinput>/path/to/cvt_cyrusdb /path/to/annotations.db skiplist /path/to/annotations.txt flat</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Copy both annotations.db and annotations.txt to a safe location.
- </para>
-
- </step>
- <step>
- <para>
- Upgrade to Cyrus IMAP 2.4.
- </para>
-
- </step>
- <xi:include href="step-convert-seen-databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <step>
- <para>
- Start the Cyrus IMAP 2.4 service:
- </para>
- <para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Copy both annotations.db and annotations.txt to a safe location.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Upgrade to Cyrus IMAP 2.4.
+ </para>
+
+ </step>
+ <xi:include href="step-convert-seen-databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <step>
+ <para>
+ Start the Cyrus IMAP 2.4 service:
+ </para>
+ <para>
+
<screen># <userinput>service cyrus-imapd start</userinput></screen>
- </para>
- <important>
- <para>
- Users should not yet be allowed to interact with the system at this point. We suggest closing access to the system through the firewall.
- </para>
-
- </important>
-
- </step>
- <xi:include href="step-select-all-mailboxes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <step>
- <para>
- Verify annotations have been preserved:
- </para>
- <para>
-
+ </para>
+ <important>
+ <para>
+ Users should not yet be allowed to interact with the system at this point. We suggest closing access to the system through the firewall.
+ </para>
+
+ </important>
+
+ </step>
+ <xi:include href="step-select-all-mailboxes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <step>
+ <para>
+ Verify annotations have been preserved:
+ </para>
+ <para>
+
<screen># <userinput>kolab -c conf/kolab-kolab2.example.org.conf \</userinput>
&gt; <userinput>list-mailbox-metadata "user/john.doe/Calendar*@example.org"</userinput>
Folder user/john.doe/Calendar@example.org
@@ -159,11 +159,11 @@ Folder user/john.doe/Calendar/Private@example.org
/shared/vendor/cmu/cyrus-imapd/size&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;305426
/shared/vendor/cmu/cyrus-imapd/sharedseen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;false</screen>
- </para>
- <para>
- If not, like in the example, use the previously saved <filename>metadata.txt</filename> to restore the annotations:
- </para>
-
+ </para>
+ <para>
+ If not, like in the example, use the previously saved <filename>metadata.txt</filename> to restore the annotations:
+ </para>
+
<programlisting language="Bash">#!/bin/bash
# Interesting Annotations
@@ -203,10 +203,10 @@ cat metadata.txt | \
fi
done</programlisting>
- </step>
-
- </procedure>
+ </step>
+ </procedure>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Upgrading_from_Kolab_2_on_OpenPKG.xml b/Administrator_Guide/en-US/Upgrading_from_Kolab_2_on_OpenPKG.xml
index d518b19..f1097c4 100644
--- a/Administrator_Guide/en-US/Upgrading_from_Kolab_2_on_OpenPKG.xml
+++ b/Administrator_Guide/en-US/Upgrading_from_Kolab_2_on_OpenPKG.xml
@@ -4,169 +4,169 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG">
- <title>Upgrading from Kolab 2 on OpenPKG</title>
- <para>
- As Kolab Groupware used to be distributed as an OpenPKG stack, with different locations for files, the upgrade of a Kolab 2 server to a Kolab 3 server is a largely manual process.
- </para>
- <note>
- <para>
- The Kolab 3 server used here has been set up for the same domain name space as the Kolab 2 server. No users have been created on the Kolab 3 server.
- </para>
-
- </note>
- <para>
- <literal>kolab2.example.org</literal> refers to the Kolab 2 server, <literal>kolab3.example.org</literal> refers to the Kolab 3 server.
- </para>
- <procedure id="proc-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Preparations">
- <title>Preparations</title>
- <step>
- <para>
- During the migration, the Kolab 2 server cannot be allowed to;
- </para>
- <para>
- <orderedlist>
- <listitem>
- <para>
- Receive new email.
- </para>
-
- </listitem>
- <listitem>
- <para>
- Let users post/submit new data.
- </para>
-
- </listitem>
-
- </orderedlist>
-
- </para>
- <para>
- The easiest way to prevent any of this happening is to shut down all Kolab Groupware related services on <literal>kolab2.example.org</literal>:
- </para>
- <para>
-
+ <title>Upgrading from Kolab 2 on OpenPKG</title>
+ <para>
+ As Kolab Groupware used to be distributed as an OpenPKG stack, with different locations for files, the upgrade of a Kolab 2 server to a Kolab 3 server is a largely manual process.
+ </para>
+ <note>
+ <para>
+ The Kolab 3 server used here has been set up for the same domain name space as the Kolab 2 server. No users have been created on the Kolab 3 server.
+ </para>
+
+ </note>
+ <para>
+ <literal>kolab2.example.org</literal> refers to the Kolab 2 server, <literal>kolab3.example.org</literal> refers to the Kolab 3 server.
+ </para>
+ <procedure id="proc-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Preparations">
+ <title>Preparations</title>
+ <step>
+ <para>
+ During the migration, the Kolab 2 server cannot be allowed to;
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Receive new email.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Let users post/submit new data.
+ </para>
+
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+ <para>
+ The easiest way to prevent any of this happening is to shut down all Kolab Groupware related services on <literal>kolab2.example.org</literal>:
+ </para>
+ <para>
+
<screen># <userinput>/kolab/bin/openpkg rc stop all</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Create a backup of the data from <literal>kolab2.example.org</literal>.
- </para>
-
- </step>
- <step>
- <para>
- Shut down the Cyrus IMAP service on <literal>kolab3.example.org</literal>:
- </para>
- <para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Create a backup of the data from <literal>kolab2.example.org</literal>.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Shut down the Cyrus IMAP service on <literal>kolab3.example.org</literal>:
+ </para>
+ <para>
+
<screen># <userinput>service cyrus-imapd stop</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Shut down the Kolab daemon on <literal>kolab3.example.org</literal>:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Shut down the Kolab daemon on <literal>kolab3.example.org</literal>:
+ </para>
+ <para>
+
<screen># <userinput>service kolabd stop</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Update the settings related to the recipient policy in <filename>/etc/kolab/kolab.conf</filename>. The following settings are important:
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- The <literal>primary_mail</literal> setting in the <literal>[<replaceable>$domain</replaceable>]</literal> section.
- </para>
- <para>
- The policy MUST<footnote> <para>
- the policy enforces consistency in the <literal>mail</literal> attribute values for all users - and therefore mailbox names, and ACL entry subject validity
- </para>
- </footnote> either match the former convention used, if any, or not be enabled at all. See <xref linkend="exam-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Example_Migration_of_example.org" /> for an example and some more gotchas.
- </para>
- <important>
- <para>
- In case the recipient policy is not to be applied, consider updating the <literal>user_types</literal> as per the instructions in <xref linkend="sect-Administrator_Guide-Kolab_Web_Administration_Panel-Editing_user_types" />.
- </para>
-
- </important>
-
- </listitem>
- <listitem>
- <para>
- The <literal>secondary_mail</literal> setting in the <literal>[<replaceable>$domain</replaceable>]</literal> section.
- </para>
- <para>
- This part of the policy does not apply should the <literal>primary_mail</literal> setting already have been disabled.
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </step>
-
- </procedure>
-
- <example id="exam-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Example_Migration_of_example.org">
- <title>Example Migration of example.org</title>
- <para>
- Our first example has had a running Kolab 2.3 on OpenPKG server, with a general email address convention of "surname"@example.org.
- </para>
- <para>
- By default, a Kolab &PRODUCT_VERSION; Groupware server will apply a recipient policy for the <literal>mail</literal> attribute value of "givenname"."surname"@example.org. The recipient policy must therefore be adjusted.
- </para>
- <para>
- In the <literal>[example.org]</literal> section in <filename>/etc/kolab/kolab.conf</filename>, the <literal>primary_mail</literal> setting must be adjusted to match the "surname"@example.org convention:
- </para>
-
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Update the settings related to the recipient policy in <filename>/etc/kolab/kolab.conf</filename>. The following settings are important:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The <literal>primary_mail</literal> setting in the <literal>[<replaceable>$domain</replaceable>]</literal> section.
+ </para>
+ <para>
+ The policy MUST<footnote> <para>
+ the policy enforces consistency in the <literal>mail</literal> attribute values for all users - and therefore mailbox names, and ACL entry subject validity
+ </para>
+ </footnote> either match the former convention used, if any, or not be enabled at all. See <xref linkend="exam-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Example_Migration_of_example.org" /> for an example and some more gotchas.
+ </para>
+ <important>
+ <para>
+ In case the recipient policy is not to be applied, consider updating the <literal>user_types</literal> as per the instructions in <xref linkend="sect-Administrator_Guide-Kolab_Web_Administration_Panel-Editing_user_types" />.
+ </para>
+
+ </important>
+
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>secondary_mail</literal> setting in the <literal>[<replaceable>$domain</replaceable>]</literal> section.
+ </para>
+ <para>
+ This part of the policy does not apply should the <literal>primary_mail</literal> setting already have been disabled.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </step>
+
+ </procedure>
+
+ <example id="exam-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Example_Migration_of_example.org">
+ <title>Example Migration of example.org</title>
+ <para>
+ Our first example has had a running Kolab 2.3 on OpenPKG server, with a general email address convention of "surname"@example.org.
+ </para>
+ <para>
+ By default, a Kolab &PRODUCT_VERSION; Groupware server will apply a recipient policy for the <literal>mail</literal> attribute value of "givenname"."surname"@example.org. The recipient policy must therefore be adjusted.
+ </para>
+ <para>
+ In the <literal>[example.org]</literal> section in <filename>/etc/kolab/kolab.conf</filename>, the <literal>primary_mail</literal> setting must be adjusted to match the "surname"@example.org convention:
+ </para>
+
<programlisting language="INI Files">(...snip...)
[example.org]
primary_mail = %(surname)s@%(domain)s
(...snip...)</programlisting>
- <para>
- Now, users that are created will get a <literal>mail</literal> attribute value of "surname"@example.org assigned.
- </para>
- <para>
- First adding user John Doe will give him a <literal>mail</literal> attribute value of <emphasis>doe@example.org</emphasis>, but should you have a Jane Doe as well, she would get <emphasis>doe2@example.org</emphasis>. It is therefore important to add users in order.
- </para>
-
- </example>
- <section id="sect-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Migration_of_LDAP">
- <title>Migration of LDAP</title>
- <para>
- This section has not been authored yet.
- </para>
-
- </section>
-
- <section id="sect-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Migration_and_Upgrade_of_Data">
- <title>Migration and Upgrade of Data</title>
- <para>
- The following procedure
- </para>
- <procedure id="proc-Administrator_Guide-Migration_and_Upgrade_of_Data-Migrate_the_Data_Through_Copying">
- <title>Migrate the Data Through Copying</title>
- <step>
- <para>
- Login to <literal>kolab3.example.org</literal> to execute the steps in this procedure.
- </para>
-
- </step>
- <!--
+ <para>
+ Now, users that are created will get a <literal>mail</literal> attribute value of "surname"@example.org assigned.
+ </para>
+ <para>
+ First adding user John Doe will give him a <literal>mail</literal> attribute value of <emphasis>doe@example.org</emphasis>, but should you have a Jane Doe as well, she would get <emphasis>doe2@example.org</emphasis>. It is therefore important to add users in order.
+ </para>
+
+ </example>
+ <section id="sect-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Migration_of_LDAP">
+ <title>Migration of LDAP</title>
+ <para>
+ This section has not been authored yet.
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG-Migration_and_Upgrade_of_Data">
+ <title>Migration and Upgrade of Data</title>
+ <para>
+ The following procedure
+ </para>
+ <procedure id="proc-Administrator_Guide-Migration_and_Upgrade_of_Data-Migrate_the_Data_Through_Copying">
+ <title>Migrate the Data Through Copying</title>
+ <step>
+ <para>
+ Login to <literal>kolab3.example.org</literal> to execute the steps in this procedure.
+ </para>
+
+ </step>
+ <!--
It doesn't seem this step causes the annotations.{db,txt} to transfer 1:1
<step>
@@ -181,12 +181,12 @@ primary_mail = %(surname)s@%(domain)s
</para>
</step>
- // --> <step>
- <para>
- Copy mailboxes.db and annotations.db. These files are located in <filename>/kolab/var/imapd/</filename> on your Kolab 2 server.
- </para>
- <para>
-
+ // --> <step>
+ <para>
+ Copy mailboxes.db and annotations.db. These files are located in <filename>/kolab/var/imapd/</filename> on your Kolab 2 server.
+ </para>
+ <para>
+
<screen># <userinput>scp root@kolab2.example.org:/kolab/var/imapd/annotations.db \</userinput>
&gt; <userinput>/var/lib/imap/annotations.db</userinput>
(...)
@@ -194,29 +194,29 @@ primary_mail = %(surname)s@%(domain)s
&gt; <userinput>/var/lib/imap/mailboxes.db</userinput>
(...)</screen>
- </para>
-
- </step>
- <step>
- <para>
- Migrate the mail spool:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Migrate the mail spool:
+ </para>
+ <para>
+
<screen># <userinput>rsync -rltpHvz --progress --partial \</userinput>
&gt; <userinput>kolab2.example.org:/var/imapd/spool/ \</userinput>
&gt; <userinput>/var/spool/imap/</userinput>
(...)</screen>
- </para>
-
- </step>
- <step>
- <para>
- Migrate the seen and subscription databases:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Migrate the seen and subscription databases:
+ </para>
+ <para>
+
<screen># <userinput>rsync -rltpHvz --progress --partial \</userinput>
&gt; <userinput>kolab2.example.org:/var/imapd/domain/ \</userinput>
&gt; <userinput>/var/lib/imap/domain/</userinput>
@@ -226,70 +226,70 @@ primary_mail = %(surname)s@%(domain)s
&gt; <userinput>/var/lib/imap/user/</userinput>
(...)</screen>
- </para>
-
- </step>
- <step>
- <para>
- Ensure the filesystem permissions are correct:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Ensure the filesystem permissions are correct:
+ </para>
+ <para>
+
<screen># <userinput>chown -R cyrus:mail /var/lib/imap/ /var/spool/imap/</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Ensure only the cyrus user can read and write, and the mail group can read the contents of either directory tree:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Ensure only the cyrus user can read and write, and the mail group can read the contents of either directory tree:
+ </para>
+ <para>
+
<screen># <userinput>find /var/lib/imap -type f -exec chmod 640 {} \;</userinput>
# <userinput>find /var/lib/imap -type d -exec chmod 750 {} \;</userinput>
# <userinput>find /var/spool/imap -type f -exec chmod 640 {} \;</userinput>
# <userinput>find /var/spool/imap -type d -exec chmod 750 {} \;</userinput></screen>
- </para>
-
- </step>
- <xi:include href="step-convert-seen-databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <step>
- <para>
- Stop the Kolab daemon:
- </para>
- <para>
+ </para>
+ </step>
+ <xi:include href="step-convert-seen-databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <step>
+ <para>
+ Stop the Kolab daemon:
+ </para>
+ <para>
+
<screen># <userinput>service kolabd stop</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Start the Cyrus IMAP service on <literal>kolab3.example.org</literal>:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Start the Cyrus IMAP service on <literal>kolab3.example.org</literal>:
+ </para>
+ <para>
+
<screen># <userinput>service cyrus-imapd start</userinput></screen>
- </para>
- <important>
- <para>
- Users should not yet be allowed to interact with the system at this point. We suggest closing access to the system through the firewall.
- </para>
-
- </important>
-
- </step>
- <xi:include href="step-select-all-mailboxes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <step>
- <para>
- The annotations database may not have been upgraded correctly, causing some annotations to miss the first 4 characters of their value. The easiest way to fix the issue, that is known to work, is to get the annotation values as they were on the old (Kolab 2) IMAP server, and set them on the new (Kolab 3) IMAP server.
- </para>
- <para>
-
+ </para>
+ <important>
+ <para>
+ Users should not yet be allowed to interact with the system at this point. We suggest closing access to the system through the firewall.
+ </para>
+
+ </important>
+
+ </step>
+ <xi:include href="step-select-all-mailboxes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <step>
+ <para>
+ The annotations database may not have been upgraded correctly, causing some annotations to miss the first 4 characters of their value. The easiest way to fix the issue, that is known to work, is to get the annotation values as they were on the old (Kolab 2) IMAP server, and set them on the new (Kolab 3) IMAP server.
+ </para>
+ <para>
+
<screen># <userinput>kolab -c conf/kolab-kolab2.example.org.conf \</userinput>
&gt; <userinput>list-mailbox-metadata "user/john.doe/Calendar*@example.org"</userinput>
Folder user/john.doe/Calendar@example.org
@@ -333,11 +333,11 @@ Folder user/john.doe/Calendar/Private@example.org
/shared/vendor/cmu/cyrus-imapd/size&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;305426
/shared/vendor/cmu/cyrus-imapd/sharedseen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;false</screen>
- </para>
- <para>
- Fix'em:
- </para>
-
+ </para>
+ <para>
+ Fix'em:
+ </para>
+
<programlisting language="Bash">#!/bin/bash
# Interesting Annotations
@@ -383,13 +383,13 @@ for folder_search in user/*@example.org shared/*@example.org; do
done</programlisting>
- </step>
- <step>
- <para>
- Upgrade all messages from Kolab Format version 2 to Kolab Format version 3 using <command>kolab-formatupgrade</command>. This command is run in two parts. The first will upgrade all mailbox contents in the personal namespace:
- </para>
- <para>
-
+ </step>
+ <step>
+ <para>
+ Upgrade all messages from Kolab Format version 2 to Kolab Format version 3 using <command>kolab-formatupgrade</command>. This command is run in two parts. The first will upgrade all mailbox contents in the personal namespace:
+ </para>
+ <para>
+
<screen># <userinput>kolab lm "user/%@example.org" | \</userinput>
&gt;&nbsp;&nbsp;&nbsp;<userinput>sed -e 's/user\///g' | \</userinput>
&gt;&nbsp;&nbsp;&nbsp;<userinput>while read user; do</userinput>
@@ -402,15 +402,15 @@ done</programlisting>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput><replaceable>localhost</replaceable></userinput>
&gt;&nbsp;&nbsp;&nbsp;<userinput>done</userinput></screen>
- </para>
- <para>
- The second part upgrades the contents of shared folders. Shared folders have no designated owners, and we can therefore not login as a designated user to upgrade the format.
- </para>
- <para>
- As the user <literal>cyrus-admin</literal> normally does not have the necessary privileges to insert new messages into mail folders, so we're going to have to give out the rights first. We'll delete them again afterwards.
- </para>
- <para>
-
+ </para>
+ <para>
+ The second part upgrades the contents of shared folders. Shared folders have no designated owners, and we can therefore not login as a designated user to upgrade the format.
+ </para>
+ <para>
+ As the user <literal>cyrus-admin</literal> normally does not have the necessary privileges to insert new messages into mail folders, so we're going to have to give out the rights first. We'll delete them again afterwards.
+ </para>
+ <para>
+
<screen># <userinput>kolab sam shared/*@example.org cyrus-admin lrswiptexa</userinput>
# <userinput>kolab lm shared/*@example.org | \</userinput>
&gt;&nbsp;&nbsp;&nbsp;<userinput>while read folder; do</userinput>
@@ -424,15 +424,15 @@ done</programlisting>
&gt;&nbsp;&nbsp;&nbsp;<userinput>done</userinput>
# <userinput>kolab dam shared/*@example.org cyrus-admin</userinput></screen>
- </para>
-
- </step>
-
- </procedure>
+ </para>
+ </step>
- </section>
+ </procedure>
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/Verifying_the_Installation.xml b/Administrator_Guide/en-US/Verifying_the_Installation.xml
index c53e3fd..c254cc3 100644
--- a/Administrator_Guide/en-US/Verifying_the_Installation.xml
+++ b/Administrator_Guide/en-US/Verifying_the_Installation.xml
@@ -4,353 +4,353 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-Verifying_the_Installation">
- <title>Verifying the Installation</title>
- <para>
- This chapter concerns verifying the Kolab Groupware installation works as expected, to the limited realm this documentation can serve. If you have modified the Kolab Groupware deployment to match your needs, some of the following verification steps may not function as expected.
- </para>
- <section id="sect-Administrator_Guide-Verifying_the_Installation-Running_Services">
- <title>Running Services</title>
- <para>
- Verify the following services are running:
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <formalpara id="form-Administrator_Guide-Running_Services-a389_Directory_Server">
- <title>389 Directory Server</title>
- <para>
- The LDAP server is crucial to authentication, authorization, user and group information and mail routing, and must be running.
- </para>
-
- </formalpara>
- <procedure>
- <step>
- <para>
- Verify the service is running:
- </para>
- <para>
-
+ <title>Verifying the Installation</title>
+ <para>
+ This chapter concerns verifying the Kolab Groupware installation works as expected, to the limited realm this documentation can serve. If you have modified the Kolab Groupware deployment to match your needs, some of the following verification steps may not function as expected.
+ </para>
+ <section id="sect-Administrator_Guide-Verifying_the_Installation-Running_Services">
+ <title>Running Services</title>
+ <para>
+ Verify the following services are running:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Running_Services-a389_Directory_Server">
+ <title>389 Directory Server</title>
+ <para>
+ The LDAP server is crucial to authentication, authorization, user and group information and mail routing, and must be running.
+ </para>
+
+ </formalpara>
+ <procedure>
+ <step>
+ <para>
+ Verify the service is running:
+ </para>
+ <para>
+
<screen># <userinput>service dirsrv status</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Verify the service is listening on the expected port(s):
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Verify the service is listening on the expected port(s):
+ </para>
+ <para>
+
<screen># <userinput>netstat -ltnp | grep -E ":(389|636)"</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Verify the firewall allows access to those ports, if the <literal>iptables</literal> service is running:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Verify the firewall allows access to those ports, if the <literal>iptables</literal> service is running:
+ </para>
+ <para>
+
<screen># <userinput>service iptables status</userinput>
# <userinput>iptables -L INPUT -n -v | grep -E "dpt:(389|636)" | grep ACCEPT</userinput></screen>
- </para>
- <note>
- <para>
- Kolab Groupware does not configure your firewall for you. You may have decided to work your firewall yourself, in which case the former commands may not include any ouput.
- </para>
-
- </note>
-
- </step>
- <step>
- <para>
- Perform a search:
- </para>
- <para>
-
+ </para>
+ <note>
+ <para>
+ Kolab Groupware does not configure your firewall for you. You may have decided to work your firewall yourself, in which case the former commands may not include any ouput.
+ </para>
+
+ </note>
+
+ </step>
+ <step>
+ <para>
+ Perform a search:
+ </para>
+ <para>
+
<screen># <userinput>ldapsearch -x -h localhost -D "${binddn}" -w "${bindpw}" -b "${basedn}"</userinput></screen>
- </para>
-
- </step>
-
- </procedure>
-
- <para>
- Log files for 389 Directory Server are located in <filename>/var/log/dirsrv/slapd-*/</filename>.
- </para>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Running_Services-Kolab_SASL_Authentication_Daemon">
- <title>Kolab SASL Authentication Daemon</title>
- <para>
- The Kolab SASL authentication daemon is used by Postfix and Cyrus IMAP, to authenticate users.
- </para>
-
- </formalpara>
- <procedure>
- <step>
- <para>
- Verify the service is running:
- </para>
- <para>
-
+ </para>
+
+ </step>
+
+ </procedure>
+
+ <para>
+ Log files for 389 Directory Server are located in <filename>/var/log/dirsrv/slapd-*/</filename>.
+ </para>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Running_Services-Kolab_SASL_Authentication_Daemon">
+ <title>Kolab SASL Authentication Daemon</title>
+ <para>
+ The Kolab SASL authentication daemon is used by Postfix and Cyrus IMAP, to authenticate users.
+ </para>
+
+ </formalpara>
+ <procedure>
+ <step>
+ <para>
+ Verify the service is running:
+ </para>
+ <para>
+
<screen># <userinput>service kolab-saslauthd status</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Make some attempts to authenticate:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Make some attempts to authenticate:
+ </para>
+ <para>
+
<screen># <userinput>testsaslauthd -u <replaceable>cyrus-admin</replaceable> -p <replaceable>$password</replaceable></userinput>
# <userinput>testsaslauthd -u <replaceable>john.doe@example.org</replaceable> -p <replaceable>$password</replaceable></userinput>
# <userinput>testsaslauthd -u <replaceable>doe</replaceable> -p <replaceable>$password</replaceable></userinput>
# <userinput>testsaslauthd -u <replaceable>doe</replaceable> -r <replaceable>example.org</replaceable> -p <replaceable>$password</replaceable></userinput></screen>
- </para>
-
- </step>
-
- </procedure>
-
- <para>
- The log file for the Kolab SASL authentication daemon is <filename>/var/log/kolab/pykolab.log</filename>.
- </para>
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Running_Services-Cyrus_IMAP">
- <title>Cyrus IMAP</title>
- <para>
- Essential for access to all email and other groupware data.
- </para>
-
- </formalpara>
- <procedure>
- <step>
- <para>
- Verify the service is running:
- </para>
- <para>
-
+ </para>
+
+ </step>
+
+ </procedure>
+
+ <para>
+ The log file for the Kolab SASL authentication daemon is <filename>/var/log/kolab/pykolab.log</filename>.
+ </para>
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Running_Services-Cyrus_IMAP">
+ <title>Cyrus IMAP</title>
+ <para>
+ Essential for access to all email and other groupware data.
+ </para>
+
+ </formalpara>
+ <procedure>
+ <step>
+ <para>
+ Verify the service is running:
+ </para>
+ <para>
+
<screen># <userinput>service cyrus-imapd status</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Verify the service is listening on the expected port(s):
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Verify the service is listening on the expected port(s):
+ </para>
+ <para>
+
<screen># <userinput>netstat -tlnp | grep -E ":(143|993)"</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Verify the firewall allows access to those ports, if the <literal>iptables</literal> service is running:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Verify the firewall allows access to those ports, if the <literal>iptables</literal> service is running:
+ </para>
+ <para>
+
<screen># <userinput>service iptables status</userinput>
# <userinput>iptables -L INPUT -n -v | grep -E "dpt:(143|993)" | grep ACCEPT</userinput></screen>
- </para>
- <note>
- <para>
- Kolab Groupware does not configure your firewall for you. You may have decided to work your firewall yourself, in which case the former commands may not include any ouput.
- </para>
-
- </note>
-
- </step>
- <step>
- <para>
- Attempt to connect and authenticate:
- </para>
- <para>
-
+ </para>
+ <note>
+ <para>
+ Kolab Groupware does not configure your firewall for you. You may have decided to work your firewall yourself, in which case the former commands may not include any ouput.
+ </para>
+
+ </note>
+
+ </step>
+ <step>
+ <para>
+ Attempt to connect and authenticate:
+ </para>
+ <para>
+
<screen># <userinput>imtest -t "" -u <replaceable>john.doe@example.org</replaceable> -w <replaceable>$password</replaceable> localhost</userinput>
# <userinput>imtest -t "" -u <replaceable>doe</replaceable> -w <replaceable>$password</replaceable> localhost</userinput></screen>
- </para>
-
- </step>
-
- </procedure>
-
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Running_Services-Apache_Webserver">
- <title>Apache Webserver</title>
- <para>
- The Apache webserver is needed for the Kolab Web Client, Administration Panel and the exchange of Free/Busy information.
- </para>
-
- </formalpara>
- <procedure id="proc-Administrator_Guide-Running_Services-Verifying_the_Apache_Webserver_Service_is_Running">
- <title>Verifying the Apache Webserver Service is Running</title>
- <step>
- <para>
- Verify the service is running:
- </para>
- <para>
-
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Running_Services-Apache_Webserver">
+ <title>Apache Webserver</title>
+ <para>
+ The Apache webserver is needed for the Kolab Web Client, Administration Panel and the exchange of Free/Busy information.
+ </para>
+
+ </formalpara>
+ <procedure id="proc-Administrator_Guide-Running_Services-Verifying_the_Apache_Webserver_Service_is_Running">
+ <title>Verifying the Apache Webserver Service is Running</title>
+ <step>
+ <para>
+ Verify the service is running:
+ </para>
+ <para>
+
<screen># <userinput>service httpd status</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Verify the service is listening on the correct ports:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Verify the service is listening on the correct ports:
+ </para>
+ <para>
+
<screen># <userinput>netstat -ltnp | grep -E ":(80|443)"</userinput></screen>
- </para>
-
- </step>
- <step>
- <para>
- Verify the firewall allows access to those ports, if the <literal>iptables</literal> service is running:
- </para>
- <para>
+ </para>
+ </step>
+ <step>
+ <para>
+ Verify the firewall allows access to those ports, if the <literal>iptables</literal> service is running:
+ </para>
+ <para>
+
<screen># <userinput>service iptables status</userinput>
# <userinput>iptables -L INPUT -n -v | grep -E "dpt:(80|443)" | grep ACCEPT</userinput></screen>
- </para>
- <note>
- <para>
- Kolab Groupware does not configure your firewall for you. You may have decided to work your firewall yourself, in which case the former commands may not include any ouput.
- </para>
-
- </note>
-
- </step>
- <step>
- <para>
- Attempt to get a few pages:
- </para>
- <para>
-
+ </para>
+ <note>
+ <para>
+ Kolab Groupware does not configure your firewall for you. You may have decided to work your firewall yourself, in which case the former commands may not include any ouput.
+ </para>
+
+ </note>
+
+ </step>
+ <step>
+ <para>
+ Attempt to get a few pages:
+ </para>
+ <para>
+
<screen># <userinput>wget -O- http://localhost</userinput>
# <userinput>wget -O- https://localhost</userinput></screen>
- </para>
- <note>
- <para>
- Kolab Groupware does not, by default, configure the webserver to also listen on HTTPS port 443.
- </para>
-
- </note>
-
- </step>
-
- </procedure>
-
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Running_Services-MySQL">
- <title>MySQL</title>
- <para>
- para
- </para>
-
- </formalpara>
- <procedure>
- <step>
- <para>
- para
- </para>
-
- </step>
-
- </procedure>
-
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Running_Services-Kolab_Web_Administration_Panel">
- <title>Kolab Web Administration Panel</title>
- <para>
- para
- </para>
-
- </formalpara>
- <procedure>
- <step>
- <para>
- para
- </para>
-
- </step>
-
- </procedure>
-
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Running_Services-Roundcube_Webmail">
- <title>Roundcube Webmail</title>
- <para>
- para
- </para>
-
- </formalpara>
- <procedure>
- <step>
- <para>
- para
- </para>
-
- </step>
-
- </procedure>
-
-
- </listitem>
- <listitem>
- <formalpara id="form-Administrator_Guide-Running_Services-The_Kolab_Daemon">
- <title>The Kolab Daemon</title>
- <para>
- para
- </para>
-
- </formalpara>
- <procedure>
- <step>
- <para>
- para
- </para>
-
- </step>
-
- </procedure>
-
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </section>
-
+ </para>
+ <note>
+ <para>
+ Kolab Groupware does not, by default, configure the webserver to also listen on HTTPS port 443.
+ </para>
+
+ </note>
+
+ </step>
+
+ </procedure>
+
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Running_Services-MySQL">
+ <title>MySQL</title>
+ <para>
+ para
+ </para>
+
+ </formalpara>
+ <procedure>
+ <step>
+ <para>
+ para
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Running_Services-Kolab_Web_Administration_Panel">
+ <title>Kolab Web Administration Panel</title>
+ <para>
+ para
+ </para>
+
+ </formalpara>
+ <procedure>
+ <step>
+ <para>
+ para
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Running_Services-Roundcube_Webmail">
+ <title>Roundcube Webmail</title>
+ <para>
+ para
+ </para>
+
+ </formalpara>
+ <procedure>
+ <step>
+ <para>
+ para
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </listitem>
+ <listitem>
+ <formalpara id="form-Administrator_Guide-Running_Services-The_Kolab_Daemon">
+ <title>The Kolab Daemon</title>
+ <para>
+ para
+ </para>
+
+ </formalpara>
+ <procedure>
+ <step>
+ <para>
+ para
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </section>
+
</chapter>
diff --git a/Administrator_Guide/en-US/chap-About_Kolab_Groupware.xml b/Administrator_Guide/en-US/chap-About_Kolab_Groupware.xml
index 39c850a..eb8a22f 100644
--- a/Administrator_Guide/en-US/chap-About_Kolab_Groupware.xml
+++ b/Administrator_Guide/en-US/chap-About_Kolab_Groupware.xml
@@ -4,27 +4,27 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Administrator_Guide-About_Kolab_Groupware">
- <title>About Kolab Groupware</title>
- <para>
- Kolab is a Groupware Solution for Emails, Appointments, Contacts and more. It supports mixed client environments (Outlook/KDE) because of an open storage format. Any email client speaking standard protocols can be served.
- </para>
- <section id="sect-Administrator_Guide-About_Kolab_Groupware-Free_Software_Components">
- <title>Free Software Components</title>
- <para>
- TODO: Come on, be a little more verbose...
- </para>
- <section id="sect-Administrator_Guide-Free_Software_Components-This_documentation">
- <title>This documentation</title>
- <para>
- Describe how this documentation can be modified to custom, internal documentation
- </para>
+ <title>About Kolab Groupware</title>
+ <para>
+ Kolab is a Groupware Solution for Emails, Appointments, Contacts and more. It supports mixed client environments (Outlook/KDE) because of an open storage format. Any email client speaking standard protocols can be served.
+ </para>
+ <section id="sect-Administrator_Guide-About_Kolab_Groupware-Free_Software_Components">
+ <title>Free Software Components</title>
+ <para>
+ TODO: Come on, be a little more verbose...
+ </para>
+ <section id="sect-Administrator_Guide-Free_Software_Components-This_documentation">
+ <title>This documentation</title>
+ <para>
+ Describe how this documentation can be modified to custom, internal documentation
+ </para>
- </section>
+ </section>
+
-
- </section>
-
- <xi:include href="sect-Supported_Platforms_and_System_Requirements.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ </section>
+
+ <xi:include href="sect-Supported_Platforms_and_System_Requirements.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</chapter>
diff --git a/Administrator_Guide/en-US/part-Clients.xml b/Administrator_Guide/en-US/part-Clients.xml
index cabfdf5..5d391cb 100644
--- a/Administrator_Guide/en-US/part-Clients.xml
+++ b/Administrator_Guide/en-US/part-Clients.xml
@@ -4,9 +4,9 @@
%BOOK_ENTITIES;
]>
<part id="part-Administrator_Guide-Kolab_Groupware_Clients">
- <title>Kolab Groupware Clients</title>
- <xi:include href="Kontact.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Thunderbird.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Outlook.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <title>Kolab Groupware Clients</title>
+ <xi:include href="Kontact.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Thunderbird.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Outlook.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
diff --git a/Administrator_Guide/en-US/part-Kolab_Server.xml b/Administrator_Guide/en-US/part-Kolab_Server.xml
index 9fbabcd..ff348ca 100755
--- a/Administrator_Guide/en-US/part-Kolab_Server.xml
+++ b/Administrator_Guide/en-US/part-Kolab_Server.xml
@@ -4,19 +4,19 @@
%BOOK_ENTITIES;
]>
<part id="part-Administrator_Guide-Kolab_Groupware_Server">
- <title>Kolab Groupware Server</title>
- <xi:include href="Upgrading_from_Kolab_2_on_OpenPKG.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <!--
+ <title>Kolab Groupware Server</title>
+ <xi:include href="Upgrading_from_Kolab_2_on_OpenPKG.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!--
<xi:include href="Upgrading_Accounts_from_Kolab_Format_version_2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Upgrading_Cyrus_IMAP_from_2.3_to_2.4.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- // --> <xi:include href="Verifying_the_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Configuring_the_Kolab_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Detailed_Kolab_Server_Overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Kolab_Web_Administration_Panel.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Combating_Spam.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Tweaking_Tips_for_389_Directory_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Tweaking_Tips_for_Cyrus_IMAP.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Tweaking_Tips_for_Postfix.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Tweaking_Tips_for_Roundcube.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ // --> <xi:include href="Verifying_the_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuring_the_Kolab_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Detailed_Kolab_Server_Overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Kolab_Web_Administration_Panel.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Combating_Spam.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Tweaking_Tips_for_389_Directory_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Tweaking_Tips_for_Cyrus_IMAP.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Tweaking_Tips_for_Postfix.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Tweaking_Tips_for_Roundcube.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
diff --git a/Administrator_Guide/en-US/sect-Kolab_Recipient_Policy_and_Web_Administration_Panel.xml b/Administrator_Guide/en-US/sect-Kolab_Recipient_Policy_and_Web_Administration_Panel.xml
new file mode 100644
index 0000000..b4bfaa8
--- /dev/null
+++ b/Administrator_Guide/en-US/sect-Kolab_Recipient_Policy_and_Web_Administration_Panel.xml
@@ -0,0 +1,464 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Administrator_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel">
+ <title>Kolab Recipient Policy and Web Administration Panel</title>
+ <para>
+ Kolab Groupware includes an automated application of user metadata, such as the user's given- and surname, to recipient email addresses. This is called <emphasis>the recipient policy</emphasis>. See <xref linkend="exam-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Example_Default_Application_of_the_Recipient_Policy" /> for the recipient policy at work.
+ </para>
+ <para>
+ The recipient policy aids deployments in achieving a level of consistency throughout their recipient database by applying a naming convention, avoiding the need for Kolab Groupware administrators to need to understand and consistently apply naming convention rules. Consistency is important when considering global address book listings and searches in different contexts, and when anticipating what a valid recipient address for a given user may be &ndash; noted that most email users do not have access to your global address book and it is likely that most communications will take place with those users.
+ </para>
+ <para>
+ Furthmore, the recipient policy allows these automatically recipient email addresses to be globally unique.
+ </para>
+ <example id="exam-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Example_Default_Application_of_the_Recipient_Policy">
+ <title>Example Default Application of the Recipient Policy</title>
+ <para>
+ If an <emphasis>example.org</emphasis> user is created with given name <emphasis>John</emphasis> and surname <emphasis>Doe</emphasis>, the default recipient policy will set the primary email address to <emphasis>john.doe@example.org</emphasis> and the secondary email addresses to <emphasis>j.doe@example.org</emphasis> and <emphasis>doe@example.org</emphasis>.
+ </para>
+
+ </example>
+ <important>
+ <para>
+ By default, the primary recipient email address is used as a globally unique identifier involving authentication (allowing login by email address), the user's mailbox name, mail delivery configuration, access control and the storage of user profiles. It is therefore very important a single primary recipient email address does not exist for two entries.
+ </para>
+
+ </important>
+ <para>
+ The recipient policy also avoids the need for Kolab Groupware administrators to understand and consistently apply the various transliteration rules for different locales. See <xref linkend="exam-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Transliteration_for_Different_Locales" /> for an example.
+ </para>
+ <example id="exam-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Transliteration_for_Different_Locales">
+ <title>Transliteration for Different Locales</title>
+ <para>
+ Names can contain non-ASCII characters, as is the case with, for example, <emphasis>Marie Möller</emphasis> (German), while recipient email addresses may not contain such characters (i.e. <emphasis>marie.möller@example.org</emphasis> is an invalid email address.
+ </para>
+ <para>
+ Without locale specific transliteration, the email address would become <emphasis>marie.moller@example.org</emphasis>. This is considered inadequate, as many users will experience this inappropriate, inconsiderate and/or awkward &ndash; it is the user's native tongue after all and transliteration is used in every-day life. Kolab Groupware should therefor also be able to apply the same transliteration rules specific to the user's native tongue.
+ </para>
+ <para>
+ With the (presumably correct) transliteration rules for German applied, the email address would become <emphasis>marie.moeller@example.org</emphasis>.
+ </para>
+
+ </example>
+ <para>
+ The recipient policy takes the value(s) of a number of attributes from an entry, and executes the recipient policy for primary and secondary recipient email addresses with help of the attribute names (referred to in the policy) and their values.
+ </para>
+ <para>
+ It will set the primary email address attribute to a singular value, though the LDAP schema allows multiple values for the default primary mail attribute <literal>mail</literal>. The secondary email address attribute (<literal>alias</literal> by default) is set to the value(s) returned by the recipient policy as well.
+ </para>
+ <formalpara id="form-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Components_that_Apply_the_Recipient_Policy">
+ <title>Components that Apply the Recipient Policy</title>
+ <para>
+ The Kolab daemon (the <literal>kolabd</literal> service) is the primary Kolab Groupware component to apply the recipient policy. The Kolab Web Administration Panel and its API also apply the recipient policy, as otherwise the user interface would be incomplete. However, installation and use of the Kolab WAP and API are optional, which is why the Kolab daemon is the primary component to apply the policy.
+ </para>
+
+ </formalpara>
+ <para>
+ Both components use the configuration settings <literal>primary_mail</literal> and <literal>secondary_mail</literal> as their policy configuration. These configuration items consist of a Python notation for string formatting, along with a limited number of string operations.
+ </para>
+ <para>
+ The <literal>primary_mail</literal> setting contains a singular basestring to be used in simplistic string formatting, while the <literal>secondary_mail</literal> setting contains a numerically ordered list of singular basestrings to be used in string formatting, with the opportunity to execute some additional string operations such as substrings and capitalization.
+ </para>
+ <example id="exam-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Example_Primary_Email_Address_Recipient_Policy">
+ <title>Example Primary Email Address Recipient Policy</title>
+ <para>
+ The primary recipient email address for an <emphasis>example.org</emphasis> user with given name <emphasis>Marie</emphasis>, surname <emphasis>Möller</emphasis> and preffered language <emphasis>de_DE</emphasis>, is composed as follows:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ The recipient policy is obtained from the <literal>primary_mail</literal> setting. By default, this configuration setting is set to:
+ </para>
+ <para>
+
+<screen language="INI Files">[example.org]
+primary_mail = %(givenname)s.%(surname)s@%(domain)s</screen>
+
+ </para>
+ <para>
+ As the configuration indicates, the attributes for the user that will be used are the given name and the surname.
+ </para>
+ <note>
+ <para>
+ For the Kolab Web Administration Panel API, the attributes supplied to the recipient policy routine are actually configured, rather than obtained from the policy configuration itself. See <xref linkend="proc-Administrator_Guide-Configuring_the_Recipient_Policy-Setting_Primary_Recipient_Email_Address" /> for more information.
+ </para>
+ <para>
+ The Kolab daemon passes a complete list of all attributes along to the recipient policy routine.
+ </para>
+
+ </note>
+
+ </step>
+ <step>
+ <para>
+ Either a specified preferred language is used, or the default locale, to transliterate the given name and surname. In this example, the transliteration rules for German are used. The result is a dictionary that looks as follows:
+ </para>
+ <para>
+
+<screen language="Python">{
+ "givenname": "Maria",
+ "surname": "Moeller",
+ "preferredlanguage": "de_DE"
+ }</screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Using Python's string formatting, the resulting primary recipient email address would become:
+ </para>
+ <para>
+
+<screen language="Python">primary_mail = "%(givenname)s.%(surname)s@%(domain)s" % {
+ "givenname": "Maria",
+ "surname": "Moeller",
+ "preferredlanguage": "de_DE"
+ }
+print primary_mail</screen>
+
+ </para>
+ <para>
+ or:
+ </para>
+ <para>
+
+<screen>maria.moeller@example.org</screen>
+
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </example>
+ <example id="exam-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Example_Secondary_Email_Address_Recipient_Policy">
+ <title>Example Secondary Email Address Recipient Policy</title>
+ <para>
+ The secondary recipient email address for an <emphasis>example.org</emphasis> user with given name <emphasis>Marie</emphasis>, surname <emphasis>Möller</emphasis> and preffered language <emphasis>de_DE</emphasis>, is composed as follows:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ The recipient policy is obtained from the <literal>secondary_mail</literal> setting. By default, this configuration setting is set to:
+ </para>
+ <para>
+
+<screen language="INI Files">[example.org]
+secondary_mail = {
+ 0: {
+ "{0}.{1}@{2}": "format('%(givenname)s'[0:1].capitalize(), '%(surname)s', '%(domain)s')"
+ },
+ 1: {
+ "{0}@{1}": "format('%(uid)s', '%(domain)s')"
+ },
+ 2: {
+ "{0}@{1}": "format('%(givenname)s.%(surname)s', '%(domain)s')"
+ }
+}</screen>
+
+ </para>
+ <para>
+ As the configuration indicates, the attributes for the user that will be used are the given name, the surname and the uid.
+ </para>
+ <note>
+ <para>
+ For the Kolab Web Administration Panel API, the attributes supplied to the recipient policy routine are actually configured, rather than obtained from the policy configuration itself. See <xref linkend="proc-Administrator_Guide-Configuring_the_Recipient_Policy-Setting_the_Secondary_Recipient_Email_Address" /> for more information.
+ </para>
+ <para>
+ The Kolab daemon passes a complete list of all attributes along to the recipient policy routine.
+ </para>
+
+ </note>
+
+ </step>
+ <step>
+ <para>
+ Either a specified preferred language is used, or the default locale, to transliterate the given name and surname. In this example, the transliteration rules for German are used. The result is a dictionary that looks as follows:
+ </para>
+ <para>
+
+<screen language="Python">{
+ "givenname": "Maria",
+ "surname": "Moeller",
+ "preferredlanguage": "de_DE",
+ "uid": "moeller"
+ }</screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Using Python's string formatting, the resulting primary recipient email address would become:
+ </para>
+ <para>
+
+<screen language="Python">secondary_mail = {
+ 0: {
+ "{0}.{1}@{2}": "format('Maria'[0:1].capitalize(), 'Moeller', 'example.org')"
+ },
+ 1: {
+ "{0}@{1}": "format('moeller', 'example.org')"
+ },
+ 2: {
+ "{0}@{1}": "format('maria.moeller', 'example.org')"
+ }
+ }
+
+print secondary_mail</screen>
+
+ </para>
+ <para>
+ or:
+ </para>
+ <para>
+
+<screen>- m.moeller@example.org
+- moeller@example.org
+- maria.moeller@example.org</screen>
+
+ </para>
+
+ </step>
+
+ </procedure>
+
+
+ </example>
+ <section id="sect-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Configuring_the_Recipient_Policy">
+ <title>Configuring the Recipient Policy</title>
+ <procedure id="proc-Administrator_Guide-Configuring_the_Recipient_Policy-Setting_Primary_Recipient_Email_Address">
+ <title>Setting Primary Recipient Email Address</title>
+ <para>
+ The primary recipient email address can be changed to reflect your naming convention through this procedure:
+ </para>
+ <step>
+ <para>
+ Edit /etc/kolab/kolab.conf and replace the value of the primary_mail setting in the applicable domain section. For example, set the policy to <literal>%(givenname)s@%(domain)s</literal> to get email addresses like <emphasis>john@example.org</emphasis> and <emphasis>jane@example.org</emphasis>.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Edit the user types for any user that matches the filter used by the kolab daemon to determine which users are kolab users. For example, "Kolab Users" and "Mail-enabled POSIX users" both include "objectclass=kolabinetorgperson" (the default kolab_user_filter) and therefore the Kolab daemon would apply the recipient policy to these objects. For each of these user_types, make sure that the auto_form_field configuration for the mail and alias attributes include all attributes needed to compose the addresses.
+ </para>
+ <example id="exam-Administrator_Guide-Setting_Primary_Recipient_Email_Address-Example">
+ <title>Example</title>
+ <para>
+ para
+ </para>
+
+ </example>
+
+ </step>
+
+ </procedure>
+
+ <procedure id="proc-Administrator_Guide-Configuring_the_Recipient_Policy-Setting_the_Secondary_Recipient_Email_Address">
+ <title>Setting the Secondary Recipient Email Address</title>
+ <para>
+ The primary recipient email address can be changed to reflect your naming convention through this procedure:
+ </para>
+ <step>
+ <para>
+ Edit /etc/kolab/kolab.conf and replace the value of the primary_mail setting in the applicable domain section. For example, set the policy to <literal>%(givenname)s@%(domain)s</literal> to get email addresses like <emphasis>john@example.org</emphasis> and <emphasis>jane@example.org</emphasis>.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Edit the user types for any user that matches the filter used by the kolab daemon to determine which users are kolab users. For example, "Kolab Users" and "Mail-enabled POSIX users" both include "objectclass=kolabinetorgperson" (the default kolab_user_filter) and therefore the Kolab daemon would apply the recipient policy to these objects. For each of these user_types, make sure that the auto_form_field configuration for the mail and alias attributes include all attributes needed to compose the addresses.
+ </para>
+ <example id="exam-Administrator_Guide-Setting_the_Secondary_Recipient_Email_Address-Example">
+ <title>Example</title>
+ <para>
+ para
+ </para>
+
+ </example>
+
+ </step>
+
+ </procedure>
+
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Controlling_the_Primary_and_Secondary_Recipient_Email_Address_Attributes">
+ <title>Controlling the Primary and Secondary Recipient Email Address Attributes</title>
+ <para>
+ The attribute names that contain the primary and secondary recipient email addresses are controlled by the <literal>mail_attrs</literal> setting in the <literal>[<replaceable>$domain</replaceable>]</literal> section of <filename>/etc/kolab/kolab.conf</filename>. Should no such section or setting exist, the fallback in the <literal>[<replaceable>$auth_mechanism</replaceable>]</literal> section is used, where <literal>$auth_mechanism</title> is the authentication mechanism configured using the <literal>auth_mechanism</literal> setting in the <literal>[kolab]</literal> section &ndash; note that only 'ldap' is currently supported as an authentication mechanism.
+ </para>
+ <para>
+ This setting is a comma- and/or comma-space separated list of attribute names. By default, <literal>mail_attrs</literal> is set to <literal>mail, alias</literal>.
+ </para>
+ <para>
+ The first item in the list will be used as the attribute to use for primary recipient email addresses. The second item in the list will be used as the attribute to use for secondary recipient email addresses.
+ </para>
+
+ </section>
+
+ <section id="sect-Administrator_Guide-Kolab_Recipient_Policy_and_Web_Administration_Panel-Disabling_the_Recipient_Policy">
+ <title>Disabling the Recipient Policy</title>
+ <para>
+ The following procedure describes how to disable the recipient policy.
+ </para>
+ <procedure id="proc-Administrator_Guide-Disabling_the_Recipient_Policy-Disabling_the_Recipient_Policy">
+ <title>Disabling the Recipient Policy</title>
+ <step>
+ <para>
+ Edit <filename>/etc/kolab/kolab.conf</filename> and navigate to the section applicable for your domain (named <literal>[<replaceable>$domain</replaceable>]</literal>).
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Remove the settings <literal>primary_mail</literal> and <literal>secondary_mail</literal>.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Restart the Kolab daemon:
+ </para>
+ <para>
+
+<screen># <userinput>service kolabd restart</userinput></screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Copy <filename>/usr/share/doc/kolab-webadmin-*/sample-insert-user_types.php</filename> to <filename>/usr/share/kolab-webadmin/</filename>:
+ </para>
+ <para>
+
+<screen># <userinput>cp /usr/share/doc/kolab-webadmin-*/sample-insert-user_types.php \</userinput>
+&gt; <userinput>/usr/share/kolab-webadmin/</userinput></screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Open <filename>/usr/share/kolab-webadmin/sample-insert-user_types.php</filename> in an editor.
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Remove the values of <literal>$attributes['auto_form_fields']['mail']</literal> and <literal>$attributes['auto_form_fields']['alias']</literal>. The corresponding lines should look as follows:
+ </para>
+ <para>
+
+<screen> "alias" =&gt; Array(
+ "type" =&gt; "list",
+ "data" =&gt; Array(
+ "givenname",
+ "preferredlanguage",
+ "sn",
+ ),
+ ),
+</screen>
+
+ </para>
+ <para>
+ and:
+ </para>
+ <para>
+
+<screen> "mail" =&gt; Array(
+ "data" =&gt; Array(
+ "givenname",
+ "preferredlanguage",
+ "sn",
+ ),
+ ),
+</screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Edit the value of <literal>$attributes['form_fields']['alias']</literal> and add <literal>$attributes['form_fields']['alias']['type'] =&gt; "list"</literal>:
+ </para>
+ <para>
+
+<screen> "alias" =&gt; Array(
+ "optional" =&gt; true,
+ "type" =&gt; "list"
+ ),
+</screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Add a new value <literal>$attributes['form_fields']['mail']</literal> with the following contents:
+ </para>
+ <para>
+
+<screen> "mail" =&gt; Array(
+ "optional" =&gt; true
+ ),
+</screen>
+
+ </para>
+
+ </step>
+ <step>
+ <important>
+ <para>
+ Remember to remove the aforementioned <literal>$attributes['auto_form_fields']</literal> changes to all user types that have mail attributes.
+ </para>
+
+ </important>
+
+ </step>
+ <step>
+ <para>
+ Exit the editor, saving your changes, and check the PHP syntax:
+ </para>
+ <para>
+
+<screen># <userinput>cd /usr/share/kolab-webadmin/</userinput>
+# <userinput>php -l sample-insert-user_types.php</userinput></screen>
+
+ </para>
+
+ </step>
+ <step>
+ <para>
+ Apply the changes to the database:
+ </para>
+ <para>
+
+<screen># <userinput>php sample-insert-user_types.php</userinput></screen>
+
+ </para>
+ <note>
+ <para>
+ You may have to log out and log back in of the Kolab Web Administration Panel for the changes to take effect.
+ </para>
+
+ </note>
+
+ </step>
+
+ </procedure>
+
+
+ </section>
+
+
+</section>
+
+
diff --git a/Administrator_Guide/es-ES/Combating_Spam.po b/Administrator_Guide/es-ES/Combating_Spam.po
index 51e92e0..dfd8e8d 100644
--- a/Administrator_Guide/es-ES/Combating_Spam.po
+++ b/Administrator_Guide/es-ES/Combating_Spam.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:16+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Configuring_the_Kolab_Server.po b/Administrator_Guide/es-ES/Configuring_the_Kolab_Server.po
index 0720e59..23dd287 100644
--- a/Administrator_Guide/es-ES/Configuring_the_Kolab_Server.po
+++ b/Administrator_Guide/es-ES/Configuring_the_Kolab_Server.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Detailed_Kolab_Server_Overview.po b/Administrator_Guide/es-ES/Detailed_Kolab_Server_Overview.po
index 91494b0..84ecd9e 100644
--- a/Administrator_Guide/es-ES/Detailed_Kolab_Server_Overview.po
+++ b/Administrator_Guide/es-ES/Detailed_Kolab_Server_Overview.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Kolab_Web_Administration_Panel.po b/Administrator_Guide/es-ES/Kolab_Web_Administration_Panel.po
index 34e56d5..99ec539 100644
--- a/Administrator_Guide/es-ES/Kolab_Web_Administration_Panel.po
+++ b/Administrator_Guide/es-ES/Kolab_Web_Administration_Panel.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Preface.po b/Administrator_Guide/es-ES/Preface.po
index b9aab54..90b393a 100644
--- a/Administrator_Guide/es-ES/Preface.po
+++ b/Administrator_Guide/es-ES/Preface.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Revision_History.po b/Administrator_Guide/es-ES/Revision_History.po
index ae4f9f3..04a10be 100644
--- a/Administrator_Guide/es-ES/Revision_History.po
+++ b/Administrator_Guide/es-ES/Revision_History.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:19+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Tweaking_Tips_for_389_Directory_Server.po b/Administrator_Guide/es-ES/Tweaking_Tips_for_389_Directory_Server.po
index 86d991b..7ea145e 100644
--- a/Administrator_Guide/es-ES/Tweaking_Tips_for_389_Directory_Server.po
+++ b/Administrator_Guide/es-ES/Tweaking_Tips_for_389_Directory_Server.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Tweaking_Tips_for_Cyrus_IMAP.po b/Administrator_Guide/es-ES/Tweaking_Tips_for_Cyrus_IMAP.po
index 1e956f4..452eccc 100644
--- a/Administrator_Guide/es-ES/Tweaking_Tips_for_Cyrus_IMAP.po
+++ b/Administrator_Guide/es-ES/Tweaking_Tips_for_Cyrus_IMAP.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Tweaking_Tips_for_Postfix.po b/Administrator_Guide/es-ES/Tweaking_Tips_for_Postfix.po
index 49dfc79..65455d7 100644
--- a/Administrator_Guide/es-ES/Tweaking_Tips_for_Postfix.po
+++ b/Administrator_Guide/es-ES/Tweaking_Tips_for_Postfix.po
@@ -5,9 +5,9 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
-"PO-Revision-Date: 2012-08-13 13:16+0000\n"
-"Last-Translator: Automatically generated\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
+"PO-Revision-Date: 2012-08-24 15:42+0000\n"
+"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -24,3 +24,66 @@ msgstr ""
#, no-c-format
msgid "para"
msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Large Kolab Distribution Groups"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you have Kolab distribution groups with many members, you may see the "
+"following message occur in log file <filename>/var/log/maillog</filename>:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"Aug 17 10:21:59 kolab postfix/cleanup[5916]: warning: 398194A151: "
+"unreasonable virtual_alias_maps map expansion size for kolab-"
+"users@example.org"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The setting <literal>virtual_alias_expansion_limit</literal> controls the "
+"maximum number of recipient address that are produced from a single original"
+" recipient address. The default depends on your installation."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To get the default value, execute:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"# <userinput>postconf -d virtual_alias_expansion_limit</userinput>\n"
+"1000"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To get the current value, execute:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"# <userinput>postconf virtual_alias_expansion_limit</userinput>\n"
+"1000"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To set a new value, execute:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"# <userinput>postconf -e virtual_alias_expansion_limit=10000</userinput>"
+msgstr ""
diff --git a/Administrator_Guide/es-ES/Tweaking_Tips_for_Roundcube.po b/Administrator_Guide/es-ES/Tweaking_Tips_for_Roundcube.po
index fb27323..83dc09e 100644
--- a/Administrator_Guide/es-ES/Tweaking_Tips_for_Roundcube.po
+++ b/Administrator_Guide/es-ES/Tweaking_Tips_for_Roundcube.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Upgrading_Accounts_from_Kolab_Format_version_2.po b/Administrator_Guide/es-ES/Upgrading_Accounts_from_Kolab_Format_version_2.po
index bf89a0b..649c014 100644
--- a/Administrator_Guide/es-ES/Upgrading_Accounts_from_Kolab_Format_version_2.po
+++ b/Administrator_Guide/es-ES/Upgrading_Accounts_from_Kolab_Format_version_2.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/Upgrading_from_Kolab_2_on_OpenPKG.po b/Administrator_Guide/es-ES/Upgrading_from_Kolab_2_on_OpenPKG.po
index 626b24d..01d8364 100644
--- a/Administrator_Guide/es-ES/Upgrading_from_Kolab_2_on_OpenPKG.po
+++ b/Administrator_Guide/es-ES/Upgrading_from_Kolab_2_on_OpenPKG.po
@@ -5,8 +5,8 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
-"PO-Revision-Date: 2012-08-15 22:09+0000\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
+"PO-Revision-Date: 2012-08-24 15:43+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
"MIME-Version: 1.0\n"
@@ -463,9 +463,9 @@ msgid ""
"&gt;&nbsp;&nbsp;&nbsp;<userinput>sed -e 's/user\\///g' | \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;<userinput>while read user; do</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>kolab-formatupgrade \\</userinput>\n"
-"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--user cyrus-admin \\</userinput>\n"
+"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--user \"${user}\" \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--password <replaceable>$password</replaceable> \\</userinput>\n"
-"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--proxyauth \"${user}\" \\</userinput>\n"
+"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--proxyauth cyrus-admin \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--port 143 \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--encrypt TLS \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput><replaceable>localhost</replaceable></userinput>\n"
diff --git a/Administrator_Guide/es-ES/Verifying_the_Installation.po b/Administrator_Guide/es-ES/Verifying_the_Installation.po
index f41d7ae..b6997d7 100644
--- a/Administrator_Guide/es-ES/Verifying_the_Installation.po
+++ b/Administrator_Guide/es-ES/Verifying_the_Installation.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:18+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/chap-About_Kolab_Groupware.po b/Administrator_Guide/es-ES/chap-About_Kolab_Groupware.po
index 79600d0..300f59d 100644
--- a/Administrator_Guide/es-ES/chap-About_Kolab_Groupware.po
+++ b/Administrator_Guide/es-ES/chap-About_Kolab_Groupware.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/part-Clients.po b/Administrator_Guide/es-ES/part-Clients.po
index df2cf92..a837eeb 100644
--- a/Administrator_Guide/es-ES/part-Clients.po
+++ b/Administrator_Guide/es-ES/part-Clients.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/part-Kolab_Server.po b/Administrator_Guide/es-ES/part-Kolab_Server.po
index a239bb2..78e8eef 100644
--- a/Administrator_Guide/es-ES/part-Kolab_Server.po
+++ b/Administrator_Guide/es-ES/part-Kolab_Server.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/sect-About_Kolab_Groupware.po b/Administrator_Guide/es-ES/sect-About_Kolab_Groupware.po
index 1e85129..98fce6a 100644
--- a/Administrator_Guide/es-ES/sect-About_Kolab_Groupware.po
+++ b/Administrator_Guide/es-ES/sect-About_Kolab_Groupware.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/sect-Feedback.po b/Administrator_Guide/es-ES/sect-Feedback.po
index f87560c..7f1e033 100644
--- a/Administrator_Guide/es-ES/sect-Feedback.po
+++ b/Administrator_Guide/es-ES/sect-Feedback.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/sect-Kolab_Product_Series.po b/Administrator_Guide/es-ES/sect-Kolab_Product_Series.po
index d440393..d911148 100644
--- a/Administrator_Guide/es-ES/sect-Kolab_Product_Series.po
+++ b/Administrator_Guide/es-ES/sect-Kolab_Product_Series.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-13 14:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/sect-Supported_Platforms_and_System_Requirements.po b/Administrator_Guide/es-ES/sect-Supported_Platforms_and_System_Requirements.po
index 7e7af66..0413267 100644
--- a/Administrator_Guide/es-ES/sect-Supported_Platforms_and_System_Requirements.po
+++ b/Administrator_Guide/es-ES/sect-Supported_Platforms_and_System_Requirements.po
@@ -5,8 +5,8 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
-"PO-Revision-Date: 2012-08-15 22:09+0000\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
+"PO-Revision-Date: 2012-08-24 15:44+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
"MIME-Version: 1.0\n"
diff --git a/Administrator_Guide/es-ES/step-convert-seen-databases.po b/Administrator_Guide/es-ES/step-convert-seen-databases.po
index faad1da..686e6fb 100644
--- a/Administrator_Guide/es-ES/step-convert-seen-databases.po
+++ b/Administrator_Guide/es-ES/step-convert-seen-databases.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/es-ES/step-select-all-mailboxes.po b/Administrator_Guide/es-ES/step-select-all-mailboxes.po
index a926bfc..4d25b24 100644
--- a/Administrator_Guide/es-ES/step-select-all-mailboxes.po
+++ b/Administrator_Guide/es-ES/step-select-all-mailboxes.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:53\n"
"PO-Revision-Date: 2012-08-15 22:08+0000\n"
"Last-Translator: Jeroen van Meeuwen <vanmeeuwen@kolabsys.com>\n"
"Language-Team: Spanish (http://www.transifex.com/projects/p/kolab/language/es/)\n"
diff --git a/Administrator_Guide/fr-FR/Tweaking_Tips_for_Postfix.po b/Administrator_Guide/fr-FR/Tweaking_Tips_for_Postfix.po
index 1216a75..ca85500 100644
--- a/Administrator_Guide/fr-FR/Tweaking_Tips_for_Postfix.po
+++ b/Administrator_Guide/fr-FR/Tweaking_Tips_for_Postfix.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-13T14:57:51\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13T14:49:20\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -22,3 +22,57 @@ msgstr ""
#, no-c-format
msgid "para"
msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Large Kolab Distribution Groups"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you have Kolab distribution groups with many members, you may see the following message occur in log file <filename>/var/log/maillog</filename>:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "Aug 17 10:21:59 kolab postfix/cleanup[5916]: warning: 398194A151: unreasonable virtual_alias_maps map expansion size for kolab-users@example.org"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The setting <literal>virtual_alias_expansion_limit</literal> controls the maximum number of recipient address that are produced from a single original recipient address. The default depends on your installation."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To get the default value, execute:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"# <userinput>postconf -d virtual_alias_expansion_limit</userinput>\n"
+"1000"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To get the current value, execute:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid ""
+"# <userinput>postconf virtual_alias_expansion_limit</userinput>\n"
+"1000"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To set a new value, execute:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# <userinput>postconf -e virtual_alias_expansion_limit=10000</userinput>"
+msgstr ""
diff --git a/Administrator_Guide/fr-FR/Upgrading_from_Kolab_2_on_OpenPKG.po b/Administrator_Guide/fr-FR/Upgrading_from_Kolab_2_on_OpenPKG.po
index 065f358..f82d279 100644
--- a/Administrator_Guide/fr-FR/Upgrading_from_Kolab_2_on_OpenPKG.po
+++ b/Administrator_Guide/fr-FR/Upgrading_from_Kolab_2_on_OpenPKG.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-15T22:08:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-13T14:49:20\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -397,9 +397,9 @@ msgid ""
"&gt;&nbsp;&nbsp;&nbsp;<userinput>sed -e 's/user\\///g' | \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;<userinput>while read user; do</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>kolab-formatupgrade \\</userinput>\n"
-"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--user cyrus-admin \\</userinput>\n"
+"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--user \"${user}\" \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--password <replaceable>$password</replaceable> \\</userinput>\n"
-"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--proxyauth \"${user}\" \\</userinput>\n"
+"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--proxyauth cyrus-admin \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--port 143 \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput>--encrypt TLS \\</userinput>\n"
"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<userinput><replaceable>localhost</replaceable></userinput>\n"
diff --git a/Administrator_Guide/ja-JP/Administrator_Guide.po b/Administrator_Guide/ja-JP/Administrator_Guide.po
index 5dd79b1..d801043 100644
--- a/Administrator_Guide/ja-JP/Administrator_Guide.po
+++ b/Administrator_Guide/ja-JP/Administrator_Guide.po
@@ -1,14 +1,14 @@
-#
+#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-24T15:34:45\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-
diff --git a/Administrator_Guide/ja-JP/Author_Group.po b/Administrator_Guide/ja-JP/Author_Group.po
index 9f1d800..e488bf5 100644
--- a/Administrator_Guide/ja-JP/Author_Group.po
+++ b/Administrator_Guide/ja-JP/Author_Group.po
@@ -1,13 +1,14 @@
-#
+#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-24T15:34:45\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@@ -46,4 +47,3 @@ msgstr ""
#, no-c-format
msgid "Systems Architect"
msgstr ""
-
diff --git a/Administrator_Guide/ja-JP/Book_Info.po b/Administrator_Guide/ja-JP/Book_Info.po
index 12e238e..2d228aa 100644
--- a/Administrator_Guide/ja-JP/Book_Info.po
+++ b/Administrator_Guide/ja-JP/Book_Info.po
@@ -1,13 +1,14 @@
-#
+#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:45\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
"PO-Revision-Date: 2012-08-24T15:34:45\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@@ -31,4 +32,3 @@ msgstr ""
#, no-c-format
msgid "A short overview and summary of the book's subject and purpose, traditionally no more than one paragraph long. Note: the abstract will appear in the front matter of your book and will also be placed in the description field of the book's RPM spec file."
msgstr ""
-
diff --git a/Administrator_Guide/ja-JP/Combating_Spam.po b/Administrator_Guide/ja-JP/Combating_Spam.po
index 2612db9..44fa890 100644
--- a/Administrator_Guide/ja-JP/Combating_Spam.po
+++ b/Administrator_Guide/ja-JP/Combating_Spam.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:45\n"
-"PO-Revision-Date: 2012-08-24T15:34:45\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
+"PO-Revision-Date: 2012-08-13 13:16+0000\n"
"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -19,37 +22,60 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Kolab Groupware includes <application>SpamAssassin</application>, a fast, well-established anti-spam solution with a large community of supporters contributing not only to the code, but to rulesets as well."
+msgid ""
+"Kolab Groupware includes <application>SpamAssassin</application>, a fast, "
+"well-established anti-spam solution with a large community of supporters "
+"contributing not only to the code, but to rulesets as well."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Combating spam is always a tricky situation. On the organizational level, a strategy has to be formulated to combat spam in order to achieve the maximum flexibility and effectiveness for individual users, separate organizations, and the deployment as a whole."
+msgid ""
+"Combating spam is always a tricky situation. On the organizational level, a "
+"strategy has to be formulated to combat spam in order to achieve the maximum"
+" flexibility and effectiveness for individual users, separate organizations,"
+" and the deployment as a whole."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A common deployment is to define deployment-wide user preferences and to use a single, deployment-wide set of rules for <application>SpamAssassin</application> to operate with -including Bayes database(s)."
+msgid ""
+"A common deployment is to define deployment-wide user preferences and to use"
+" a single, deployment-wide set of rules for "
+"<application>SpamAssassin</application> to operate with -including Bayes "
+"database(s)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The problems start when individual users mark legitimate email as spam, most notably the company newsletter or correspondation they have opted in some time ago, but wish to no longer receive. Users tend to ignore the long-term effects of marking these message as spam, if at all they are aware of any, and just want such messages out of their way."
+msgid ""
+"The problems start when individual users mark legitimate email as spam, most"
+" notably the company newsletter or correspondation they have opted in some "
+"time ago, but wish to no longer receive. Users tend to ignore the long-term "
+"effects of marking these message as spam, if at all they are aware of any, "
+"and just want such messages out of their way."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Common examples of the sort of messages that are often marked as spam while being legitimate traffic include:"
+msgid ""
+"Common examples of the sort of messages that are often marked as spam while "
+"being legitimate traffic include:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Newsletters, where users, rather then unsubscribe, mark legitimate messages as spam,"
+msgid ""
+"Newsletters, where users, rather then unsubscribe, mark legitimate messages "
+"as spam,"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notifications from social networks such as from Google+, Facebook, Twitter, etc., where users, rather then adjust their notification preferences, mark legitimate messages as spam,"
+msgid ""
+"Notifications from social networks such as from Google+, Facebook, Twitter, "
+"etc., where users, rather then adjust their notification preferences, mark "
+"legitimate messages as spam,"
msgstr ""
#. Tag: para
@@ -59,32 +85,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If enough users mark these messages as spam, the system will start to recognize these messages as spam, and other users may be prevented from receiving the same or similar messages in their INBOX."
+msgid ""
+"If enough users mark these messages as spam, the system will start to "
+"recognize these messages as spam, and other users may be prevented from "
+"receiving the same or similar messages in their INBOX."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<application>Amavis</application>, the default content filter performing anti-virus and anti-spam, wraps around <application>SpamAssassin</application> to achieve this flexibility."
+msgid ""
+"<application>Amavis</application>, the default content filter performing "
+"anti-virus and anti-spam, wraps around "
+"<application>SpamAssassin</application> to achieve this flexibility."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Separate Bayes database(s) can be created on a per-recipient and per-policy-bank <application>SpamAssassin</application> configuration files and SQL Bayes usernames."
+msgid ""
+"Separate Bayes database(s) can be created on a per-recipient and per-policy-"
+"bank <application>SpamAssassin</application> configuration files and SQL "
+"Bayes usernames."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Without over-complicating things, a common scenario sufficiently serving the anti-spam effort, includes the following aspects;"
+msgid ""
+"Without over-complicating things, a common scenario sufficiently serving the"
+" anti-spam effort, includes the following aspects;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A <code>shared/Spam</code> folder is created, with permissions for all users to lookup, read, and insert messages. It is the intention users move or copy messages they think are spam into this folder."
+msgid ""
+"A <code>shared/Spam</code> folder is created, with permissions for all users"
+" to lookup, read, and insert messages. It is the intention users move or "
+"copy messages they think are spam into this folder."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that, optionally, the permissions for users to maintain the 'seen' state of messages could not be granted, which in combination with <literal>sharedseen</literal> could provide a mechanism that would allow users to view which messages have been learned as spam in the past."
+msgid ""
+"Note that, optionally, the permissions for users to maintain the 'seen' "
+"state of messages could not be granted, which in combination with "
+"<literal>sharedseen</literal> could provide a mechanism that would allow "
+"users to view which messages have been learned as spam in the past."
msgstr ""
#. Tag: title
@@ -99,12 +143,16 @@ msgstr ""
#. Tag: screen
#, no-c-format
-msgid "$ <userinput>find /var/spool/imap/ -type d -name \"Spam\" -o -name \"Junk\"</userinput>"
+msgid ""
+"$ <userinput>find /var/spool/imap/ -type d -name \"Spam\" -o -name "
+"\"Junk\"</userinput>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finding all folders called \"Spam\" or \"Junk\" can potentially take a long time, depending on the size of the spool."
+msgid ""
+"Finding all folders called \"Spam\" or \"Junk\" can potentially take a long "
+"time, depending on the size of the spool."
msgstr ""
#. Tag: screen
@@ -114,12 +162,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<application>SpamAssassin</application> will not learn about messages it has learned about before. There's no requirement of purging or deleting the messages that <application>SpamAssassin</application> has learned about already, and purging or deleting those messages only helps to speed up the learning process run."
+msgid ""
+"<application>SpamAssassin</application> will not learn about messages it has"
+" learned about before. There's no requirement of purging or deleting the "
+"messages that <application>SpamAssassin</application> has learned about "
+"already, and purging or deleting those messages only helps to speed up the "
+"learning process run."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Do NOT delete the messages from the filesystem directly. Please refer to <xref linkend=\"sect-Administrator_Guide-Combating_Spam-Expiring_Messages_from_SpamHam_Shared_Folders\" /> for ways to purge, expire and/or delete messages from spam folders in a sustainable way."
+msgid ""
+"Do NOT delete the messages from the filesystem directly. Please refer to "
+"<xref linkend=\"sect-Administrator_Guide-Combating_Spam-"
+"Expiring_Messages_from_SpamHam_Shared_Folders\" /> for ways to purge, expire"
+" and/or delete messages from spam folders in a sustainable way."
msgstr ""
#. Tag: title
@@ -129,12 +186,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "As Bayes is only effective after it has learned about 200 messages, it is recommended to preseed the Bayes database with some high-quality ham and spam. Preseeding the Bayes database with some ham, and some spam, is done using the <emphasis>SpamAssassin Public Corpus</emphasis>. The public corpus consists of many messages qualified as ham and spam, collected from a variety of sources."
+msgid ""
+"As Bayes is only effective after it has learned about 200 messages, it is "
+"recommended to preseed the Bayes database with some high-quality ham and "
+"spam. Preseeding the Bayes database with some ham, and some spam, is done "
+"using the <emphasis>SpamAssassin Public Corpus</emphasis>. The public corpus"
+" consists of many messages qualified as ham and spam, collected from a "
+"variety of sources."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The SpamAssassin Public Corpus can be found at <ulink url=\"http://spamassassin.apache.org/publiccorpus/\" />."
+msgid ""
+"The SpamAssassin Public Corpus can be found at <ulink "
+"url=\"http://spamassassin.apache.org/publiccorpus/\" />."
msgstr ""
#. Tag: title
@@ -149,7 +214,8 @@ msgstr ""
#. Tag: screen
#, no-c-format
-msgid "# mkdir -p /tmp/salearn\n"
+msgid ""
+"# mkdir -p /tmp/salearn\n"
"# cd /tmp/salearn\n"
"# wget --recursive --timestamping --no-directories --level=1 --reject=gif,png,html,=A,=D http://spamassassin.apache.org/publiccorpus/"
msgstr ""
@@ -176,7 +242,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The total number of messages is about 7000. Learning about all of them may take quite a while. We recommend running the command in a screen."
+msgid ""
+"The total number of messages is about 7000. Learning about all of them may "
+"take quite a while. We recommend running the command in a screen."
msgstr ""
#. Tag: para
@@ -191,7 +259,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The total number of messages is about 2500. Learning about all of them may take quite a while. We recommend running the command in a screen."
+msgid ""
+"The total number of messages is about 2500. Learning about all of them may "
+"take quite a while. We recommend running the command in a screen."
msgstr ""
#. Tag: title
@@ -201,7 +271,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To learn about spam quickly, allow the Cyrus IMAP postuser to post into a shared folder that will be included in the regular <command>sa-learn</command> run."
+msgid ""
+"To learn about spam quickly, allow the Cyrus IMAP postuser to post into a "
+"shared folder that will be included in the regular <command>sa-"
+"learn</command> run."
msgstr ""
#. Tag: title
@@ -211,12 +284,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Set up the Cyrus IMAP postuser, using the <literal>postuser</literal> setting in <filename>/etc/imapd.conf</filename>."
+msgid ""
+"Set up the Cyrus IMAP postuser, using the <literal>postuser</literal> "
+"setting in <filename>/etc/imapd.conf</filename>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If, for example, the <literal>postuser</literal> is set to <literal>bb</literal>, the mail to <literal>bb+shared.blah</literal> will be delivered to the <literal>shared.blah</literal> folder."
+msgid ""
+"If, for example, the <literal>postuser</literal> is set to "
+"<literal>bb</literal>, the mail to <literal>bb+shared.blah</literal> will be"
+" delivered to the <literal>shared.blah</literal> folder."
msgstr ""
#. Tag: para
@@ -236,12 +314,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Submit / subscribe to known spam aggregators (search Google for \"free email offers\")"
+msgid ""
+"Submit / subscribe to known spam aggregators (search Google for \"free email"
+" offers\")"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Optionally, set the <literal>luser_relay</literal> option in Postfix, to trap all messages sent to non-existent recipients."
+msgid ""
+"Optionally, set the <literal>luser_relay</literal> option in Postfix, to "
+"trap all messages sent to non-existent recipients."
msgstr ""
#. Tag: title
@@ -251,22 +333,45 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bayes' score is dependent on the probability Bayes attaches of a message being spam. The rules used to match a message's probability of being spam are systematically prefixed with <literal>BAYES_</literal>, followed by the percentage of likelihood of the message being spam."
+msgid ""
+"Bayes' score is dependent on the probability Bayes attaches of a message "
+"being spam. The rules used to match a message's probability of being spam "
+"are systematically prefixed with <literal>BAYES_</literal>, followed by the "
+"percentage of likelihood of the message being spam."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Because there is rarely a 100% certainty of a message being spam, the highest percentage is 99%. By default, the configuration attaches a 3.5 score to this probability. Depending on the configuration value for <literal>$sa_tag2_level_deflt</literal> supplied in the Amavis configuration file, <literal>6.31</literal> by default, it is unlikely spam will reach the cut-off point of actually being marked as spam solely on the basis of Bayes' probability score."
+msgid ""
+"Because there is rarely a 100% certainty of a message being spam, the "
+"highest percentage is 99%. By default, the configuration attaches a 3.5 "
+"score to this probability. Depending on the configuration value for "
+"<literal>$sa_tag2_level_deflt</literal> supplied in the Amavis configuration"
+" file, <literal>6.31</literal> by default, it is unlikely spam will reach "
+"the cut-off point of actually being marked as spam solely on the basis of "
+"Bayes' probability score."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is therefor recommended to increase the score attached to messages with a 99% probability of being spam to at least <literal>6.308</literal>, if not simply <literal>6.31</literal>. Using <literal>6.308</literal>, you configure spam to be tagged not solely on the basis of Bayes' 99% probability score, but request that in addition the message is recognized to be in HTML (and HTML only), and perhaps uses a big font &ndash;or similar patterns with a very small <literal>0.01</literal> score."
+msgid ""
+"It is therefor recommended to increase the score attached to messages with a"
+" 99% probability of being spam to at least <literal>6.308</literal>, if not "
+"simply <literal>6.31</literal>. Using <literal>6.308</literal>, you "
+"configure spam to be tagged not solely on the basis of Bayes' 99% "
+"probability score, but request that in addition the message is recognized to"
+" be in HTML (and HTML only), and perhaps uses a big font &ndash;or similar "
+"patterns with a very small <literal>0.01</literal> score."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Some spam has been submitted through systems listed at <ulink url=\"http://dnswl.org\" />, a collaborative false positive protection mechanism, a default score of 1 is substracted from the total score. If this spam reaches you, consider increasing the score on <literal>BAYES_99</literal> with another one point."
+msgid ""
+"Some spam has been submitted through systems listed at <ulink "
+"url=\"http://dnswl.org\" />, a collaborative false positive protection "
+"mechanism, a default score of 1 is substracted from the total score. If this"
+" spam reaches you, consider increasing the score on "
+"<literal>BAYES_99</literal> with another one point."
msgstr ""
#. Tag: title
@@ -276,7 +381,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Edit <filename>/etc/mail/spamassassin/local.cf</filename>, and make sure the following line is present:"
+msgid ""
+"Edit <filename>/etc/mail/spamassassin/local.cf</filename>, and make sure the"
+" following line is present:"
msgstr ""
#. Tag: screen
@@ -301,17 +408,29 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is important to not just learn about spam, but learn about ham, legitimate email messages, as well. When not learning about ham, the anti-spam system will become heavily biased towards spam, and ultimately classify all email messages as such."
+msgid ""
+"It is important to not just learn about spam, but learn about ham, "
+"legitimate email messages, as well. When not learning about ham, the anti-"
+"spam system will become heavily biased towards spam, and ultimately classify"
+" all email messages as such."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Learning about ham follows a slightly different doctrine then learning about spam. Most importantly, ham is not to be posted to a shared folder that everyone else can read the contents from. It is most commonly a \"Not Junk\" or \"Ham\" folder in one's personal namespace users are instructed to copy or move messages to, that have been classified as spam but are actually ham."
+msgid ""
+"Learning about ham follows a slightly different doctrine then learning about"
+" spam. Most importantly, ham is not to be posted to a shared folder that "
+"everyone else can read the contents from. It is most commonly a \"Not Junk\""
+" or \"Ham\" folder in one's personal namespace users are instructed to copy "
+"or move messages to, that have been classified as spam but are actually ham."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is recommended users are both instructed to use ham folders, as well as create them by default &mdash;regardless whether they are called \"Ham\" or \"Not Junk\" or equivalent localized version of such."
+msgid ""
+"It is recommended users are both instructed to use ham folders, as well as "
+"create them by default &mdash;regardless whether they are called \"Ham\" or "
+"\"Not Junk\" or equivalent localized version of such."
msgstr ""
#. Tag: para
@@ -326,17 +445,29 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you share folders to which users can move or copy ham and/or spam messages, it is sensible to purge the contents of those folders regularly, or the folder size continues to increase indefinitely. Run the expiry after <command>sa-learn</command> has been run."
+msgid ""
+"When you share folders to which users can move or copy ham and/or spam "
+"messages, it is sensible to purge the contents of those folders regularly, "
+"or the folder size continues to increase indefinitely. Run the expiry after "
+"<command>sa-learn</command> has been run."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Running <command>ipurge</command> to purge mail folder messages occurs independent from setting <literal>expunge_mode</literal>, and independent from the <literal>expire</literal> annotation as well."
+msgid ""
+"Running <command>ipurge</command> to purge mail folder messages occurs "
+"independent from setting <literal>expunge_mode</literal>, and independent "
+"from the <literal>expire</literal> annotation as well."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Using the <literal>expire</literal> annotation is sufficient to purge the contents of the folder, as, with or without the <literal>expunge_mode</literal> setting having been set to delayed, rather then immediate, the Bayes database will only be updated with messages Bayes has not learned about before."
+msgid ""
+"Using the <literal>expire</literal> annotation is sufficient to purge the "
+"contents of the folder, as, with or without the "
+"<literal>expunge_mode</literal> setting having been set to delayed, rather "
+"then immediate, the Bayes database will only be updated with messages Bayes "
+"has not learned about before."
msgstr ""
#. Tag: para
@@ -346,7 +477,8 @@ msgstr ""
#. Tag: screen
#, no-c-format
-msgid "$ <userinput>/usr/lib/cyrus-imapd/ipurge -d 1 user/folder/name@domain.tld</userinput>\n"
+msgid ""
+"$ <userinput>/usr/lib/cyrus-imapd/ipurge -d 1 user/folder/name@domain.tld</userinput>\n"
"(...output abbreviated...)\n"
"$ <userinput>/usr/lib/cyrus-imapd/ipurge -i -d 1 user/folder/name@domain.tld</userinput>"
msgstr ""
@@ -358,22 +490,36 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "As part of the <application>SpamAssasin</application> package, a utility is provided to update the rulesets from channels configured."
+msgid ""
+"As part of the <application>SpamAssasin</application> package, a utility is "
+"provided to update the rulesets from channels configured."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For systems on which either of the SpamAssassin daemon or Amavis daemon is running, the software packages automatically install a nightly cronjob to ensure the rules are updated frequently."
+msgid ""
+"For systems on which either of the SpamAssassin daemon or Amavis daemon is "
+"running, the software packages automatically install a nightly cronjob to "
+"ensure the rules are updated frequently."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The spam rulesets are updated using the <command>sa-update</command> command, supplying one or more <literal>--channel</literal> options specifying the names of the ruleset channels to update, and (optionally) one or more <literal>--gpgkey</literal> options specifying the Pretty Good Privacy keys to allow signatures on the rulesets to have been signed with."
+msgid ""
+"The spam rulesets are updated using the <command>sa-update</command> "
+"command, supplying one or more <literal>--channel</literal> options "
+"specifying the names of the ruleset channels to update, and (optionally) one"
+" or more <literal>--gpgkey</literal> options specifying the Pretty Good "
+"Privacy keys to allow signatures on the rulesets to have been signed with."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The cronjob that is installed by default, executes <command>sa-update</command> for all channels defined in <filename>/etc/mail/spamassassin/channels.d/</filename> with one file per channel."
+msgid ""
+"The cronjob that is installed by default, executes <command>sa-"
+"update</command> for all channels defined in "
+"<filename>/etc/mail/spamassassin/channels.d/</filename> with one file per "
+"channel."
msgstr ""
#. Tag: title
@@ -383,7 +529,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If more then one system needs to make use of the Bayes database, consider using a network SQL Bayes database."
+msgid ""
+"If more then one system needs to make use of the Bayes database, consider "
+"using a network SQL Bayes database."
msgstr ""
#. Tag: title
@@ -398,7 +546,8 @@ msgstr ""
#. Tag: screen
#, no-c-format
-msgid "# mysql -e 'create database <emphasis>kolab_bayes</emphasis><footnote> <para>\n"
+msgid ""
+"# mysql -e 'create database <emphasis>kolab_bayes</emphasis><footnote> <para>\n"
" Replace with desired database name\n"
" </para>\n"
" </footnote>;'"
@@ -411,7 +560,8 @@ msgstr ""
#. Tag: screen
#, no-c-format
-msgid "# mysql -e \"CREATE USER '<emphasis>kolab_bayes</emphasis><footnote> <para>\n"
+msgid ""
+"# mysql -e \"CREATE USER '<emphasis>kolab_bayes</emphasis><footnote> <para>\n"
" Replace with desired username\n"
" </para>\n"
" </footnote>'@'%' IDENTIFIED BY PASSWORD '<emphasis>Welcome2KolabSystems</emphasis><footnote> <para>\n"
@@ -427,7 +577,8 @@ msgstr ""
#. Tag: screen
#, no-c-format
-msgid "# mysql -e \"GRANT USAGE ON * . * TO '<emphasis>kolab_bayes</emphasis><footnote> <para>\n"
+msgid ""
+"# mysql -e \"GRANT USAGE ON * . * TO '<emphasis>kolab_bayes</emphasis><footnote> <para>\n"
" Replace with desired username\n"
" </para>\n"
" </footnote>'@'%' IDENTIFIED BY PASSWORD '<emphasis>Welcome2KolabSystems</emphasis><footnote> <para>\n"
@@ -455,12 +606,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Download the latest Bayes Database SQL schema file from <ulink url=\"http://svn.apache.org/repos/asf/spamassassin/trunk/sql/bayes_mysql.sql\">bayes_mysql.sql</ulink> (when using MySQL):"
+msgid ""
+"Download the latest Bayes Database SQL schema file from <ulink "
+"url=\"http://svn.apache.org/repos/asf/spamassassin/trunk/sql/bayes_mysql.sql\">bayes_mysql.sql</ulink>"
+" (when using MySQL):"
msgstr ""
#. Tag: screen
#, no-c-format
-msgid "# wget <ulink url=\"http://svn.apache.org/repos/asf/spamassassin/trunk/sql/bayes_mysql.sql\" />"
+msgid ""
+"# wget <ulink "
+"url=\"http://svn.apache.org/repos/asf/spamassassin/trunk/sql/bayes_mysql.sql\""
+" />"
msgstr ""
#. Tag: para
@@ -470,7 +627,8 @@ msgstr ""
#. Tag: screen
#, no-c-format
-msgid "# mysql <emphasis>kolab_bayes</emphasis><footnote> <para>\n"
+msgid ""
+"# mysql <emphasis>kolab_bayes</emphasis><footnote> <para>\n"
" Replace with database name used.\n"
" </para>\n"
" </footnote> &lt; bayes_mysql.sql"
@@ -483,7 +641,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, export any existing Bayes databases, run the following command (on each server with a Bayes database):"
+msgid ""
+"First, export any existing Bayes databases, run the following command (on "
+"each server with a Bayes database):"
msgstr ""
#. Tag: screen
@@ -493,7 +653,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A recommended step, but completely optional, is to expire the current copy of the database:"
+msgid ""
+"A recommended step, but completely optional, is to expire the current copy "
+"of the database:"
msgstr ""
#. Tag: screen
@@ -503,12 +665,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Modify <filename>/etc/mail/spamassassin/local.cf</filename> to contain the following settings:"
+msgid ""
+"Modify <filename>/etc/mail/spamassassin/local.cf</filename> to contain the "
+"following settings:"
msgstr ""
#. Tag: screen
#, no-c-format
-msgid "bayes_store_module Mail::SpamAssassin::BayesStore::SQL\n"
+msgid ""
+"bayes_store_module Mail::SpamAssassin::BayesStore::SQL\n"
"bayes_sql_dsn DBI:mysql:<emphasis>kolab_bayes</emphasis><footnote> <para>\n"
" Replace with database name\n"
" </para>\n"
@@ -544,12 +709,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "For the purpose of troubleshooting, or in deployments with clients that have spam filtering capabilities, it is sensible to always insert the spam headers into email messages, both to avoid clients scanning the message again, as well as troubleshooting why mail may or may not have been filtered."
+msgid ""
+"For the purpose of troubleshooting, or in deployments with clients that have"
+" spam filtering capabilities, it is sensible to always insert the spam "
+"headers into email messages, both to avoid clients scanning the message "
+"again, as well as troubleshooting why mail may or may not have been "
+"filtered."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To always insert the spam score into the message headers, find the line in <filename>/etc/amavisd/amavisd.conf</filename> that starts with <literal>$sa_tag_level_deflt</literal> and replace it with:"
+msgid ""
+"To always insert the spam score into the message headers, find the line in "
+"<filename>/etc/amavisd/amavisd.conf</filename> that starts with "
+"<literal>$sa_tag_level_deflt</literal> and replace it with:"
msgstr ""
#. Tag: screen
@@ -559,17 +732,32 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "While the score is available from the log files should the level of logging verbosity have been increased, in some scenarios it is necessary to include the spam score regardless of the traffic being inbound or outbound. An example is a mail gateway for an unknown number of, or regularly changing, or dynamic, or large list of domain name spaces with both inbound and outbound traffic, which needs to be protected senders as well as receivers from spam."
+msgid ""
+"While the score is available from the log files should the level of logging "
+"verbosity have been increased, in some scenarios it is necessary to include "
+"the spam score regardless of the traffic being inbound or outbound. An "
+"example is a mail gateway for an unknown number of, or regularly changing, "
+"or dynamic, or large list of domain name spaces with both inbound and "
+"outbound traffic, which needs to be protected senders as well as receivers "
+"from spam."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Normally only inbound traffic is tagged &ndash;if at all&ndash;, by recognizing the recipient domain name space as local. The setting <literal>@local_domains</literal> or, in later versions of Amavis, <literal>@local_domains_acl</literal> is used."
+msgid ""
+"Normally only inbound traffic is tagged &ndash;if at all&ndash;, by "
+"recognizing the recipient domain name space as local. The setting "
+"<literal>@local_domains</literal> or, in later versions of Amavis, "
+"<literal>@local_domains_acl</literal> is used."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a default Kolab Groupware installation, the recipients are looked up in LDAP, and if an entry is found, Amavisd will also classify the domain as local &ndash; regardless of any <literal>@local_domains</literal> and/or <literal>@local_domains_acl</literal> setting."
+msgid ""
+"In a default Kolab Groupware installation, the recipients are looked up in "
+"LDAP, and if an entry is found, Amavisd will also classify the domain as "
+"local &ndash; regardless of any <literal>@local_domains</literal> and/or "
+"<literal>@local_domains_acl</literal> setting."
msgstr ""
#. Tag: title
@@ -579,7 +767,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To recognize all domain name spaces as local, edit <filename>/etc/amavisd/amavisd.conf</filename> and make sure the following settings are not configured:"
+msgid ""
+"To recognize all domain name spaces as local, edit "
+"<filename>/etc/amavisd/amavisd.conf</filename> and make sure the following "
+"settings are not configured:"
msgstr ""
#. Tag: para
@@ -629,7 +820,13 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The default behaviour shown in a Kolab Groupware deployment depends on the default settings that come with the packages delivered mostly through native, distribution-specific software repositories. This chapter documents various aspects of the behaviour Kolab Groupware will show referring to the appropriate settings that will allow a system administrator to modify the behaviour."
+msgid ""
+"The default behaviour shown in a Kolab Groupware deployment depends on the "
+"default settings that come with the packages delivered mostly through "
+"native, distribution-specific software repositories. This chapter documents "
+"various aspects of the behaviour Kolab Groupware will show referring to the "
+"appropriate settings that will allow a system administrator to modify the "
+"behaviour."
msgstr ""
#. Tag: title
@@ -639,7 +836,8 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Amavisd, by default, adds spam information headers only to messages that;"
+msgid ""
+"Amavisd, by default, adds spam information headers only to messages that;"
msgstr ""
#. Tag: para
@@ -649,12 +847,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Get a spam score over <literal>2.0</literal> from <application>SpamAssassin</application>."
+msgid ""
+"Get a spam score over <literal>2.0</literal> from "
+"<application>SpamAssassin</application>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The related setting is <literal>$sa_tag_level_deflt</literal> in <filename>/etc/amavisd/amavisd.conf</filename>."
+msgid ""
+"The related setting is <literal>$sa_tag_level_deflt</literal> in "
+"<filename>/etc/amavisd/amavisd.conf</filename>."
msgstr ""
#. Tag: title
@@ -664,12 +866,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The spam kill level controls which score spam must have been marked with before Amavisd considers the message to not be delivered to the intended recipient(s)."
+msgid ""
+"The spam kill level controls which score spam must have been marked with "
+"before Amavisd considers the message to not be delivered to the intended "
+"recipient(s)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Depending on your platform, the default for this score is <literal>6.31</literal> or <literal>6.9</literal>. When a message is marked with a spam score higher than or equal to this level, Amavisd will take \"evasive action\". See <xref linkend=\"sect-Administrator_Guide-Combating_Spam-Configuring_Amavis_Evasive_Action\" /> for more information on configuring evasive actions."
+msgid ""
+"Depending on your platform, the default for this score is "
+"<literal>6.31</literal> or <literal>6.9</literal>. When a message is marked "
+"with a spam score higher than or equal to this level, Amavisd will take "
+"\"evasive action\". See <xref linkend=\"sect-Administrator_Guide-"
+"Combating_Spam-Configuring_Amavis_Evasive_Action\" /> for more information "
+"on configuring evasive actions."
msgstr ""
#. Tag: title
@@ -679,7 +890,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can control what \"evasive action\" Amavisd takes using the <literal>$final_spam_destiny</literal> and <literal>$final_virus_destiny</literal> settings in <filename>/etc/amavisd/amavisd.conf</filename>. The default is usually to discard the message, but the following options are available:"
+msgid ""
+"You can control what \"evasive action\" Amavisd takes using the "
+"<literal>$final_spam_destiny</literal> and "
+"<literal>$final_virus_destiny</literal> settings in "
+"<filename>/etc/amavisd/amavisd.conf</filename>. The default is usually to "
+"discard the message, but the following options are available:"
msgstr ""
#. Tag: title
@@ -689,12 +905,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The message is accepted for delivery to the intended recipient(s), despite having been scored passed the kill or cutoff level, and regardless of bad content."
+msgid ""
+"The message is accepted for delivery to the intended recipient(s), despite "
+"having been scored passed the kill or cutoff level, and regardless of bad "
+"content."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend=\"form-Administrator_Guide-Configuring_Amavis_Evasive_Action-Configuring_Quarantine\" /> to learn how to configure the quarantine address."
+msgid ""
+"If a quarantine address has been configured, the quarantine address will "
+"receive a copy of the email. See <xref linkend=\"form-Administrator_Guide-"
+"Configuring_Amavis_Evasive_Action-Configuring_Quarantine\" /> to learn how "
+"to configure the quarantine address."
msgstr ""
#. Tag: title
@@ -704,7 +927,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The message is not accepted for delivery to the intended recipient(s). A Delivery Status Notification stating delivery failure is sent out to the sender."
+msgid ""
+"The message is not accepted for delivery to the intended recipient(s). A "
+"Delivery Status Notification stating delivery failure is sent out to the "
+"sender."
msgstr ""
#. Tag: title
@@ -714,7 +940,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The message is rejected by Amavisd, and while Amavisd sends out a 550 SMTP response to the Mail Transfer Agent, said Mail Transfer Agent is responsible for sending out the Delivery Status Notification, if any."
+msgid ""
+"The message is rejected by Amavisd, and while Amavisd sends out a 550 SMTP "
+"response to the Mail Transfer Agent, said Mail Transfer Agent is responsible"
+" for sending out the Delivery Status Notification, if any."
msgstr ""
#. Tag: title
@@ -724,7 +953,11 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The message is simply discarded by Amavisd. The sending Mail Transfer Agent will receive a positive SMTP delivery response, and Amavisd sends out no Delivery Status Notification, nor does it forward the message for delivery to the intended recipients."
+msgid ""
+"The message is simply discarded by Amavisd. The sending Mail Transfer Agent "
+"will receive a positive SMTP delivery response, and Amavisd sends out no "
+"Delivery Status Notification, nor does it forward the message for delivery "
+"to the intended recipients."
msgstr ""
#. Tag: title
@@ -734,16 +967,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Two separate quarantine forwarding addresses can be configured. One is for messages labeled as spam, another for messages suspected to contain a virus."
+msgid ""
+"Two separate quarantine forwarding addresses can be configured. One is for "
+"messages labeled as spam, another for messages suspected to contain a virus."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A catchall address for spam can be configured by setting the <literal>$spam_quarantine_to</literal> setting to a valid recipient address in <filename>/etc/amavisd/amavisd.conf</filename>"
+msgid ""
+"A catchall address for spam can be configured by setting the "
+"<literal>$spam_quarantine_to</literal> setting to a valid recipient address "
+"in <filename>/etc/amavisd/amavisd.conf</filename>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A catchall address for messages suspected of containing a virus can be configured by setting the <literal>$virus_quarantine_to</literal> setting to a valid recipient address in <filename>/etc/amavisd/amavisd.conf</filename>."
+msgid ""
+"A catchall address for messages suspected of containing a virus can be "
+"configured by setting the <literal>$virus_quarantine_to</literal> setting to"
+" a valid recipient address in "
+"<filename>/etc/amavisd/amavisd.conf</filename>."
msgstr ""
-
diff --git a/Administrator_Guide/ja-JP/Configuring_the_Kolab_Server.po b/Administrator_Guide/ja-JP/Configuring_the_Kolab_Server.po
index c414e3b..5f84810 100644
--- a/Administrator_Guide/ja-JP/Configuring_the_Kolab_Server.po
+++ b/Administrator_Guide/ja-JP/Configuring_the_Kolab_Server.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:45\n"
-"PO-Revision-Date: 2012-08-24T15:34:45\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
+"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -34,12 +37,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Web server performance is greatly improved by caching the interpreted bytecode for the PHP applications using the Alternative PHP Cache (APC) extension from PECL. With APC enabled, PHP source code is compiled only once (per retention interval), and subsequent inclusions for or execution of said PHP source code is obtained directly from cache."
+msgid ""
+"Web server performance is greatly improved by caching the interpreted "
+"bytecode for the PHP applications using the Alternative PHP Cache (APC) "
+"extension from PECL. With APC enabled, PHP source code is compiled only once"
+" (per retention interval), and subsequent inclusions for or execution of "
+"said PHP source code is obtained directly from cache."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To enable APC, install the <application>php-pecl-apc</application> package:"
+msgid ""
+"To enable APC, install the <application>php-pecl-apc</application> package:"
msgstr ""
#. Tag: screen
@@ -49,7 +58,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then, edit <filename>/etc/php.d/apc.ini</filename> and set or consider setting any of the following options;"
+msgid ""
+"Then, edit <filename>/etc/php.d/apc.ini</filename> and set or consider "
+"setting any of the following options;"
msgstr ""
#. Tag: title
@@ -69,17 +80,30 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Issue a <literal>stat()</literal> call to see if the file with PHP source code has changed since the last binary compilation. Disabling the <literal>stat()</literal> call is recommended for production environments, as calling <literal>stat()</literal> includes a write call to update the file's last access time (atime). Note that the update write call for the last access time can be prevented by mounting the relevant filesystem with the <literal>noatime</literal> option."
+msgid ""
+"Issue a <literal>stat()</literal> call to see if the file with PHP source "
+"code has changed since the last binary compilation. Disabling the "
+"<literal>stat()</literal> call is recommended for production environments, "
+"as calling <literal>stat()</literal> includes a write call to update the "
+"file's last access time (atime). Note that the update write call for the "
+"last access time can be prevented by mounting the relevant filesystem with "
+"the <literal>noatime</literal> option."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Changes to PHP Source Code Files with APC <literal>stat()</literal> Disabled"
+msgid ""
+"Changes to PHP Source Code Files with APC <literal>stat()</literal> Disabled"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that when APC is configured to not issue a <literal>stat()</literal> call to see if a PHP source code file is changed, changes to PHP source code files will only be included in subsequent execution after the APC cache has been cleared. The APC cache is cleared upon web server service reload, restart or using the PHP call <literal>apc_clear_cache()</literal>."
+msgid ""
+"Note that when APC is configured to not issue a <literal>stat()</literal> "
+"call to see if a PHP source code file is changed, changes to PHP source code"
+" files will only be included in subsequent execution after the APC cache has"
+" been cleared. The APC cache is cleared upon web server service reload, "
+"restart or using the PHP call <literal>apc_clear_cache()</literal>."
msgstr ""
#. Tag: title
@@ -89,7 +113,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When issuing a <literal>stat()</literal> call to see if the file with PHP source code has changed, use the file's change time attribute as opposed to the default, the file's modification time attribute."
+msgid ""
+"When issuing a <literal>stat()</literal> call to see if the file with PHP "
+"source code has changed, use the file's change time attribute as opposed to "
+"the default, the file's modification time attribute."
msgstr ""
#. Tag: title
@@ -99,7 +126,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "While overriding the expensive system calls issued during an <literal>include_once()</literal> or <literal>require_once()</literal> call be the PHP source code, this option MUST NOT be enabled. See <ulink url=\"https://bugzilla.kolabsys.com/show_bug.cgi?id=113\" /> for more information."
+msgid ""
+"While overriding the expensive system calls issued during an "
+"<literal>include_once()</literal> or <literal>require_once()</literal> call "
+"be the PHP source code, this option MUST NOT be enabled. See <ulink "
+"url=\"https://bugzilla.kolabsys.com/show_bug.cgi?id=113\" /> for more "
+"information."
msgstr ""
#. Tag: title
@@ -109,12 +141,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When using the <application>perl-Kolab</application> libraries on a system that is not a Kolab server itself, please be aware the perl-Kolab libraries expect and/or require certain settings to be available that are not really relevant for normal operations. This section explains which settings are expected and/or required, how to configure them and what the implications are."
+msgid ""
+"When using the <application>perl-Kolab</application> libraries on a system "
+"that is not a Kolab server itself, please be aware the perl-Kolab libraries "
+"expect and/or require certain settings to be available that are not really "
+"relevant for normal operations. This section explains which settings are "
+"expected and/or required, how to configure them and what the implications "
+"are."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An example use-case scenario &ndash;to install and use the Kolab perl libraries on a system that is not a Kolab server&ndash; is, where user provisioning scripts are executed outside of Kolab, and require interfacing with Kolab's IMAP server components to manage user or shared mailboxes."
+msgid ""
+"An example use-case scenario &ndash;to install and use the Kolab perl "
+"libraries on a system that is not a Kolab server&ndash; is, where user "
+"provisioning scripts are executed outside of Kolab, and require interfacing "
+"with Kolab's IMAP server components to manage user or shared mailboxes."
msgstr ""
#. Tag: title
@@ -124,12 +166,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The following is a snippet of the configuration file <filename>/etc/kolab/kolab.conf</filename> that prevents perl errors from being printed to <code>stderr</code>;"
+msgid ""
+"The following is a snippet of the configuration file "
+"<filename>/etc/kolab/kolab.conf</filename> that prevents perl errors from "
+"being printed to <code>stderr</code>;"
msgstr ""
#. Tag: screen
#, no-c-format
-msgid "kolab_usr: kolab\n"
+msgid ""
+"kolab_usr: kolab\n"
"kolab_musr: kolab\n"
"kolab_rusr: kolab\n"
"kolab_grp: kolab\n"
@@ -139,12 +185,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a traditional Kolab deployment, these settings are used with the configuration management utilities. On a server that is not a Kolab server, naturally the configuration management does not apply. However, the Kolab perl libraries still require these settings to be available for errors to be suppressed."
+msgid ""
+"In a traditional Kolab deployment, these settings are used with the "
+"configuration management utilities. On a server that is not a Kolab server, "
+"naturally the configuration management does not apply. However, the Kolab "
+"perl libraries still require these settings to be available for errors to be"
+" suppressed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Please see <ulink url=\"https://bugzilla.kolabsys.com/show_bug.cgi?id=114\" /> for more information."
+msgid ""
+"Please see <ulink url=\"https://bugzilla.kolabsys.com/show_bug.cgi?id=114\" "
+"/> for more information."
msgstr ""
#. Tag: title
@@ -164,11 +217,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The connection address for the Kolab perl libraries. Currently this is being used for IMAP connections."
+msgid ""
+"The connection address for the Kolab perl libraries. Currently this is being"
+" used for IMAP connections."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "See <ulink url=\"https://bugzilla.kolabsys.com/show_bug.cgi?id=112\">Bugzilla #112: <emphasis>Use of connect_addr, local_addr, bind_addr and bind_any</emphasis></ulink> and <ulink url=\"https://bugzilla.kolabsys.com/show_bug.cgi?id=115\">Bugzilla #115: <emphasis>NEW</emphasis></ulink> for more information."
+msgid ""
+"See <ulink "
+"url=\"https://bugzilla.kolabsys.com/show_bug.cgi?id=112\">Bugzilla #112: "
+"<emphasis>Use of connect_addr, local_addr, bind_addr and "
+"bind_any</emphasis></ulink> and <ulink "
+"url=\"https://bugzilla.kolabsys.com/show_bug.cgi?id=115\">Bugzilla #115: "
+"<emphasis>NEW</emphasis></ulink> for more information."
msgstr ""
-
diff --git a/Administrator_Guide/ja-JP/Detailed_Kolab_Server_Overview.po b/Administrator_Guide/ja-JP/Detailed_Kolab_Server_Overview.po
index 8092103..364f39a 100644
--- a/Administrator_Guide/ja-JP/Detailed_Kolab_Server_Overview.po
+++ b/Administrator_Guide/ja-JP/Detailed_Kolab_Server_Overview.po
@@ -1,16 +1,19 @@
-#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
+# Translators:
msgid ""
msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2012-08-24T15:34:45\n"
-"PO-Revision-Date: 2012-08-24T15:34:45\n"
+"Project-Id-Version: Kolab Groupware Solution\n"
+"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
+"POT-Creation-Date: 2012-08-24T15:41:52\n"
+"PO-Revision-Date: 2012-08-13 13:17+0000\n"
"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/kolab/language/ja/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0\n"
#. Tag: title
#, no-c-format
@@ -19,7 +22,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Kolab Server consists of various 3rd-party OpenSource components as well as some kolab specific components which provide the glue between those. Most of the 3rd-party components can be exchanged, such as the IMAP-Server."
+msgid ""
+"The Kolab Server consists of various 3rd-party OpenSource components as well"
+" as some kolab specific components which provide the glue between those. "
+"Most of the 3rd-party components can be exchanged, such as the IMAP-Server."
msgstr ""
#. Tag: title
@@ -34,7 +40,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Postfix is an <emphasis>MTA</emphasis> (Mail Transfer Agent), responsible for the transport and distribution of emails."
+msgid ""
+"Postfix is an <emphasis>MTA</emphasis> (Mail Transfer Agent), responsible "
+"for the transport and distribution of emails."
msgstr ""
#. Tag: para
@@ -44,7 +52,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Documentation: <ulink url=\"http://www.postfix.org/documentation.html\">Postfix Documentation</ulink>"
+msgid ""
+"Documentation: <ulink "
+"url=\"http://www.postfix.org/documentation.html\">Postfix "
+"Documentation</ulink>"
msgstr ""
#. Tag: title
@@ -94,12 +105,14 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<filename>/etc/postfix/ldap/virtual_alias_maps_mailenabled_distgroups.cf</filename>"
+msgid ""
+"<filename>/etc/postfix/ldap/virtual_alias_maps_mailenabled_distgroups.cf</filename>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<filename>/etc/postfix/ldap/virtual_alias_maps_mailenabled_dynamic_distgroups.cf</filename>"
+msgid ""
+"<filename>/etc/postfix/ldap/virtual_alias_maps_mailenabled_dynamic_distgroups.cf</filename>"
msgstr ""
#. Tag: title
@@ -129,7 +142,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <application>Cyrus-IMAP</application> server is a scalable, fast IMAP server."
+msgid ""
+"The <application>Cyrus-IMAP</application> server is a scalable, fast IMAP "
+"server."
msgstr ""
#. Tag: para
@@ -139,7 +154,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Documentation: <ulink url=\"http://www.cyrusimap.org/docs/cyrus-imapd/\">Cyrus Documentation</ulink>"
+msgid ""
+"Documentation: <ulink url=\"http://www.cyrusimap.org/docs/cyrus-"
+"imapd/\">Cyrus Documentation</ulink>"
msgstr ""
#. Tag: para
@@ -169,7 +186,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "LDAP is the directory services used to store information about users as well as parts of the Kolab configuration. The service consists of the <application>slapd</application> deamon, which provides access to the directory. <application>slurpd</application> is a replication deamon for the LDAP database, allowing the system to be distributed over several machines which increases relaiability as well as availability. <application>slurpd</application> is replaced by <application>syncrepl</application> as of version 3.0."
+msgid ""
+"LDAP is the directory services used to store information about users as well"
+" as parts of the Kolab configuration. The service consists of the "
+"<application>slapd</application> deamon, which provides access to the "
+"directory. <application>slurpd</application> is a replication deamon for the"
+" LDAP database, allowing the system to be distributed over several machines "
+"which increases relaiability as well as availability. "
+"<application>slurpd</application> is replaced by "
+"<application>syncrepl</application> as of version 3.0."
msgstr ""
#. Tag: para
@@ -179,7 +204,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Documentation: <ulink url=\"http://www.openldap.org/doc/admin24/\">OpenLDAP admin guide</ulink>"
+msgid ""
+"Documentation: <ulink url=\"http://www.openldap.org/doc/admin24/\">OpenLDAP "
+"admin guide</ulink>"
msgstr ""
#. Tag: para
@@ -199,7 +226,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "SASL (Simple Authentication and Security Layer) is a method to add authentication support for connection based protocols. The authentication via SASL is used by Postfix and the IMAP-Server. <application>saslauthd</application> is the deamon providing the authentication, using the credentials stored in the LDAP database."
+msgid ""
+"SASL (Simple Authentication and Security Layer) is a method to add "
+"authentication support for connection based protocols. The authentication "
+"via SASL is used by Postfix and the IMAP-Server. "
+"<application>saslauthd</application> is the deamon providing the "
+"authentication, using the credentials stored in the LDAP database."
msgstr ""
#. Tag: para
@@ -219,7 +251,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<application>Amavisd</application> is an emailscanner, which unpacks all messages (including attachments) and forwards them to virus scanners and spam filters."
+msgid ""
+"<application>Amavisd</application> is an emailscanner, which unpacks all "
+"messages (including attachments) and forwards them to virus scanners and "
+"spam filters."
msgstr ""
#. Tag: para
@@ -234,7 +269,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "<application>ClamAV</application> is a virus scanner, suitable for Mailservers."
+msgid ""
+"<application>ClamAV</application> is a virus scanner, suitable for "
+"Mailservers."
msgstr ""
#. Tag: para
@@ -304,7 +341,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Apart from the main components, consisting of proven 3rd-party OpenSource software, there are also some Kolab specific software components."
+msgid ""
+"Apart from the main components, consisting of proven 3rd-party OpenSource "
+"software, there are also some Kolab specific software components."
msgstr ""
#. Tag: title
@@ -314,7 +353,10 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Kolab-Daemon is the central control unit between the various components. It is responsible for synchronizing the user accounts in the LDAP directory with the available IMAP folders. TODO: further responsabilites of kolabd"
+msgid ""
+"The Kolab-Daemon is the central control unit between the various