paul@7 | 1 | Template: kolab-conf/title-imap |
paul@7 | 2 | Type: title |
paul@7 | 3 | _Description: Configuring Kolab IMAP settings |
paul@7 | 4 | |
paul@7 | 5 | Template: kolab-conf/imap-server-selection |
paul@7 | 6 | Type: string |
paul@7 | 7 | _Description: Select an IMAP URI: |
paul@7 | 8 | Please indicate the IMAP server to be used by the Kolab |
paul@7 | 9 | components. (If this is a remote server, no attempt will |
paul@7 | 10 | be made to set up server instances or to configure |
paul@7 | 11 | services.) |
paul@7 | 12 | |
paul@14 | 13 | Template: kolab-conf/title-mta |
paul@14 | 14 | Type: title |
paul@14 | 15 | _Description: Configuring Kolab MTA settings |
paul@14 | 16 | |
paul@14 | 17 | Template: kolab-conf/ssl-certificate-selection |
paul@14 | 18 | Type: string |
paul@14 | 19 | _Description: Certificate name: |
paul@14 | 20 | Please indicate the name of the certificate to be used |
paul@14 | 21 | by Postfix. If this is a new certificate, an attempt |
paul@14 | 22 | will be made to create it. Note that this should be only |
paul@14 | 23 | a simple name like "localhost" or "ssl-cert-snakeoil", |
paul@14 | 24 | not a filename or pathname. |
paul@14 | 25 | |
paul@0 | 26 | Template: kolab-conf/title-ldap |
paul@0 | 27 | Type: title |
paul@0 | 28 | _Description: Configuring Kolab LDAP settings |
paul@0 | 29 | |
paul@15 | 30 | Template: kolab-conf/ldap-setup-skipped |
paul@15 | 31 | Type: note |
paul@15 | 32 | _Description: Skipping setup of LDAP, as specified: |
paul@15 | 33 | An explicit request to skip LDAP setup was made. |
paul@15 | 34 | |
paul@15 | 35 | Template: kolab-conf/ldap-system-conflict |
paul@15 | 36 | Type: note |
paul@15 | 37 | _Description: Conflicting LDAP system configuration: |
paul@15 | 38 | You cannot configure Kolab to run against OpenLDAP and |
paul@15 | 39 | Active Directory simultaneously. |
paul@15 | 40 | |
paul@15 | 41 | Template: kolab-conf/ldap-setup-in-progress |
paul@15 | 42 | Type: note |
paul@15 | 43 | _Description: LDAP setup in progress: |
paul@15 | 44 | Setup is now going to set up the 389 Directory Server. |
paul@15 | 45 | This may take a little while (during which period there is |
paul@15 | 46 | no output and no progress indication). |
paul@15 | 47 | |
paul@0 | 48 | Template: kolab-conf/ldap-server-selection |
paul@0 | 49 | Type: string |
paul@0 | 50 | _Description: Select an LDAP URI: |
paul@0 | 51 | Please indicate the LDAP server to be used by the Kolab |
paul@3 | 52 | components. (If this is a remote server, no attempt will |
paul@0 | 53 | be made to set up server instances or to configure services, |
paul@0 | 54 | but the indicated server instance will be populated with |
paul@0 | 55 | Kolab settings.) |
paul@0 | 56 | |
paul@0 | 57 | Template: kolab-conf/ldap-server-population |
paul@0 | 58 | Type: boolean |
paul@0 | 59 | _Description: Populate the LDAP server: |
paul@0 | 60 | A different host is being used for LDAP services. Do you |
paul@0 | 61 | want to populate the directory on this remote host? |
paul@0 | 62 | |
paul@0 | 63 | Template: kolab-conf/ldap-instances-found-available |
paul@0 | 64 | Type: note |
paul@0 | 65 | _Description: Existing directory instances found: |
paul@6 | 66 | It seems the directory server has an existing instance |
paul@0 | 67 | configured and that this instance is available using the |
paul@0 | 68 | stored credentials. |
paul@0 | 69 | . |
paul@0 | 70 | To change the Kolab configuration information, should you |
paul@0 | 71 | wish to do so, run the following command: |
paul@0 | 72 | . |
paul@0 | 73 | setup-kolab -S ldap --reset-ldap-config |
paul@0 | 74 | . |
paul@0 | 75 | If the intention is to start with a fresh directory, please |
paul@0 | 76 | make sure that /etc/dirsrv/ and /var/lib/dirsrv/ are clean |
paul@0 | 77 | so that this configuration process can be performed in |
paul@0 | 78 | full. |
paul@0 | 79 | |
paul@0 | 80 | Template: kolab-conf/ldap-instances-found-unavailable |
paul@0 | 81 | Type: note |
paul@0 | 82 | _Description: Existing directory instances found: |
paul@6 | 83 | It seems the directory server has an existing instance |
paul@0 | 84 | configured but that this instance is not available using |
paul@0 | 85 | the stored credentials. |
paul@0 | 86 | . |
paul@0 | 87 | To update the Kolab configuration with appropriate |
paul@0 | 88 | information, run the following command: |
paul@0 | 89 | . |
paul@0 | 90 | setup-kolab -S ldap --reset-ldap-config |
paul@0 | 91 | . |
paul@0 | 92 | If the intention is to start with a fresh directory, please |
paul@0 | 93 | make sure that /etc/dirsrv/ and /var/lib/dirsrv/ are clean |
paul@0 | 94 | so that this configuration process can be performed in |
paul@0 | 95 | full. |
paul@0 | 96 | |
paul@0 | 97 | Template: kolab-conf/ldap-directory-not-changed |
paul@0 | 98 | Type: note |
paul@0 | 99 | _Description: Existing directory not changed: |
paul@0 | 100 | No further LDAP configuration will be performed due to |
paul@0 | 101 | the presence of existing directory information. Only the |
paul@0 | 102 | Kolab configuration file has been updated. |
paul@0 | 103 | |
paul@0 | 104 | Template: kolab-conf/ldap-setup-error |
paul@0 | 105 | Type: note |
paul@0 | 106 | _Description: Error during LDAP setup: |
paul@0 | 107 | An error was detected in the setup procedure for the |
paul@0 | 108 | directory server. This process will write the error and |
paul@0 | 109 | output information to /var/log/kolab/setup.error.log and |
paul@0 | 110 | /var/log/kolab/setup.out.log respectively. |
paul@0 | 111 | |
paul@0 | 112 | Template: kolab-conf/ldap-admin |
paul@0 | 113 | Type: password |
paul@0 | 114 | _Description: Administrator password for the directory server: |
paul@0 | 115 | Please supply a password for the LDAP administrator user |
paul@0 | 116 | 'admin', used to login to the graphical console of 389 |
paul@0 | 117 | Directory server. |
paul@0 | 118 | |
paul@0 | 119 | Template: kolab-conf/ldap-manager |
paul@0 | 120 | Type: password |
paul@0 | 121 | _Description: Directory manager password for the directory server: |
paul@0 | 122 | Please supply a password for the LDAP Directory Manager |
paul@0 | 123 | user, which is the administrator user you will be using |
paul@0 | 124 | to at least initially log in to the Web Admin, and that |
paul@0 | 125 | Kolab uses to perform administrative tasks. |
paul@0 | 126 | |
paul@0 | 127 | Template: kolab-conf/dirsrv-user |
paul@0 | 128 | Type: string |
paul@0 | 129 | _Description: User to run the directory server: |
paul@0 | 130 | Please choose the system user the directory service should |
paul@0 | 131 | use to run under. It should be an existing, unprivileged, |
paul@0 | 132 | local system POSIX account with no shell. |
paul@0 | 133 | |
paul@0 | 134 | Template: kolab-conf/dirsrv-group |
paul@0 | 135 | Type: string |
paul@0 | 136 | _Description: Group to run the directory server: |
paul@0 | 137 | Please choose the system group the directory service should |
paul@0 | 138 | use to run under. |
paul@0 | 139 | |
paul@0 | 140 | Template: kolab-conf/kolab-domain-namespace |
paul@0 | 141 | Type: string |
paul@0 | 142 | _Description: Domain namespace to use for Kolab: |
paul@0 | 143 | This setup procedure plans to set up Kolab Groupware for |
paul@0 | 144 | the following domain name space. This domain name is |
paul@0 | 145 | obtained from the reverse DNS entry on your network |
paul@0 | 146 | interface. Please confirm this is the appropriate domain |
paul@0 | 147 | name space. |
paul@0 | 148 | |
paul@0 | 149 | Template: kolab-conf/kolab-root-dn |
paul@0 | 150 | Type: string |
paul@0 | 151 | _Description: Root dn to use for Kolab: |
paul@0 | 152 | The standard root dn we composed for you as follows. |
paul@0 | 153 | Please confirm this is the root dn you wish to use. |
paul@0 | 154 | |
paul@0 | 155 | Template: kolab-conf/cyrus-admin |
paul@0 | 156 | Type: password |
paul@0 | 157 | _Description: Cyrus administrator password: |
paul@0 | 158 | Please supply a Cyrus administrator password. This |
paul@0 | 159 | password is used by Kolab to execute administrative |
paul@0 | 160 | tasks in Cyrus IMAP. You may also need the password |
paul@0 | 161 | yourself to troubleshoot Cyrus IMAP and/or perform |
paul@0 | 162 | other administrative tasks against Cyrus IMAP directly. |
paul@0 | 163 | |
paul@0 | 164 | Template: kolab-conf/ldap-kolab-service |
paul@0 | 165 | Type: password |
paul@0 | 166 | _Description: Kolab service password for the directory server: |
paul@0 | 167 | Please supply a Kolab service account password. This |
paul@0 | 168 | account is used by various services such as Postfix, |
paul@0 | 169 | and Roundcube, as anonymous binds to the LDAP server |
paul@0 | 170 | will not be allowed. |
paul@0 | 171 | |
paul@0 | 172 | Template: kolab-conf/title-mysql |
paul@0 | 173 | Type: title |
paul@0 | 174 | _Description: Configuring MySQL for Kolab use |
paul@0 | 175 | |
paul@0 | 176 | Template: kolab-conf/mysql-kolab |
paul@0 | 177 | Type: password |
paul@0 | 178 | _Description: Kolab database access password: |
paul@0 | 179 | Please supply a password for the MySQL user 'kolab'. |
paul@0 | 180 | This password will be used by Kolab services, such as |
paul@0 | 181 | the Web Administration Panel. |
paul@0 | 182 | |
paul@0 | 183 | Template: kolab-conf/mysql-root-new |
paul@0 | 184 | Type: password |
paul@0 | 185 | _Description: New MySQL root password: |
paul@0 | 186 | Please supply a root password for MySQL. This password |
paul@0 | 187 | will be the administrative user for this MySQL server, |
paul@0 | 188 | and it should be kept a secret. After this setup process |
paul@0 | 189 | has completed, Kolab is going to discard and forget |
paul@0 | 190 | about this password, but you will need it for |
paul@0 | 191 | administrative tasks in MySQL. |
paul@0 | 192 | |
paul@0 | 193 | Template: kolab-conf/mysql-root-existing |
paul@0 | 194 | Type: password |
paul@0 | 195 | _Description: Current MySQL root password: |
paul@0 | 196 | Please supply the root password for MySQL, so we can set |
paul@0 | 197 | up user accounts for other components that use MySQL. |
paul@0 | 198 | |
paul@0 | 199 | Template: kolab-conf/title-php |
paul@0 | 200 | Type: title |
paul@0 | 201 | _Description: Configuring PHP for Kolab use |
paul@0 | 202 | |
paul@0 | 203 | Template: kolab-conf/php-timezone |
paul@0 | 204 | Type: string |
paul@0 | 205 | _Description: Timezone to be used by PHP: |
paul@0 | 206 | Please supply the region-based timezone PHP should be using. |
paul@0 | 207 | You have to use a continent or 'country/city' locality name |
paul@0 | 208 | like 'Europe/Berlin'. Conventional time zones such as CEST |
paul@0 | 209 | are not acceptable. |
paul@0 | 210 | |
paul@0 | 211 | Template: kolab-conf/title-roundcube |
paul@0 | 212 | Type: title |
paul@0 | 213 | _Description: Configuring Roundcube to use Kolab |
paul@0 | 214 | |
paul@0 | 215 | Template: kolab-conf/roundcube-password |
paul@0 | 216 | Type: password |
paul@0 | 217 | _Description: Roundcube database access password: |
paul@0 | 218 | Please supply a password for the MySQL user 'roundcube'. |
paul@0 | 219 | This password will be used by the Roundcube webmail |
paul@0 | 220 | interface. |
paul@3 | 221 | |
paul@8 | 222 | Template: kolab-conf/smtp-server-selection |
paul@8 | 223 | Type: string |
paul@8 | 224 | _Description: Select an SMTP server host: |
paul@8 | 225 | Please indicate the SMTP server to be used by the Kolab |
paul@8 | 226 | components. (If this is a remote server, no attempt will |
paul@8 | 227 | be made to set up server instances or to configure |
paul@8 | 228 | services.) |
paul@8 | 229 | |
paul@11 | 230 | Template: kolab-conf/title-converse |
paul@11 | 231 | Type: title |
paul@11 | 232 | _Description: Configuring Converse to use Kolab |
paul@11 | 233 | |
paul@3 | 234 | Template: kolab-conf/xmpp-bind-server |
paul@3 | 235 | Type: string |
paul@3 | 236 | _Description: Select an XMPP server bind URI: |
paul@3 | 237 | Please indicate the location of the bind server providing |
paul@3 | 238 | access to the XMPP server to be used by Converse. |
paul@3 | 239 | . |
paul@3 | 240 | If this is a remote server, a proxy will be set up to allow |
paul@3 | 241 | users to connect to it. |
paul@11 | 242 | |
paul@11 | 243 | Template: kolab-conf/xmpp-proxy-server |
paul@11 | 244 | Type: string |
paul@11 | 245 | _Description: Select an XMPP server proxy URI: |
paul@11 | 246 | Please indicate the location of the proxy server providing |
paul@11 | 247 | access to the XMPP server to be used by Converse. |
paul@11 | 248 | . |
paul@11 | 249 | You can leave this empty to insist that the bind URI is |
paul@11 | 250 | reachable from Web applications served by this host. |