docs/diploma
changeset 76:5bd3f2118960
merge
| author | meillo@marmaro.de |
|---|---|
| date | Tue, 04 Nov 2008 11:34:30 +0100 |
| parents | a01ff7d2ca7e 6843dfd6c4fa |
| children | a6d67c5f7d78 |
| files | |
| diffstat | 9 files changed, 362 insertions(+), 200 deletions(-) [+] |
line diff
1.1 --- a/docs/mailinglist_old/masqmail.mbox Tue Nov 04 11:33:15 2008 +0100 1.2 +++ b/docs/mailinglist_old/masqmail.mbox Tue Nov 04 11:34:30 2008 +0100 1.3 @@ -521,7 +521,7 @@ 1.4 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.5 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.6 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.7 -Status: O 1.8 +Status: RO 1.9 1.10 --Y7xTucakfITjPcLV 1.11 Content-Type: text/plain; charset=us-ascii 1.12 @@ -591,7 +591,7 @@ 1.13 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.14 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.15 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.16 -Status: O 1.17 +Status: RO 1.18 1.19 Hi, 1.20 1.21 @@ -657,7 +657,7 @@ 1.22 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.23 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.24 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.25 -Status: O 1.26 +Status: RO 1.27 1.28 --uZ3hkaAS1mZxFaxD 1.29 Content-Type: text/plain; charset=us-ascii 1.30 @@ -762,7 +762,7 @@ 1.31 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.32 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.33 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.34 -Status: O 1.35 +Status: RO 1.36 1.37 Hi, 1.38 1.39 @@ -818,7 +818,7 @@ 1.40 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.41 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.42 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.43 -Status: O 1.44 +Status: RO 1.45 1.46 --Q68bSM7Ycu6FN28Q 1.47 Content-Type: text/plain; charset=us-ascii 1.48 @@ -898,7 +898,7 @@ 1.49 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.50 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.51 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.52 -Status: O 1.53 +Status: RO 1.54 1.55 > > ... 1.56 > 1.57 @@ -953,7 +953,7 @@ 1.58 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.59 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.60 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.61 -Status: O 1.62 +Status: RO 1.63 1.64 Hi Oliver, 1.65 1.66 @@ -1045,7 +1045,7 @@ 1.67 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.68 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.69 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.70 -Status: O 1.71 +Status: RO 1.72 1.73 --da4uJneut+ArUgXk 1.74 Content-Type: text/plain; charset=us-ascii 1.75 @@ -1127,7 +1127,7 @@ 1.76 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.77 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.78 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.79 -Status: O 1.80 +Status: RO 1.81 1.82 Hi Oliver, 1.83 1.84 @@ -1170,7 +1170,7 @@ 1.85 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.86 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.87 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.88 -Status: O 1.89 +Status: RO 1.90 1.91 Hi, 1.92 1.93 @@ -1223,7 +1223,7 @@ 1.94 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.95 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.96 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.97 -Status: O 1.98 +Status: RO 1.99 1.100 > On Fri, Aug 02, 2002 at 12:25:39PM +0000, Anonymous User wrote: 1.101 > > 1.102 @@ -1294,7 +1294,7 @@ 1.103 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.104 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.105 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.106 -Status: O 1.107 +Status: RO 1.108 1.109 Hi Oliver, 1.110 1.111 @@ -1364,7 +1364,7 @@ 1.112 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.113 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.114 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.115 -Status: O 1.116 +Status: RO 1.117 1.118 --7AUc2qLy4jB3hD7Z 1.119 Content-Type: text/plain; charset=us-ascii 1.120 @@ -1443,7 +1443,7 @@ 1.121 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.122 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.123 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.124 -Status: O 1.125 +Status: RO 1.126 1.127 Hi Oliver, 1.128 1.129 @@ -1502,7 +1502,7 @@ 1.130 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.131 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.132 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.133 -Status: O 1.134 +Status: RO 1.135 1.136 Hi Oliver, 1.137 1.138 @@ -1564,7 +1564,7 @@ 1.139 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.140 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.141 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.142 -Status: O 1.143 +Status: RO 1.144 1.145 --xXmbgvnjoT4axfJE 1.146 Content-Type: text/plain; charset=us-ascii 1.147 @@ -1653,7 +1653,7 @@ 1.148 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.149 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.150 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.151 -Status: O 1.152 +Status: RO 1.153 1.154 --7lMq7vMTJT4tNk0a 1.155 Content-Type: text/plain; charset=us-ascii 1.156 @@ -1740,7 +1740,7 @@ 1.157 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.158 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.159 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.160 -Status: O 1.161 +Status: RO 1.162 1.163 > On Fri, Aug 02, 2002 at 06:10:20PM +0200, Anonymous wrote: 1.164 > > Hi Oliver, 1.165 @@ -1778,7 +1778,7 @@ 1.166 The masqmail.route man page has got nothing to do with this issue. 1.167 1.168 From now on I will check my stuff twice before posting. 1.169 -Status: O 1.170 +Status: RO 1.171 1.172 By the way, I think you are doing a great job. 1.173 For me, masqmail is the best MTA around, it is lightweight in size 1.174 @@ -1832,7 +1832,7 @@ 1.175 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.176 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.177 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.178 -Status: O 1.179 +Status: RO 1.180 1.181 --zYM0uCDKw75PZbzx 1.182 Content-Type: text/plain; charset=us-ascii 1.183 @@ -1939,7 +1939,7 @@ 1.184 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.185 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.186 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.187 -Status: O 1.188 +Status: RO 1.189 1.190 On Monday 29 July 2002 12:02, Oliver Kurth wrote: 1.191 > On Fri, Jul 26, 2002 at 08:02:20PM +0200, Wilbert Berendsen wrote: 1.192 @@ -2049,7 +2049,7 @@ 1.193 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.194 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.195 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.196 -Status: O 1.197 +Status: RO 1.198 1.199 --t0UkRYy7tHLRMCai 1.200 Content-Type: text/plain; charset=us-ascii 1.201 @@ -2432,7 +2432,7 @@ 1.202 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.203 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.204 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.205 -Status: O 1.206 +Status: RO 1.207 Content-Length: 585 1.208 Lines: 20 1.209 1.210 @@ -2497,7 +2497,7 @@ 1.211 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.212 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.213 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.214 -Status: O 1.215 +Status: RO 1.216 Content-Length: 1413 1.217 Lines: 50 1.218 1.219 @@ -2594,7 +2594,7 @@ 1.220 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.221 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.222 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.223 -Status: O 1.224 +Status: RO 1.225 Content-Length: 1089 1.226 Lines: 39 1.227 1.228 @@ -2680,7 +2680,7 @@ 1.229 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.230 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.231 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.232 -Status: O 1.233 +Status: RO 1.234 Content-Length: 1485 1.235 Lines: 51 1.236 1.237 @@ -2779,7 +2779,7 @@ 1.238 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.239 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.240 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.241 -Status: O 1.242 +Status: RO 1.243 Content-Length: 632 1.244 Lines: 20 1.245 1.246 @@ -2846,7 +2846,7 @@ 1.247 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.248 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.249 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.250 -Status: O 1.251 +Status: RO 1.252 Content-Length: 980 1.253 Lines: 37 1.254 1.255 @@ -2928,7 +2928,7 @@ 1.256 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.257 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.258 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.259 -Status: O 1.260 +Status: RO 1.261 Content-Length: 913 1.262 Lines: 36 1.263 1.264 @@ -3002,7 +3002,7 @@ 1.265 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.266 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.267 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.268 -Status: O 1.269 +Status: RO 1.270 Content-Length: 781 1.271 Lines: 28 1.272 1.273 @@ -3077,7 +3077,7 @@ 1.274 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.275 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.276 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.277 -Status: O 1.278 +Status: RO 1.279 Content-Length: 2403 1.280 Lines: 68 1.281 1.282 @@ -3187,7 +3187,7 @@ 1.283 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.284 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.285 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.286 -Status: O 1.287 +Status: RO 1.288 Content-Length: 792 1.289 Lines: 22 1.290 1.291 @@ -3254,7 +3254,7 @@ 1.292 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.293 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.294 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.295 -Status: O 1.296 +Status: RO 1.297 Content-Length: 1374 1.298 Lines: 48 1.299 1.300 @@ -3347,7 +3347,7 @@ 1.301 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.302 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.303 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.304 -Status: O 1.305 +Status: RO 1.306 Content-Length: 1248 1.307 Lines: 44 1.308 1.309 @@ -3435,7 +3435,7 @@ 1.310 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.311 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.312 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.313 -Status: O 1.314 +Status: RO 1.315 Content-Length: 830 1.316 Lines: 24 1.317 1.318 @@ -3504,7 +3504,7 @@ 1.319 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.320 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.321 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.322 -Status: O 1.323 +Status: RO 1.324 Content-Length: 1145 1.325 Lines: 44 1.326 1.327 @@ -3593,7 +3593,7 @@ 1.328 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.329 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.330 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.331 -Status: O 1.332 +Status: RO 1.333 Content-Length: 2790 1.334 Lines: 77 1.335 1.336 @@ -3713,7 +3713,7 @@ 1.337 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.338 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.339 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.340 -Status: O 1.341 +Status: RO 1.342 Content-Length: 230 1.343 Lines: 9 1.344 1.345 @@ -3760,7 +3760,7 @@ 1.346 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.347 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.348 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.349 -Status: O 1.350 +Status: RO 1.351 Content-Length: 88 1.352 Lines: 6 1.353 1.354 @@ -3813,7 +3813,7 @@ 1.355 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.356 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.357 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.358 -Status: O 1.359 +Status: RO 1.360 Content-Length: 1140 1.361 Lines: 40 1.362 1.363 @@ -3898,7 +3898,7 @@ 1.364 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.365 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.366 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.367 -Status: O 1.368 +Status: RO 1.369 Content-Length: 1472 1.370 Lines: 47 1.371 1.372 @@ -3992,7 +3992,7 @@ 1.373 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.374 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.375 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.376 -Status: O 1.377 +Status: RO 1.378 Content-Length: 812 1.379 Lines: 34 1.380 1.381 @@ -4074,7 +4074,7 @@ 1.382 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.383 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.384 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.385 -Status: O 1.386 +Status: RO 1.387 Content-Length: 562 1.388 Lines: 25 1.389 1.390 @@ -4146,7 +4146,7 @@ 1.391 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.392 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.393 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.394 -Status: O 1.395 +Status: RO 1.396 Content-Length: 2193 1.397 Lines: 69 1.398 1.399 @@ -4253,7 +4253,7 @@ 1.400 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.401 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.402 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.403 -Status: O 1.404 +Status: RO 1.405 Content-Length: 375 1.406 Lines: 14 1.407 1.408 @@ -4314,7 +4314,7 @@ 1.409 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.410 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.411 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.412 -Status: O 1.413 +Status: RO 1.414 Content-Length: 1523 1.415 Lines: 46 1.416 1.417 @@ -4401,7 +4401,7 @@ 1.418 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.419 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.420 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.421 -Status: O 1.422 +Status: RO 1.423 Content-Length: 545 1.424 Lines: 21 1.425 1.426 @@ -4469,7 +4469,7 @@ 1.427 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.428 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.429 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.430 -Status: O 1.431 +Status: RO 1.432 Content-Length: 1763 1.433 Lines: 65 1.434 1.435 @@ -4575,7 +4575,7 @@ 1.436 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.437 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.438 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.439 -Status: O 1.440 +Status: RO 1.441 Content-Length: 1245 1.442 Lines: 47 1.443 1.444 @@ -4669,7 +4669,7 @@ 1.445 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.446 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.447 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.448 -Status: O 1.449 +Status: RO 1.450 Content-Length: 1687 1.451 Lines: 60 1.452 1.453 @@ -4776,7 +4776,7 @@ 1.454 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.455 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.456 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.457 -Status: O 1.458 +Status: RO 1.459 Content-Length: 1756 1.460 Lines: 59 1.461 1.462 @@ -4880,7 +4880,7 @@ 1.463 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.464 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.465 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.466 -Status: O 1.467 +Status: RO 1.468 Content-Length: 714 1.469 Lines: 34 1.470 1.471 @@ -4959,7 +4959,7 @@ 1.472 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.473 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.474 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.475 -Status: O 1.476 +Status: RO 1.477 Content-Length: 921 1.478 Lines: 38 1.479 1.480 @@ -5045,7 +5045,7 @@ 1.481 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.482 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.483 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.484 -Status: O 1.485 +Status: RO 1.486 Content-Length: 894 1.487 Lines: 36 1.488 1.489 @@ -5128,7 +5128,7 @@ 1.490 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.491 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.492 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.493 -Status: O 1.494 +Status: RO 1.495 Content-Length: 2497 1.496 Lines: 74 1.497 1.498 @@ -5250,7 +5250,7 @@ 1.499 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.500 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.501 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.502 -Status: O 1.503 +Status: RO 1.504 Content-Length: 813 1.505 Lines: 28 1.506 1.507 @@ -5325,7 +5325,7 @@ 1.508 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.509 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.510 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.511 -Status: O 1.512 +Status: RO 1.513 Content-Length: 2459 1.514 Lines: 75 1.515 1.516 @@ -5441,7 +5441,7 @@ 1.517 List-Unsubscribe: <http://lists.masqmail.cx/cgi-bin/mailman/listinfo/masqmail>, 1.518 <mailto:masqmail-request@lists.masqmail.cx?subject=unsubscribe> 1.519 List-Archive: <http://lists.masqmail.cx/pipermail/masqmail/> 1.520 -Status: O 1.521 +Status: RO 1.522 Content-Length: 553 1.523 Lines: 22 1.524
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 2.2 +++ b/docs/various/qref-mta.txt Tue Nov 04 11:34:30 2008 +0100 2.3 @@ -0,0 +1,55 @@ 2.4 +http://qref.sourceforge.net/Debian/reference/reference.en.txt 2.5 + 2.6 +9.6.1. Mail transport agents (MTAs) 2.7 +----------------------------------- 2.8 + 2.9 + For a full-featured MTA, use `exim' in Woody and use `exim4' in Sarge. 2.10 + [1] References: 2.11 + * `exim-doc' and `exim-doc-html' packages for `exim' 2.12 + * `exim4-doc-info' and `exim4-doc-html' packages for `exim4' 2.13 + * http://www.exim.org/ 2.14 + The only reasonable alternative MTA is `postfix' if you care about 2.15 + security. `sendmail' and `qmail' are available as Debian packages but 2.16 + are not recommended. 2.17 + 2.18 + If you do not need the relay capability of an MTA as in the case of a 2.19 + satellite system such as a laptop PC, you may consider using one of 2.20 + these lightweight packages: 2.21 + * `ssmtp': needs an SMTP connection and is alias-capable, or 2.22 + * `nullmailer': can spool but is not alias-capable. 2.23 + At this moment, I find `exim' to be more suitable even for my personal 2.24 + workstation machine, which is a laptop PC. 2.25 + 2.26 + You may need to remove `exim' for the installation of these 2.27 + conflicting packages: 2.28 + 2.29 + # dpkg -P --force-depends exim 2.30 + # apt-get install nullmailer # or ssmtp 2.31 + 2.32 +[1] Following sections use `exim' in examples. For Sarge replace this 2.33 + with `exim4' as needed. 2.34 + 2.35 +9.6.1.1. Smarthost 2.36 +------------------ 2.37 + 2.38 + If you are running `exim4' or `exim' on a host which is connected 2.39 + through the consumer grade services, please make sure to send outgoing 2.40 + mail through a smarthost offered by your ISP or some others. [1] 2.41 + There are few good reasons: 2.42 + * to ensure SMTP retries since your ISP's smarthost usually have 2.43 + more reliably connection. 2.44 + * to avoid sending mail directly from a _dynamic IP address_ which 2.45 + will likely be blocked by dial-up spam lists. 2.46 + * to save your local bandwidth to send mails with multiple 2.47 + recipients. 2.48 + 2.49 + The only conceivable exceptions are: 2.50 + * the emergency cure for your ISP's SMTP service trouble. 2.51 + * an experiment for the educational purpose. 2.52 + * your host being a professionally hosted server. 2.53 + 2.54 +[1] You must follow this rule for any hosts on dial-up, DSL, cable 2.55 + services or LAN through some broadband router. Even if your home host 2.56 + has a fixed IP from your ISP, it is still a good idea to follow this 2.57 + rule. Most workstations and home servers fall into this category. 2.58 +
3.1 --- a/thesis/bib/thesis.bib Tue Nov 04 11:33:15 2008 +0100 3.2 +++ b/thesis/bib/thesis.bib Tue Nov 04 11:34:30 2008 +0100 3.3 @@ -42,7 +42,7 @@ 3.4 note = "ISBN: 1-56592-724-9. Also available at {\small\url{http://catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/} (2008-10-14)}", 3.5 } 3.6 3.7 -@book{sendmail, 3.8 +@book{costales97, 3.9 author = "Bryan Costales and Eric Allman", 3.10 title = "sendmail", 3.11 year = "1997", 3.12 @@ -51,6 +51,15 @@ 3.13 note = "ISBN: 1-56592-222-0", 3.14 } 3.15 3.16 +@book{vixie01, 3.17 + author = "Paul A. Vixie and Frederick M. Avolio", 3.18 + title = "Sendmail: Theory and Practice", 3.19 + year = "2001", 3.20 + edition = "Second", 3.21 + publisher = "Digital Press", 3.22 + note = "ISBN: 1-55558-229-X. The first chapter ``Background and History'' is available online at {\small\url{http://smtap.al.org/ch01.pdf} (2008-10-23)}", 3.23 +} 3.24 + 3.25 3.26 3.27 =====================================
4.1 --- a/thesis/bib/websites.bib Tue Nov 04 11:33:15 2008 +0100 4.2 +++ b/thesis/bib/websites.bib Tue Nov 04 11:34:30 2008 +0100 4.3 @@ -100,3 +100,86 @@ 4.4 title = "\emph{Definition for ``mail transfer agent''}", 4.5 howpublished = "On the Internet: {\small\url{http://www.kayian.freeserve.co.uk/page7.htm} (2008-10-15)}", 4.6 } 4.7 + 4.8 + 4.9 +@misc{faqs:mmdf, 4.10 + author = "FAQs.org", 4.11 + title = "\emph{The MMDF Frequently Asked Questions List (FAQ)}", 4.12 + howpublished = "On the Internet: {\small\url{http://www.faqs.org/faqs/mail/mmdf-faq/part1/} (2008-10-23)}", 4.13 +} 4.14 + 4.15 + 4.16 +# email history 4.17 +@misc{email:griffiths, 4.18 + author = "Richard T. Griffiths", 4.19 + title = "\emph{History of the Internet, Internet for Historians (and just about everyone else)}", 4.20 + chapter = "3", 4.21 + howpublished = "On the Internet: {\small\url{http://www.let.leidenuniv.nl/history/ivh/chap3.htm} (2008-10-23)}", 4.22 +} 4.23 + 4.24 +@misc{email:crocker, 4.25 + author = "Dave Crocker", 4.26 + title = "\emph{Email History, How Email Was Invented}", 4.27 + howpublished = "On the Internet: {\small\url{http://www.livinginternet.com/e/ei.htm} (2008-10-23)}", 4.28 +} 4.29 + 4.30 +@misc{email:vleck, 4.31 + author = "Tom van Vleck", 4.32 + title = "\emph{The History of Electronic Mail}", 4.33 + howpublished = "On the Internet: {\small\url{http://www.multicians.org/thvv/mail-history.html} (2008-10-23)}", 4.34 +} 4.35 + 4.36 +@misc{email:akkad, 4.37 + author = "Jay Akkad", 4.38 + title = "\emph{The History of Email}", 4.39 + howpublished = "On the Internet: {\small\url{http://www.cs.ucsb.edu/~almeroth/classes/F04.176A/homework1_good_papers/jay-akkad.html} (2008-10-23)}", 4.40 +} 4.41 + 4.42 +@misc{email:murakami, 4.43 + author = "Gary J. Murakami", 4.44 + title = "\emph{The History of ihnp4 and The Growth of the Email Network}", 4.45 + howpublished = "On the Internet: {\small\url{http://www.nobell.org/~gjm/about/ihnp4.html} (2008-10-23)}", 4.46 +} 4.47 + 4.48 +@misc{email:tomlinson, 4.49 + author = "Ray Tomlinson", 4.50 + title = "\emph{The First Network Email}", 4.51 + howpublished = "On the Internet: {\small\url{http://openmap.bbn.com/~tomlinso/ray/firstemailframe.html} (2008-10-23)}", 4.52 +} 4.53 + 4.54 +@misc{wikipedia:uucp, 4.55 + author = "Wikipedia", 4.56 + title = "\emph{UUCP}", 4.57 + howpublished = "On the Internet: {\small\url{http://en.wikipedia.org/w/index.php?title=UUCP&oldid=238072862} (2008-10-23)}", 4.58 +} 4.59 + 4.60 +@misc{wikipedia:arpanet, 4.61 + author = "Wikipedia", 4.62 + title = "\emph{ARPANET}", 4.63 + howpublished = "On the Internet: {\small\url{http://en.wikipedia.org/w/index.php?title=ARPANET&oldid=247162321} (2008-10-23)}", 4.64 +} 4.65 + 4.66 +@misc{wikipedia:email, 4.67 + author = "Wikipedia", 4.68 + title = "\emph{E-mail}", 4.69 + howpublished = "On the Internet: {\small\url{http://en.wikipedia.org/w/index.php?title=E-mail&oldid=247092569} (2008-10-23)}", 4.70 +} 4.71 + 4.72 +@misc{wikipedia:historyoftheinternet, 4.73 + author = "Wikipedia", 4.74 + title = "\emph{History of the Internet}", 4.75 + howpublished = "On the Internet: {\small\url{http://en.wikipedia.org/w/index.php?title=History_of_the_Internet&oldid=245178555} (2008-10-23)}", 4.76 +} 4.77 + 4.78 +@misc{unix-mail-intro, 4.79 + author = "Network Computing", 4.80 + title = "\emph{Introducing Unix Mail}", 4.81 + howpublished = "On the Internet: {\small\url{http://www.networkcomputing.com/unixworld/tutorial/810.txt.html} (2008-10-23)}", 4.82 +} 4.83 + 4.84 +@misc{packages.debian:masqmail, 4.85 + author = "Debian", 4.86 + title = "\emph{Details of package masqmail in lenny}", 4.87 + howpublished = "On the Internet: {\small\url{http://packages.debian.org/lenny/masqmail} (2008-10-24)}", 4.88 +} 4.89 +
5.1 --- a/thesis/tex/1-Candidates.tex Tue Nov 04 11:33:15 2008 +0100 5.2 +++ b/thesis/tex/1-Candidates.tex Tue Nov 04 11:34:30 2008 +0100 5.3 @@ -1,86 +1,83 @@ 5.4 \chapter{\unix\ \MTA{}s} 5.5 5.6 -This chapter introduces a group of \mta{}s. 5.7 -The selected group will be delimited against other groups of \MTA{}s, which are described as well. 5.8 +After having read about the history of electronic mail and the basics of \mta{}s in the last chapter, this chapter introduces a group of \mta{}s. Among them, the already mentioned \sendmail. The selected group will be delimited against other groups of \MTA{}s, which are described as well. 5.9 5.10 -The chosen programs will be presented to the reader in a short overview and with the most important facts. 5.11 -The next chapter will show a comparison of these programs in several disciplines. 5.12 +The chosen programs will be presented to the reader in a short overview and with the most important facts. The next chapter will show a comparison of these programs in several disciplines. 5.13 5.14 5.15 \section{Types of \MTA{}s} 5.16 -``Mail transfer agent'' is a term covering a variety of programs. 5.17 -One thing is common to them: they transport email from one \emph{thing} to another. 5.18 -These \emph{things} can be hosts, meaning independent machines, or protocols like \NAME{SMTP} and \NAME{UUCP}, between which mail is transfered.\footnote{\sendmail{}'s initial purpose was moving mail between \NAME{UUCP}, \name{Berknet} and \NAME{SMTP}.} 5.19 +``Mail transfer agent'' is a term covering a variety of programs. One thing is common to them: they transfer email from one \emph{thing} to another. These \emph{things} can be hosts, meaning independent machines, or protocols like \NAME{SMTP} and \NAME{UUCP}, between which mail is transfered.\footnote{\sendmail{}'s initial purpose was moving mail between \NAME{UUCP}, \NAME{SMTP}, and \name{Berknet}.} 5.20 5.21 -Beside this common property, \MTA{}s can be very different. 5.22 -Some of them have \NAME{POP3} and/or \NAME{IMAP} servers included. 5.23 -Some can fetch mails through these protocols. 5.24 -Others have have every feature you can think of. 5.25 -And maybe there are some that do nothing else, but transporting email. 5.26 +Beside this common property, \MTA{}s can be very different. Some of them have \NAME{POP3} and/or \NAME{IMAP} servers included. Some can fetch mails through these protocols. Others have have all features you can think of. And maybe there are some that do nothing else but transporting email. 5.27 5.28 -Here are groups of \mta{}s that will not be regarded in the following chapter. 5.29 -% Prof: briefly discuss the border between small MTAs (sendmail, masqmail) and state-of-the-art mailservers (postfix) and groupware (notes, exchange): give usecases. 5.30 +Following are groups of \mta{}s that will \emph{not} be regarded further. 5.31 5.32 \subsection{Relay-only \MTA{}s} 5.33 -This is the most simple kind of \MTA. They transfer mail only to defined \name{smart hosts}\footnote{\name{smart host}s are \MTA{}s that receives email and route it to the actual destination}. \name{Relay-only} \MTA{}s do not receive mail, they only send it. 5.34 +\label{subsec:relay-only} 5.35 +This is the most simple kind of \MTA. It transfers mail only to defined \name{smart hosts}\footnote{\name{smart host}s are \MTA{}s that receives email and route it to the actual destination}. \name{Relay-only} \MTA{}s do not receive mail from outside the system, and they do not deliver locally. 5.36 5.37 -Most \MTA{}s can be configured to act as such a forwarder. But this is usually an additional functionality. 5.38 +Most \MTA{}s can be configured to act as such a \name{forwarder}. But this is usually an additional functionality. 5.39 5.40 -One would use such a program to give a system the possibility to send mail, without the need to do lots of configuration. In a local network, usually the clients are set up with such a forwarder, while there is one \name{mail server} that acts as a \name{smart host}. The ``dumb'' clients send mail only to this one \name{mail server} which does the ``real work''. 5.41 +One would use such a program to give a system the possibility to send mail, without the need to do lots of configuration. In a local network, usually the clients are set up with a \name{relay-only} \MTA, while there is one \name{mail server} that acts as a \name{smart host}. The ``dumb'' clients send mail to this one \name{mail server} which does all the work. 5.42 5.43 Examples for that group are: \name{nullmailer}, \name{ssmtp} and \name{esmtp}. 5.44 5.45 5.46 \subsection{Groupware} 5.47 -Normally the term ``groupware'' does not mean one single program, but a suite of programs. They are build up a framework which can be populated with various modules that provide actual funktionality. These modules including mail transfer, file storage, calendars, resource management, instant messaging and more. 5.48 +Normally the term ``groupware'' does not mean one single program, but a suite of programs. They build a framework which is then populated with various modules that provide actual funktionality. Modules for mail transfer, file storage, calendars, resource management, instant messaging, etc., are commonly available. 5.49 5.50 -One would use one of these program suites if the main work to do is not mail transfer, but providing communication and team working support for a group of people. The most common scenario are companies. They have \name{groupware} running to provide adequate services for their teams to work efficently. But home servers may provide \name{groupware} services for the family members also. 5.51 +One would use one of these program suites if the main work to do is not mail transfer, but providing integrated communication facilities and team working support for a group of people. The most common scenario are companies. They have \name{groupware} running to provide adequate services for their teams to work efficently. But one may use \name{groupware} on the home server for his family members also. 5.52 5.53 -Examples for this kind of programs are: \name{Lotus Notes}, \name{Microsoft Exchange}, \name{OpenGroupware.org} and \name{eGroupWare}. 5.54 +Examples are: \name{Lotus Notes}, \name{Microsoft Exchange}, \name{OpenGroupware.org} and \name{eGroupWare}. 5.55 5.56 5.57 -\subsection{More limitations} 5.58 -Third, only \emph{sendmail-compatible} \MTA{}s will be regarded in the competition. 5.59 -Hence all \MTA{}s not having a \emph{sendmail-compatible} interface or not offering it as a compatibility addon, will not be covered here. %FIXME: give an example for non-sendmail-compatible 5.60 -The reason is the heavy reliance of \unix\ systems on the existance of a programs called \path{sendmail}. 5.61 -This has historical reasons. See section \ref{sec:sendmail} for further information. 5.62 +\subsection{``Real'' \MTA{}s} 5.63 +There is a third type of \mta{}s in between the minimalistic \name{relay-only} \MTA{}s and the bloated \name{groupware}. Those programs may be named ``real \MTA{}s'', or ``proper \MTA{}s'', though there is no common name. They are what is meant with the term ``\mta''. 5.64 5.65 -Further more, only programs with source code available are regarded. %FIXME: why 5.66 +Common to them is their focus on transfering email, while being able to act as \name{smart host}. Their variety ranges from ones mostly restricted to mail transfer (\name{qmail}) to others already having interfaces for adding further mail processing modules (\name{postfix})---thus everything in between the other two groups. %FIXME: are postfix and qmail good examples? 5.67 5.68 +This group is of importance in this document. The programs selected for the comparison are ``real \MTA{}s''. 5.69 5.70 -\subsection{The ones not regarded here} 5.71 -The candidates for the competition in the next chapter are a subset of the \MTA{}s available. 5.72 -Comparision between totally different programs (apart of one function) makes not much sense. %FIXME: better words 5.73 -One would not use a program for a job it is not suited for. 5.74 -Therefor \mta{}s that are rarely similar to \masqmail\ are not regarded. 5.75 + 5.76 + 5.77 +\section{Programs to sort out} 5.78 + 5.79 +\name{Mail transfer agent}s can be segmented in various ways, apart from the classification above. Groups of programs wiproperties significantly different from \masqmail\ will be sorted out now. 5.80 + 5.81 +\subsection{Non-\emph{sendmail-compatible} \MTA{}s} 5.82 +Due to \sendmail's significance---described in section \ref{sec:sendmail}---compatiblity interfaces for \sendmail\ are of importance for \unix\ \MTA{}s. Being not \emph{sendmail-compatible} does not need to matter for some fields of action, but makes the program ineligible for serving as a general purpose \MTA\ on \unix\ systems. 5.83 + 5.84 +Hence all \MTA{}s not having a \emph{sendmail-compatible} interface or not offering it as a compatibility addon, will not be covered here. 5.85 + 5.86 +An Examples here is \name{Apache James}. %FIXME: check if correct 5.87 + 5.88 + 5.89 +\subsection{Non-free software} 5.90 +Only programs being \freesw\ are regarded, because comparing \freesw\ with proprietary or commercial software is not what typical users of programs like \masqmail\ do. Comparison with those non-free programs may be a point for large \freesw\ projects, trying to step into the business world. Small projects, mostly used by individuals at home, need to be compared against other projects of similar shape. 5.91 + 5.92 +The comparison should be seen from \masqmail's point of view, so non-free software is out of the way. 5.93 + 5.94 5.95 5.96 \section{The programs regarded} 5.97 -The programs remaining are \emph{sendmail-compatible} ``smart'' \MTA{}s that do not offer masses of features unrelated to mail transport. 5.98 +The programs remaining are \emph{sendmail-compatible} ``smart'' \MTA{}s that focus on mail transfer and are \freesw. One would not use a program for a job it is not suited for. Therefor only \mta{}s that are mostly similar to \masqmail\ are regarded. 5.99 5.100 -For the comparision, five programs of this group are taken. 5.101 -These are: \sendmail, \name{qmail}, \name{postfix}, \name{exim} and \masqmail. 5.102 -The four alternatives to \masqmail\ are the most important representatives of the regarded group. 5.103 -%TODO: what about having one program as ``outsider'' ...? 5.104 +For the comparision, five programs are taken. These are: \sendmail, \name{qmail}, \name{postfix}, \name{exim}, and \masqmail. The four alternatives to \masqmail\ are the most important representatives of the regarded group. % FIXME: add ref that affirm that 5.105 5.106 -Other, but not covered, group members are: %FIXME: are these all MTAs of that group? why these and not others? 5.107 -%TODO: what about `courier-mta'? 5.108 +\name{courier-mta} is also a member of this group, being even closer to \name{groupware} than \name{postfix}. It is excluded here, because the \NAME{IMAP} and webmail parts of the mail server suite are more in focus than its \MTA. Common mail server setups even bundle \name{courier-imap} with \name{postfix}. 5.109 5.110 -Here follows a small introduction to each of the five. 5.111 +Other members are: \name{smail}, \name{zmailer}, \name{mmdf}, and more; they all are less important and rarely used. 5.112 + 5.113 +Following is a small introduction to each of the five programs chosen for comparision. 5.114 5.115 \subsection{\sendmail} 5.116 -\sendmail\ is the most popular \mta. 5.117 -Since it was one of the first \MTA{}s and was shipped by many vendors of \unix\ systems. 5.118 +\sendmail\ is the most popular \mta. Since it was one of the first \MTA{}s and was shipped by many vendors of \unix\ systems. 5.119 5.120 -The program was written by Eric Allman as the successor of his program \name{delivermail}. 5.121 -\sendmail\ was first released with \NAME{BSD} 4.1c in 1983. 5.122 -Allman was not the only one working on the program. 5.123 -Other people developed own versions of it and a variety of flavors came up, especially in the late eighties when Allman was inactive. 5.124 +The program was written by Eric Allman as the successor of his program \name{delivermail}. \sendmail\ was first released with \NAME{BSD} 4.1c in 1983. Allman was not the only one working on the program. Other people developed own versions of it and a variety of flavors came up, especially in the late eighties when Allman was inactive. 5.125 5.126 \sendmail\ is focused on transfering mails between different protocols and networks, this lead to a very flexible (though complex) configuration. 5.127 5.128 -The latest version is 8.14.3 from May 2008. 5.129 -The program is distributed under the \name{Sendmail License} as both, \freesw\ and proprietary software of \name{Sendmail, Inc.}. 5.130 +The latest version is 8.14.3 from May 2008. The program is distributed under the \name{Sendmail License} as both, \freesw\ and proprietary software of \name{Sendmail, Inc.}. 5.131 5.132 Further development will go into the project \name{MeTA1} which succeeds \sendmail. 5.133 5.134 @@ -88,43 +85,31 @@ 5.135 5.136 5.137 \subsection{\name{qmail}} 5.138 -\name{qmail} is seen by its community as ``a modern SMTP server which makes sendmail obsolete''. 5.139 -It was written by Daniel~J.\ Bernstein starting in 1995. 5.140 -His primary goal was to create a secure \MTA\ to replace the popular, but vulnerable, \sendmail. 5.141 +\name{qmail} is seen by its community as ``a modern SMTP server which makes sendmail obsolete''. It was written by Daniel~J.\ Bernstein starting in 1995. His primary goal was to create a secure \MTA\ to replace the popular, but vulnerable, \sendmail. 5.142 5.143 \name{qmail} first introduced may innovative concepts in \mta\ design and is generally seen as the first security-aware \MTA\ developed. 5.144 5.145 -Since November 2007, \name{qmail} is released in the \name{public domain} which makes it \freesw. 5.146 -The latest release is 1.03 from July 1998. 5.147 +Since November 2007, \name{qmail} is released in the \name{public domain} which makes it \freesw. The latest release is 1.03 from July 1998. 5.148 5.149 The programs homepages are \citeweb{qmail:homepage1} and \citeweb{qmail:homepage2}. Further information about \name{qmail} is available on \citeweb{lifewithqmail}, \citeweb{wikipedia:qmail} and \citeweb{jdebp}. 5.150 5.151 5.152 \subsection{\name{postfix}} 5.153 -The \name{postfix} project was started in 1999 at \name{IBM research}, then called \name{VMailer} or \name{IBM Secure Mailer}. 5.154 -Wietse Venema's program ``attempts to be fast, easy to administer, and secure. The outside has a definite Sendmail-ish flavor, but the inside is completely different.''\citeweb{postfix:homepage} 5.155 -In fact, \name{postfix} was mainly designed after qmail's architecture to gain security. 5.156 -But in contrast to \name{qmail} it aims much more on being fast and full-featured. 5.157 +The \name{postfix} project was started in 1999 at \name{IBM research}, then called \name{VMailer} or \name{IBM Secure Mailer}. Wietse Venema's program ``attempts to be fast, easy to administer, and secure. The outside has a definite Sendmail-ish flavor, but the inside is completely different.''\citeweb{postfix:homepage} In fact, \name{postfix} was mainly designed after qmail's architecture to gain security. But in contrast to \name{qmail} it aims much more on being fast and full-featured. 5.158 5.159 Today \name{postfix} is taken by many \unix systems and \gnulinux distributions as default \MTA. 5.160 5.161 -The latest stable version is numbered 2.5.5 from August 2008. 5.162 -\name{postfix} is covered by the \name{IBM Public License 1.0} which is a \freesw\ license. 5.163 +The latest stable version is numbered 2.5.5 from August 2008. \name{postfix} is covered by the \name{IBM Public License 1.0} which is a \freesw\ license. 5.164 5.165 Additional information is available on the program's homepage \citeweb{postfix:homepage}, on \citeweb{jdebp} and \citeweb{wikipedia:postfix}. 5.166 5.167 5.168 \subsection{\name{exim}} 5.169 -\name{exim} was started in 1995 by Philip Hazel at the \name{University of Cambridge}. 5.170 -Its age is about the same as \name{qmail}'s, but the architecture is totally different. 5.171 +\name{exim} was started in 1995 by Philip Hazel at the \name{University of Cambridge}. Its age is about the same as \name{qmail}'s, but the architecture is totally different. 5.172 5.173 -While \name{qmail} took a completely new approach, \name{exim} forked of \name{smail-3}, and therefor is monolitic like that and like \sendmail. 5.174 -But having no separation of the individual components of the system, like \name{qmail} and \name{postfix} have, did not hurt. 5.175 -Its security is comparably good. 5.176 +While \name{qmail} took a completely new approach, \name{exim} forked of \name{smail-3}, and therefor is monolitic like that and like \sendmail. But having no separation of the individual components of the system, like \name{qmail} and \name{postfix} have, did not hurt. Its security is comparably good. 5.177 5.178 -\name{exim} is highly configurable, especially in the field of mail policies. 5.179 -This makes it easy to specify how mail is routed through the system and who is allowed to send email to whom. 5.180 -Also interfaces for integration of virus and spam check programs are provided by design. 5.181 +\name{exim} is highly configurable, especially in the field of mail policies. This makes it easy to specify how mail is routed through the system and who is allowed to send email to whom. Also interfaces for integration of virus and spam check programs are provided by design. 5.182 5.183 The program is \freesw, released under the \GPL. The latest stable version is 4.69 from December 2007. 5.184 5.185 @@ -132,16 +117,11 @@ 5.186 5.187 5.188 \subsection{\masqmail} 5.189 -The \masqmail\ program was written by Oliver Kurth, starting in 1999. 5.190 -His aim was to create a small \mta\ which is especially focused on computers with dial-up connections to the internet. 5.191 -\masqmail\ is easy configurable for situations which are rarely solveable with the common \MTA{}s. 5.192 +The \masqmail\ program was written by Oliver Kurth, starting in 1999. His aim was to create a small \mta\ which is especially focused on computers with dial-up connections to the internet. \masqmail\ is easy configurable for situations which are rarely solveable with the common \MTA{}s. 5.193 5.194 -\masqmail\ queues mail for destinations outside the local network if no connection to the internet is online. 5.195 -If the machine goes online, this mail is sent. 5.196 -Mail to local machines is sent immediately. 5.197 +\masqmail\ queues mail for destinations outside the local network if no connection to the internet is online. If the machine goes online, this mail is sent. Mail to local machines is sent immediately. 5.198 5.199 -While the other \MTA{}s are more general purpose \MTA{}s, \masqmail\ aims on special situations only. 5.200 -Nevertheless can it handle ordinary mail transfers too. 5.201 +While the other \MTA{}s are more general purpose \MTA{}s, \masqmail\ aims on special situations only. Nevertheless can it handle ordinary mail transfers too. 5.202 5.203 \masqmail\ is released under the \GPL, which makes it \freesw. The latest stable version is 0.2.21 from November 2005. 5.204
6.1 --- a/thesis/tex/1-Comparision.tex Tue Nov 04 11:33:15 2008 +0100 6.2 +++ b/thesis/tex/1-Comparision.tex Tue Nov 04 11:34:30 2008 +0100 6.3 @@ -1,6 +1,11 @@ 6.4 \chapter{Comparison of \MTA{}s} 6.5 6.6 +% http://shearer.org/MTA_Comparison 6.7 % http://www.geocities.com/mailsoftware42/ 6.8 +% http://fanf.livejournal.com/50917.html 6.9 +% http://archives.neohapsis.com/archives/postfix/2006-07/1762.html 6.10 +% http://www.oreillynet.com/lpt/a/6849 6.11 +% http://www.mailradar.com/mailstat/ 6.12 6.13 \section{First release} 6.14 sendmail: 1983
7.1 --- a/thesis/tex/1-Introduction.tex Tue Nov 04 11:33:15 2008 +0100 7.2 +++ b/thesis/tex/1-Introduction.tex Tue Nov 04 11:34:30 2008 +0100 7.3 @@ -3,71 +3,44 @@ 7.4 7.5 \section{History of electronic mail} 7.6 %TODO: have a quote from Bell Labs about email here 7.7 -%FIXME: add references to text 7.8 7.9 -Electronic mail\index{electronic mail} (short: \name{email}) is a basic concept in \unix. 7.10 -On \unix\ machines, a lot of information is distributed by \name{system mail}, which is email sent by the operating system. 7.11 -Beside that, email is the common communication system between humans working on computers. 7.12 +Electronic mail\index{electronic mail} (short: \name{email})\citeweb{wikipedia:email} is a basic concept in \unix.\citeweb{unix-mail-intro} On \unix\ machines, a lot of information is distributed by \name{system mail}, which is email sent by the operating system. Beside that, email is the common communication system between humans working on computers. 7.13 7.14 -The \unix\ operating system supports email through the \name{mail user agent} (\NAME{MUA}) \name{/bin/mail}. 7.15 +The \unix\ operating system supports email through the \name{mail user agent} (short: \NAME{MUA}) \name{/bin/mail}. 7.16 7.17 -As generally known, development of \unix\ was not only made in the \name{Bell Labratories} of \NAME{AT\&T}. 7.18 -The \name{Univerity of California at Berkeley} worked on their version of a \unix\ operating system, too. 7.19 -It is refered to as \NAME{UCB} \unix, or \name{Berkeley} \unix\index{Berkeley Unix}. 7.20 +Development of \unix\ was not only made in the \name{Bell Labratories} of \NAME{AT\&T}. The \name{Univerity of California at Berkeley} worked on their version of a \unix\ operating system, too. It is refered to as \NAME{UCB} \unix, or \name{Berkeley} \unix\index{Berkeley Unix}. 7.21 7.22 -The few features of \name{/bin/mail} lead to a second \NAME{MUA} from Berkeley: \name{Mail} (with a capital `M'). 7.23 -Later, the superior functionality of \name{Mail} went back to \name{Bell Labs} and into the program \name{mailx}, the successor of \name{/bin/mail}. 7.24 -The different programs for handling mail are a good example for the problem of standardization of \unix. 7.25 +The few features of \name{/bin/mail} lead to a second \NAME{MUA} from Berkeley: \name{Mail} (with a capital `M'). Later, the superior functionality of \name{Mail} went back to \name{Bell Labs} and into the program \name{mailx}, the successor of \name{/bin/mail}. 7.26 7.27 Nowadays, \name{mailx} and \name{Mail} are quite equivalent and \name{/bin/mail} is linked to either of them---whichever is installed. 7.28 7.29 -For transporting mail in between two systems, the \NAME{UUCP} program and protocol suite (for ``\unix\ to \unix\ copy'') was invented at \name{Bell Labs}. 7.30 -Berkeley however had an own creation called \name{Berknet} in use. %FIXME: why? license issues? closed source? 7.31 -Further more there was a third important network type: the \NAME{ARPAnet}, based on the \name{transmission control protocol} (\NAME{TCP}). %FIXME: where did it came from? 7.32 +At that time, computers were connected by various kinds of networks. \name{Bell Labs} had invented the \NAME{UUCP} program and protocol suite (for ``\unix\ to \unix\ copy'')\citeweb{wikipedia:uucp}. Berkeley however had an own creation called \name{Berknet} in use. And the \name{United States Department of Defence Advanded Research Projects Agency}'s (\NAME{ARPA}) effort on designing a new wide area network, led to the \NAME{ARPANET}\citeweb{wikipedia:arpanet}, based on the \name{transmission control protocol} (\NAME{TCP}). There were also other, minor, kinds of networks in use. 7.33 7.34 -Each of the three network types could transfer email between different machines. 7.35 -The file transfer itself was made using \NAME{FTP}, but the higher layered logic of the transfer was different in each. 7.36 -For example was the addressing schema not the same: \NAME{UUCP} used a flat-style schema, while \NAME{ARPAnet} was hierachical. 7.37 +Email was transfered between different machines within the same networks. The file transfer itself was made uniformly using \NAME{FTP}, but the higher layered logic of the transfer was different. For example was addressing done different: \NAME{UUCP} used a flat-style schema, while \NAME{ARPANET}'s was hierachical. 7.38 7.39 -Mail transport from one machine using one kind of network to a second machine using another kind was a problem. 7.40 -This showed up at Berkeley where some departments of the university had switched to \NAME{ARPAnet}, and some to \NAME{UUCP}, while the rest was \name{Berknet}. 7.41 +Mail transport from one machine connected to one kind of network to a second machine connected to another was a problem. This showed up at Berkeley where some departments of the university had switched to \NAME{ARPANET}, and some to \NAME{UUCP}, while the rest used \name{Berknet}. 7.42 7.43 -It was around 1982, when Eric Allman, then a student at Berkeley, wrote \name{delivermail}. 7.44 -Its purpose was to transform email from one network to another. 7.45 -\name{delivermail} like its successor, the more flexible \sendmail, intermediated between the different networks. 7.46 -They were able to transform email messages from any network to any other. 7.47 +It was around 1982, when Eric Allman, then a student at Berkeley, wrote \name{delivermail}. Its purpose was to transform email from one network to another. \name{delivermail}, like its successor---the more flexible \sendmail---intermediated between the different networks. They were able to transform email messages from any network to any other. 7.48 7.49 -Todays email structure is basicly the same as then. 7.50 -The major difference is the uniformity of the underlying network, which is nearly always the \NAME{ARPAnet}-based \name{Internet}. 7.51 -Most other differences are organized as extensions to the old model of electronic mail. 7.52 +Todays email structure is basicly the same as then. The major difference is the uniformity of the underlying network, which is nearly always the \NAME{ARPANET}-based \name{Internet}. Hence lowering the importance of the transformation capabilities of \MTA{}s, that was essential to \sendmail's success---yet being the primary motivation for the program. 7.53 7.54 -More information about electronic mail and its history can be found at: 7.55 -%FIXME: add books and websites here 7.56 +More information about the history of electronic mail can be found at: \citeweb{email:griffiths}, \citeweb{email:crocker}, \citeweb{email:vleck}, \citeweb{email:akkad}, \citeweb{email:murakami}, and \citeweb{email:tomlinson}. A good starting point for general information on internet history is \citeweb{wikipedia:historyoftheinternet}. 7.57 +%TODO: check the websites which ones are the important ones; remove unnessesary ones 7.58 7.59 -% http://www.helpdesk.umd.edu/documents/4/4804/ 7.60 -% http://www.networkcomputing.com/unixworld/tutorial/810.txt.html 7.61 -% http://www.livinginternet.com/i/iw_unix_war.htm 7.62 -% http://www.nobell.org/~gjm/about/ihnp4.html 7.63 -% http://en.wikipedia.org/wiki/E-mail 7.64 -% http://en.wikipedia.org/wiki/UUCP 7.65 -% http://en.wikipedia.org/wiki/ARPAnet 7.66 -% http://en.wikipedia.org/wiki/History_of_the_Internet 7.67 -% http://www.multicians.org/thvv/mail-history.html 7.68 -% http://openmap.bbn.com/~tomlinso/ray/firstemailframe.html 7.69 -% http://www.livinginternet.com/e/ei.htm 7.70 -% http://www.cs.ucsb.edu/~almeroth/classes/F04.176A/homework1_good_papers/jay-akkad.html 7.71 7.72 7.73 \section{Transporting mail} 7.74 -%TODO: include definitions from others here (cites) 7.75 %TODO: when was the term ``mail transfer agent'' established? 7.76 -The basic job of a \name{mail transfer agent} (or \index{mail transport agent|see{mail transfer agent}}\name{mail transport agent}, short \NAME{MTA}) is to transfer/transport \name{electronic mail} (short \name{email}) from one host to another. 7.77 7.78 -Here are definitions from various sources: 7.79 +This thesis is about a \name{mail transfer agent} (or \index{mail transport agent|see{mail transfer agent}}\name{mail transport agent}, short \NAME{MTA}): \masqmail. \sendmail\ is one too---the most important one. 7.80 + 7.81 +The basic job of a \mta\ is to transfer/transport electronic mail from one host to another. 7.82 + 7.83 +Here are definitions from others: 7.84 7.85 \begin{quotation} 7.86 -A mail transfer agent (MTA) is a highly specialized program that delivers mail and transports it between machines, like the post office. Usually there is only one MTA on a machine. The sendmail program is an MTA. 7.87 -\cite{sendmail} 7.88 +A mail transfer agent (MTA) is a highly specialized program that delivers mail and transports it between machines, like the post office. 7.89 +\cite{costales97} 7.90 \end{quotation} 7.91 7.92 \begin{quotation} 7.93 @@ -81,39 +54,41 @@ 7.94 \end{quotation} 7.95 7.96 \begin{quotation} 7.97 -Message Transfer Agent - (MTA, Mail Transfer Agent) Any program responsible for delivering e-mail messages. Upon receiving a message from a Mail User Agent or another MTA, often by SMTP over the Internet, it stores it temporarily locally and analyses the recipients and delivers it to any local addressees and/or forwards it to other remote MTAs (routing) for delivery to remote recipients. In either case it may edit and/or add to the message headers. 7.98 - 7.99 -The most widely used MTA for Unix is sendmail, which communicates using SMTP. 7.100 - 7.101 -RFC 2821 (SMTP) expands MTA as ``Mail Transfer Agent'' though this is less common. Alternatives with ``Transport'' are also seen but less correct. 7.102 +Message Transfer Agent - (MTA, Mail Transfer Agent): Any program responsible for delivering e-mail messages. Upon receiving a message from a Mail User Agent or another MTA, [...] it [...] delivers it to any local addressees and/or forwards it to other remote MTAs (routing) for delivery to remote recipients. 7.103 +%Any program responsible for delivering e-mail messages. Upon receiving a message from a Mail User Agent or another MTA, often by SMTP over the Internet, it stores it temporarily locally and analyses the recipients and delivers it to any local addressees and/or forwards it to other remote MTAs (routing) for delivery to remote recipients. In either case it may edit and/or add to the message headers. 7.104 +% 7.105 +%The most widely used MTA for Unix is sendmail, which communicates using SMTP. 7.106 +% 7.107 +%RFC 2821 (SMTP) expands MTA as ``Mail Transfer Agent'' though this is less common. Alternatives with ``Transport'' are also seen but less correct. 7.108 \citeweb{website:thefreedictionary} 7.109 \end{quotation} 7.110 7.111 -\begin{quotation} 7.112 -mail transfer agent (MTA) The program responsible for delivering e-mail messages. Upon receiving a message from a mail user agent or another MTA it stores it temporarily locally and analyses the recipients and either delivers it (local addressee) or forwards it to another MTA. In either case it may edit and/or add to the message headers. A widely used MTA for Unix is sendmail. 7.113 -\citeweb{website:faqs} 7.114 -\end{quotation} 7.115 +Common is the transfer of mail to other machines; this is the actual job. \MTA{}s work with mail, received from local users and/or remote machines. Mail delivery however is \emph{not} what \mta{}s are for, although probably every \MTA\ is able to deliver mail, and many do. \name{mail delivery agents} (short: \NAME{MDA}) are the programs for this job. Two of the best known \NAME{MDA}s are \name{procmail} and \name{maildrop}. 7.116 7.117 -\begin{quotation} 7.118 -Mail Transfer Agent (MTA): The means by which mail messages are transferred between machines over the Internet. 7.119 -\citeweb{website:freeserve.co.uk} 7.120 -\end{quotation} 7.121 7.122 7.123 \section{\sendmail} 7.124 \label{sec:sendmail} 7.125 -\name{sendmail} is the de facto standard for \name{mail transfer agents}. 7.126 7.127 -% FIXME: is that true? 7.128 -It was the first \NAME{MTA} and had no real alternative for a long time. 7.129 +Allman wrote it to transfer emails between different networks, thus giving \sendmail\ mighty address rewriting abilities. In contrast to its predecessor \name{delivermail}, was \sendmail\ designed to offer greatest flexiblity in configuration; this enabled it to deal with any type of network. 7.130 7.131 -Most other existing substitutes (on \unix\ systems), which are mainly \name{postfix}, \name{exim}, \name{qmail} and the here regarded \name{masqmail}, mimic \name{sendmail}'s interface. 7.132 -Especially, they all create a symbolic link named ``sendmail'' pointing to their own executable. 7.133 -This is because a lot of programs assume there is an executable called ``sendmail'' on every computer system existing. 7.134 +\sendmail\ was, and still is, very successful. So successful that it stands, like no other, for the whole group of \MTA{}s: \name{sendmail} actually is the \emph{de facto standard} for \mta{}s. 7.135 7.136 -Besides being the ``standard'', \name{sendmail} probably is the most scalable and powerful solution for transfering emails and definately the most flexible one. 7.137 +Its author, Allman, sees three reasons for the huge success: the ``sloopy'' approach (accepting badly formed messages); its focus on the routing function; and the flexible configuration (this was important in \sendmail's early days). 7.138 +\cite[page xviii]{costales97} 7.139 7.140 +Others see \sendmail's success more critical. One of them is quoted in the \name{MMDF} FAQs \citeweb{faqs:mmdf}: 7.141 +\begin{quotation} 7.142 +Sendmail was once compared by one old Internet hand to ``those killer bees that escaped from the laboratory---and now they're everywhere and you can't get rid of 'em''. 7.143 +\end{quotation} 7.144 +He definately hints here at \sendmail's many security vulnerabilities that came to light and on its complexity, in particular its obscure configuration file \path{sendmail.cf}. 7.145 7.146 +No matter how \sendmail\ is seen, one must admit its influence on \unix\ emailing programs. Most existing substitutes mimic \sendmail's interface and behavior. Most notable, they create a symbolic link named ``sendmail'' pointing to their own executable. The reason herefor are the many programs assuming an executable called ``sendmail'' on every computer system existing. 7.147 7.148 -\section{(a look at Windows)} 7.149 +\sendmail\ is not only ported to many platforms, even including \name{Microsoft Windows}, but also it is still the prefered \MTA\ on many systems. 7.150 7.151 +For deeper knowledge on \sendmail's history, see \cite{costales97} and \cite{vixie01}. 7.152 + 7.153 + 7.154 +\section{A look at Windows} 7.155 +% TODO: add content here
8.1 --- a/thesis/tex/1-Masqmail.tex Tue Nov 04 11:33:15 2008 +0100 8.2 +++ b/thesis/tex/1-Masqmail.tex Tue Nov 04 11:34:30 2008 +0100 8.3 @@ -4,13 +4,53 @@ 8.4 8.5 8.6 \section{Target field} 8.7 +Its original author, Oliver Kurth, sees \masqmail\ so: 8.8 +\begin{quotation} 8.9 +MasqMail is a mail server designed for hosts that do not have a permanent internet connection eg. a home network or a single host at home. It has special support for connections to different ISPs. It replaces sendmail or other MTAs such as qmail or exim. 8.10 +\end{quotation} 8.11 + 8.12 +\masqmail\ is inteded to cover a specific niche: non-permanent internet connection and different \NAME{ISP}s. 8.13 + 8.14 +Although it can basically replace other \MTA{}s, it is not generally aimed to do so. The package description of \debian\citeweb{packages.debian:masqmail} states this more clearly by changing the last sentence to: 8.15 +\begin{quotation} 8.16 +In these cases, MasqMail is a slim replacement for full-blown MTAs such as sendmail, exim, qmail or postfix. 8.17 +\end{quotation} 8.18 +\masqmail\ is a good replacement ``in these cases'', but not generally, since is lacks features essential for running on mail servers. It is primarily not secure enough for being accessable from untrusted locations. %Nevertheless has \masqmail\ this field of action, where it is better suited for than other \MTA{}s. 8.19 + 8.20 +The program is best used in home networks, which are non-permanently connected to the internet. \masqmail\ sends mail to local destinations, like users on the same machine and on other machines in the local net, immediately. Email to recipients outside the local net are queued when offline and sent when a online connection gets established. 8.21 + 8.22 +Further more does \masqmail\ respect online connections through different \NAME{ISP}s; a common thing for dial-up connections. In particular can different sender addresses be set, dependent on the \NAME{ISP} that is used. This prevents mail to be likely classified as spam. 8.23 + 8.24 8.25 8.26 \section{Typical usage} 8.27 +This section describes situations that make senseful use of \masqmail. 8.28 + 8.29 +A home network consisting of some workstations without a server. The network is connected to the internet by dial-up or broadband. Going online is initiated by computers inside the local net. \NAME{IP} addresses change at least once every day. 8.30 + 8.31 +Every workstation would be equiped with \masqmail. Mail transfer within the same machine or within the local net works straight forward. Outgoing mail to the internet is sent, to the concerning \NAME{ISP} for relaying, whenever the router goes online. Receiving of mail from outside needs to be done by a mail fetch program, like the \masqmail\ internal \NAME{POP3} client or \name{fetchmail} for example. The configuration for \masqmail\ would be the same on every computer, except the hostname. 8.32 + 8.33 +For the same network but having a server, one could have \masqmail\ running on the server and using simple forwarders (see \ref{subsec:relay-only}) to the server on the workstations. This setup does only support mail transfer to the server, but not back to a workstation; also sending mail to another user on the same workstation is not possible. 8.34 + 8.35 +A better setup is to run \masqmail\ on every machine %FIXME 8.36 + 8.37 +%How it works 8.38 +% 8.39 +%When offline, MasqMail queues all mail with a destination outside of the local network. When you connect to the internet, masqmail will be called with a connection name as an argument. MasqMail then sends the queued mail to the configured mailserver for that ISP. When a message from the local net is received when online, MasqMail delivers it immediately. If there is no mail server for that ISP, MasqMail can also send the mails directly to their destinations. 8.40 +% 8.41 +%For each ISP different return addresses can be configured. This makes it possible to get around spam traps which desire your return address to be from the same domain as the host the mail is coming from. This is not a problem if you always connect to a single ISP, but is one if you use different ones from time to time. It also makes it possible to configure your mailer to a return address on your local network which maybe totally unknown outside. So delivery failure messages originating on your local net can be sent directly to you, while those that occur outside will be sent to the configured address. (Note that the return path is different from the From: address or the Reply-to: address. You can still have a single address where you want replys to be sent to). 8.42 +% 8.43 +%When offline, MasqMail behaves just like any other ordinary mail server (with a few limitations, but these will be fixed in the future). 8.44 +% 8.45 +%To detect its online status, MasqMail can take advantage of the masqdialer system. But it also works well without it. 8.46 + 8.47 8.48 8.49 \section{What makes it special} 8.50 8.51 +As main advantage, \masqmail\ makes it easy to set up an \MTA\ on workstations or notebooks without the need to do complex configuration or to be an mail server expert. 8.52 + 8.53 +Workstations use 8.54 8.55 \section{Alternatives?} 8.56 % http://anfi.homeunix.org/sendmail/dialup10.html 8.57 @@ -19,6 +59,21 @@ 8.58 8.59 8.60 \section{Features} 8.61 +\begin{itemize} 8.62 + \item Delivers only when online to a destination 'outside' your LAN 8.63 + \item Support for multiple Providers (ie. Mail Servers, or direct delivery) 8.64 + \item Rewriting of Return addresses (Return-Path:, From:, Reply-To:), configurable for each Provider separately 8.65 + \item can also be used as a Mail Server on a LAN 8.66 + \item alias support 8.67 + \item delivery to pipes 8.68 + \item delivery to MDAs (eg. procmail) 8.69 + \item Maildir support (version >= 0.2.5) 8.70 + \item routing depending on sender 8.71 + \item AUTH (RFC 2554) support (as client, since version 0.1.0) 8.72 + \item SMTP-after-POP 8.73 + \item POP3 client 8.74 + \item POP3 client daemon (fetch mail in regular intervals if online) 8.75 +\begin{itemize} 8.76 8.77 8.78 \section{History}
9.1 --- a/thesis/thesis.sty Tue Nov 04 11:33:15 2008 +0100 9.2 +++ b/thesis/thesis.sty Tue Nov 04 11:34:30 2008 +0100 9.3 @@ -12,7 +12,7 @@ 9.4 9.5 \setlength{\parindent}{0em} 9.6 \setlength{\parskip}{1.0ex plus 1.0ex minus 0.5ex} 9.7 - \setcounter{tocdepth}{3} 9.8 + \setcounter{tocdepth}{1} 9.9 9.10 \pagestyle{headings} 9.11 %\pagestyle{fancy}