summaryrefslogtreecommitdiff
path: root/Architecture_and_Design/nl-NL/Kolab_Server_Overview.po
blob: cf317a9381696fc78aef2b94fe887b44942b7050 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
# AUTHOR <EMAIL@ADDRESS>, YEAR.
# 
# Translators:
msgid ""
msgstr ""
"Project-Id-Version: Kolab Groupware Solution\n"
"Report-Msgid-Bugs-To: https://isues.kolab.org/\n"
"POT-Creation-Date: 2012-11-20T12:52:22\n"
"PO-Revision-Date: 2012-08-13 13:33+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: Dutch (http://www.transifex.com/projects/p/kolab/language/nl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: nl\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Tag: title
#, no-c-format
msgid "Kolab Server Overview"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"This chapter provides an overview of the architecture of the Kolab Groupware"
" server. <xref linkend=\"figu-Architecture_and_Design-Kolab_Server_Overview-"
"Primary_Components_of_the_Kolab_Server\" /> illustrates the following "
"primary functional components that make up a Kolab Groupware server "
"deployment:"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Authentication and Authorization Database"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The authentication database is the canonical source for information about "
"users and groups, and is used to authenticate and authorize users "
"&ndash;among other things. Traditionally, Kolab Groupware has been designed "
"based on LDAP specific capabilities &ndash;more specifically, in fact, it "
"has been based on OpenLDAP specific capabilities&ndash; but virtually any "
"authentication and authorization method and/or technology is eligible to "
"work for Kolab, including, but not limited to;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Kerberos (v5)"
msgstr ""

#. Tag: para
#, no-c-format
msgid "LDAP"
msgstr ""

#. Tag: para
#, no-c-format
msgid "MySQL"
msgstr ""

#. Tag: para
#, no-c-format
msgid "PAM"
msgstr ""

#. Tag: para
#, no-c-format
msgid "PostgreSQL"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Shadow"
msgstr ""

#. Tag: para
#, no-c-format
msgid "SQLite(3)"
msgstr ""

#. Tag: title
#, no-c-format
msgid "(Web) Administration"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The optional web administration panel allows users and administrators to "
"control certain aspects relevant to Kolab Groupware. For example, this "
"includes folder subscriptions, authorization on folders, password "
"management, mobile device management, and more."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Most of the components in the web administration panel are subject to the "
"user's authorization."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Mail Exchanger"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Mail exchangers are responsible for the exchange of email messages between "
"nodes, as well as the exchange of email messages between services."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Functionally, mail exchangers can be categorized using the following "
"environment specific implementation characteristics;"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Backend Mail Exchanger"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"A backend mail exchanger typically installed on an IMAP backend server and "
"is used for two primary purposes; to enable, having received a message for "
"one or more recipients on the backend IMAP server in question, one-shot "
"delivery through LMTP, and to generate the backscatter (non-delivery "
"reports, LMTP related errors)."
msgstr ""

#. Tag: title
#, no-c-format
msgid "External Mail Exchanger"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"An external mail exchanger is tasked with the exchange of email messages "
"with external, 3rd parties. Typically, both email messages received from as "
"well as sent to external sources passes through external mail exchangers."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Internal Mail Exchanger"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Internal mail exchangers are the core of an environment with multiple "
"authentication- and/or authorization databases, and/or with multiple IMAP "
"backend servers. Typically, internal mail exchangers relay email messages to"
" the correct backend server, regardless of whether the backend server is a "
"Microsoft Exchange SMTP bridgehead server, a Kolab IMAP backend server, or a"
" external mail exchanger."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The level in which each of the aforementioned types of mail exchangers are "
"relevant functional components in a certain deployment scenario depends on "
"the desired functionality of the architecture, as well as the available "
"resources in order to implement such functionality."
msgstr ""

#. Tag: title
#, no-c-format
msgid "IMAP Server"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The IMAP server is primarily responsible for mailbox storage, distribution "
"and access control."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To assist in the creation, modification and deletion of mailboxes, Kolab "
"includes a daemon."
msgstr ""

#. Tag: title
#, no-c-format
msgid "(Web) Client"
msgstr ""

#. Tag: para
#, no-c-format
msgid "TODO"
msgstr ""

#. Tag: title
#, no-c-format
msgid "(Web) Client does not include Smart Clients"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Although the (web) client software will need to have capabilities similar to"
" those of a Smart Client, the distinction between (web) client software and "
"smart clients like Kontact or Outlook is the latter two are not considered "
"server components. There may be other server applications that act as a "
"Kolab Groupware client."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Primary Components of the Kolab Server"
msgstr ""

#. Tag: title
#, no-c-format
msgid ""
"Functional Requirements of the Authentication &amp; Authorization Database"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"There is a certain minimal amount of information that Kolab requires to be "
"available in any authentication database, such as the credentials that need "
"to be supplied by a client in order to verify the identity of the user. "
"Which details of those credentials are stored in the authentication database"
" very much depends on the authentication technology used. For a Kerberos "
"(v5) deployment for example, the username and realm would suffice (the "
"ticket is verified with the KDC, and no password exchange is required). For "
"an LDAP deployment however, any unique attribute value, or part thereof, "
"within the search scope may be used in combination with the password needed "
"for a fast-bind operation."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"It is worth noting that ultimately, all authentication is based on one or "
"more shared secrets. In Kerberos, those shared secrets are called keytabs, "
"and with LDAP, MySQL and PAM for example, this is the user's password. As "
"all authentication is based on the principle of sharing a secret, the "
"exchange and verification of the shared secret is crucial to the "
"architecture of an infrastructure using any of the aforementioned "
"authentication technologies."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Authorization for a user can be separate from the authentication. For "
"example, user <literal>john@doe.org</literal> can be authorized as "
"<literal>john.doe@example.org</literal>, or even "
"<literal>max.imum@example.org</literal> if necessary. Additionally, groups "
"of users are often used as a simple way of authorizing larger numbers of "
"users."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Functional Requirements of the (Web) Administration"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Functional Requirements of the Mail Exchanger"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Positioning"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Role definition"
msgstr ""

#. Tag: para
#, no-c-format
msgid "High Availability"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Load Balancing"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Efficient and cost-effective"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Free Software"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Content Filtering"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Functional Requirements of the IMAP Server"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Functional Requirements for the (Web) Client"
msgstr ""