summaryrefslogtreecommitdiff
path: root/Architecture_and_Design/de-DE/Kolab_SMTP_Access_Policy.po
blob: 500e63b2a6d88cd14a39628903249811eb646492 (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
# 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-09-08T14:57:34\n"
"PO-Revision-Date: 2012-08-13 13:33+0000\n"
"Last-Translator: Automatically generated\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: de\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Tag: title
#, no-c-format
msgid "Kolab SMTP Access Policy"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The Kolab SMTP Access Policy is a policy service for Postfix that applies "
"mandatory recipient and sender address access controls using the <ulink "
"url=\"http://www.postfix.org/SMTPD_POLICY_README.html\">Postfix SMTPD "
"Policy</ulink>."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"It verifies envelope sender address used in the message against the "
"authentication and authorization database."
msgstr ""

#. Tag: title
#, no-c-format
msgid "What the Kolab SMTP Access Policy is"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The policy service is the implementation of a fine-grained mandatory access "
"control system, that allows delegates to be appointed authorization to use "
"one's email address(es) as the envelope sender address for messages the "
"delegates send, and/or allows an administrator &ndash;or individual, if "
"you'll permit this through custom ACI&ndash; to configure a user account to "
"be restricted access to receive from and/or send to only individual "
"addresses, groups, group members, domain name spaces, and groups of domain "
"name spaces."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"As such, a corporate board or directors for example, may have a distribution"
" group 'board@example.com' to which only the members of the board of "
"directors are allowed to send messages, but no-one else."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Note that this is slightly different from a mailing list such as implemented"
" with Majordomo or Mailman. While these technologies could require approved,"
" subscription-based submission of messages even though in a more enhanced "
"fashion, the subscribers list to such a mailing list is not based on LDAP "
"group membership, organizational unit orientation, roles, queries or "
"otherwise related to regular user provisioning and"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Similarly, each of the board members may authorize assisting personal to "
"respond to email using their own envelope sender address. Here's how that "
"works:"
msgstr ""

#. Tag: title
#, no-c-format
msgid "John Doe, the Chief Executive Officer"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"John has a lovely secretary called Lucy. John allows Lucy to read and write "
"to John's Calendar, and opens up his INBOX folder to Lucy for read-only "
"access."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"John however, being a CEO and all that, tends to be unable to regularly read"
" his email and take the time to respond. Internet is only free of charge "
"half an hour a time, twice, at Schiphol. John would like Lucy to be able to "
"respond on his behalf (especially to those invitations for random events a "
"CEO has little interest in). John therefor authorizes Lucy to \"send on "
"behalf of\". This is considered a Kolab Delegate -future enhancements "
"notwithstanding."
msgstr ""

#. Tag: para
#, no-c-format
msgid "In LDAP, this would look as follows:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"dn: uid=doe,ou=People,dc=example,dc=com\n"
"cn: John Doe\n"
"(...)\n"
"mail: john.doe@example.com\n"
"(...)\n"
"kolabDelegate: uid=meier,ou=People,dc=example,dc=com\n"
"(...)"
msgstr ""

#. Tag: title
#, no-c-format
msgid "What the Kolab SMTP Access Policy is not"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The Kolab SMTP Access Policy applies access control between senders and "
"recipients on an individual, per-entity basis. It can be used to restrict an"
" individual user from receiving from or sending to other recipients or "
"senders, including entire domain name spaces, but it does not apply a global"
" blacklist/whitelist mechanism."
msgstr ""

#. Tag: title
#, no-c-format
msgid "When?"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The Kolab SMTP Access Policy needs to be executed in desired points in a "
"mail-flow."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"A typical deployment executes the Kolab SMTP Access Policy upon receiving "
"messages, or in other words, in <application>smtpd</application> and "
"<application>submission</application>. The submission part is the most "
"illustrative of why the Kolab SMTP Access Policy works the way it does."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Kolab SMTP Access Policy in Action During Submission"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The submission of a new email by a user of Kolab Groupware has the following"
" three interesting stages;"
msgstr ""

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

#. Tag: para
#, no-c-format
msgid "There is always one envelope sender address."
msgstr ""

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

#. Tag: para
#, no-c-format
msgid "There are one or more recipients for each message."
msgstr ""

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

#. Tag: para
#, no-c-format
msgid ""
"In the DATA SMTP protocol state, the envelope sender and all recipients are "
"known. It is here that the Kolab SMTP Access Policy starts checking the "
"policies that apply to the sender and recipients in one go."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Postfix allows for more and different restrictions to be configured to check"
" the policy, but these are the interesting ones."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Using the Postfix sender restrictions allows the Kolab SMTP Access Policy to"
" verify certain information, and otherwise block the mail early on. Note "
"that the first policy request occurs in protocol state RCPT, and thus also "
"the first recipient for the message is being supplied in the policy request."
" For the purpose of verifying the sender's authorization to use the envelope"
" sender address access however, this is of little interest."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Is the sender authenticated?"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Is the authenticated sender allowed to use the envelope sender address?"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Envelope sender addresses that a user is typically allowed to use include "
"primary and secondary email addresses directly associated with the user's "
"entity in the authentication and authorization database."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Other address may include any of the email addresses the user has been made "
"an authorized Kolab delegate for."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In case these checks are successful the Kolab SMTP Access Policy either "
"continues with \"checking\" the recipient - please see notes later on."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"If configured to not also check recipient (the default is to check "
"recipients too) the Kolab SMTP Access Policy returns action DUNNO, which "
"indicates to Postfix the policy service doesn't care about blocking nor "
"accepting the message. Please see the notes later on for more information."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Using the Postfix recipient restrictions allows the Kolab SMTP Access Policy"
" to aggregate all recipients to which the message is intended. The Kolab "
"SMTP Access Policy has no interest in blocking at this stage, and will "
"always return DUNNO."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"It is not until the very last policy request in the DATA protocol state, "
"that Postfix allows the Kolab SMTP Access Policy to iterate over the "
"information received so far, and let's the Kolab SMTP Access Policy know the"
" parts of the complete message submission that involves sender and one or "
"more recipients is over."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"It is therefor crucially important that the Kolab SMTP Access Policy process"
" spawned by Postfix only exits after a complete message policy request has "
"finished (DATA protocol state, at which all possible MAIL FROM and RCPT TO "
"must have been submitted by the client), and it has given Postfix back to "
"ultimate policy request result."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"It is to this end, that the Kolab SMTP Access Policy reads policy requests, "
"for as long as it can, until it reaches the DATA protocol state. Only then "
"does the Kolab SMTP Access Policy actually check sender access policies and "
"recipient access policies. During the RCPT TO protocol state, the policy "
"service will return DUNNO using function <code>ignore(_(\"No objections "
"yet\"))</code>."
msgstr ""