summaryrefslogtreecommitdiff
path: root/Architecture_and_Design/pot/Email.pot
blob: e4ae8e4f7366bf963835d927f45300554b10e4c8 (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
# 
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2012-09-08T14:57:34\n"
"PO-Revision-Date: 2012-09-08T14:57:34\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

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

#. Tag: para
#, no-c-format
msgid "This chapter addresses the email aspects of the Kolab Groupware Solution."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Content-filtering"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Content-filtering is usually performed as close to the outer edge of the corporate network as possible. In reality, content-filtering is typically implemented on any or all of the following mail exchanger types, in order of likelihood;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Receiving <xref linkend=\"form-Architecture_and_Design-Terminology-External_Mail_Exchanger\" />,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Sending <xref linkend=\"form-Architecture_and_Design-Terminology-External_Mail_Exchanger\" />,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<xref linkend=\"form-Architecture_and_Design-Terminology-Internal_Mail_Exchanger\" />,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Address content-filtering (where, when, what, enhance, control, audit, report, account)."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Available Technologies"
msgstr ""

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

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

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

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

#. Tag: para
#, no-c-format
msgid "Postfix' postscreen (version 2.8 and later)"
msgstr ""

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

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

#. Tag: para
#, no-c-format
msgid "3rd party appliances"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Recipient Checking"
msgstr ""

#. Tag: para
#, no-c-format
msgid "As far as content-filtering is concerned, recipient address checking &ndash;verifying whether or not the recipient address exists in any of the groupware environments&ndash; is typically triggered as one of the first content-filtering defense mechanisms on an <xref linkend=\"form-Architecture_and_Design-Terminology-External_Mail_Exchanger\" /> &mdash;usually only those external mail exchangers of type <xref linkend=\"form-Architecture_and_Design-External_Mail_Exchanger_Types-Receiving\" />."
msgstr ""

#. Tag: para
#, no-c-format
msgid "By implementing recipient address checking as a defense mechanism too early, however, an organization exposes itself to recognaisance attacks; an attacker could, relatively quickly, discover which recipient addresses do and which do not exist."
msgstr ""

#. Tag: para
#, no-c-format
msgid "There is a significant trade-off to implementing recipient address checking too late, however. All email could have to go through (and pass) the relatively processing intensive anti-spam and anti-virus content filters, offering an attacker opportunity to successfully execute Denial-of-Service attacks."
msgstr ""

#. Tag: para
#, no-c-format
msgid "It is therefor strongly recommended to implement other defense mechanisms before recipient address checking is performed, such as blacklisting, greylisting, real-time DNS blacklisting and sender address and domain name space verification, and to implement recipient address checking before anti-spam and anti-virus content filtering."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Anti-Spam"
msgstr ""

#. Tag: para
#, no-c-format
msgid "When Kolab Groupware is configured to be responsible for anti-spam content filtering measures &ndash;the default&ndash; it will choose to use Apache's SpamAssassin software to do so."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Integration with SpamAssassin comes in different shapes and forms, depending on the technology used and the options chosen."
msgstr ""

#. Tag: para
#, no-c-format
msgid "For example, anti-spam content filtering can be implemented inline, providing opportunity to not accept the email for delivery, inherently holding the sender MTA responsible for the non-delivery report."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Whether or not to use deployment-wide or per-user anti-spam content filtering preferences is another one of such options. This one, however, greatly impacts where exactly anti-spam content filtering may take place."
msgstr ""

#. Tag: para
#, no-c-format
msgid "For a more complete reference to email anti-spam techniques, please see <ulink url=\"http://en.wikipedia.org/wiki/Anti-spam_techniques_(e-mail)\">Wikipedia's article on Anti-Spam Techniques</ulink>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Anti-Virus"
msgstr ""

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

#. Tag: title
#, no-c-format
msgid "White- and Blacklisting"
msgstr ""

#. Tag: para
#, no-c-format
msgid "When implementing greylisting, recipient addresses are first rejected, before being accepted at a later time. To track which email has been greylisted before, and should thus be accepted when retried, a mail exchanger typically maintains an internal database recording three key pieces of information &ndash;a so-called <emphasis>triplet</emphasis>:"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The IP address of the sending mail exchanger,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The envelope sender address,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The envelope recipient address(es)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Naturally, for greylisting policies to work the internal database must also keep record of the timestamp for the delivery attempt rejected."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Greylisting requires the sender to retry delivery, which is not a RFC requirement until <ulink url=\"http://tools.ietf.org/search/rfc5321\">RFC 5321: \"Simple Mail Transfer Protocol\"</ulink>, which obsoleted <ulink url=\"http://tools.ietf.org/search/rfc821\">RFC 821: \"Simple Mail Transfer Protocol\"</ulink>. RFC 821 had recommended (not required) retrying delivery. Older mailservers may not be in compliance with the new specifications in RFC 5321."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Greylisting introduces a delay in delivery for those \"triplets\" that do not have established use patterns. This may be contrary to what users expect, as most email delivery is virtually instantaneous. For greylisting to work effectively, whitelisting should be used extensively."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The former notwithstanding, trusted 3rd parties can be annotated as such by, for example, listing the 3rd party server IP addresses or DNS PTR entry record(s) (by CIDR or regex notation)."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Additional Reading"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<ulink url=\"http://en.wikipedia.org/wiki/Greylisting\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<ulink url=\"http://www.greylisting.org/whitelisting.shtml\">Known servers not compliant with greylisting</ulink>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Real-time DNS Blacklisting"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Sender Address Verification"
msgstr ""

#. Tag: title
#, no-c-format
msgid "SPF Record Enforcement"
msgstr ""

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

#. Tag: para
#, no-c-format
msgid "recipient address checking"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Integration &amp; Interoperability"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Pretty Good Privacy &amp; S/MIME"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Example, GPG signing without Exchange clients enabled to decrypt / verify signatures - same for S/MIME."
msgstr ""

#. Tag: title
#, no-c-format
msgid "See Also"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<xref linkend=\"sect-Architecture_and_Design-Integration_amp_Interoperability-SSL_Certificate_Infrastructure\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Email Routing"
msgstr ""

#. Tag: para
#, no-c-format
msgid "TODO - routing mtas as internal mtas. link with archiving and discovery. link with content-filtering. link with accounting."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Shared Folders"
msgstr ""

#. Tag: para
#, no-c-format
msgid "TODO - on shared folders on one groupware environment for clients configured against another groupware environment"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Distribution Groups"
msgstr ""

#. Tag: para
#, no-c-format
msgid "TODO - distribution groups between multiple groupware environments, access control."
msgstr ""

#. Tag: para
#, no-c-format
msgid "<xref linkend=\"chap-Architecture_and_Design-Integration_amp_Interoperability\" />"
msgstr ""