docs/diploma
diff thesis/tex/4-MasqmailsFuture.tex @ 129:5a122d28f1ca
moved some comment lines
author | meillo@marmaro.de |
---|---|
date | Tue, 09 Dec 2008 18:01:42 +0100 |
parents | 098bd0876934 |
children | a83a29e10b10 |
line diff
1.1 --- a/thesis/tex/4-MasqmailsFuture.tex Tue Dec 09 18:01:20 2008 +0100 1.2 +++ b/thesis/tex/4-MasqmailsFuture.tex Tue Dec 09 18:01:42 2008 +0100 1.3 @@ -2,6 +2,22 @@ 1.4 1.5 << plans to get masqmail more popular again (if that is the goal) >> %FIXME 1.6 1.7 +architecture: 1.8 +(ssl) -> msg-in (local or remote protocol handlers) -> spam-filter (and more) -> queue -> msg-out (local-delivery by MDA, or remote-protocol-handlers) -> (ssl) 1.9 + 1.10 + 1.11 +http://fanf.livejournal.com/50917.html %how not to design an mta - the sendmail command 1.12 +http://fanf.livejournal.com/51349.html %how not to design an mta - partitioning for security 1.13 +http://fanf.livejournal.com/61132.html %how not to design an mta - local delivery 1.14 +http://fanf.livejournal.com/64941.html %how not to design an mta - spool file format 1.15 +http://fanf.livejournal.com/65203.html %how not to design an mta - spool file logistics 1.16 +http://fanf.livejournal.com/65911.html %how not to design an mta - more about log-structured MTA queues 1.17 +http://fanf.livejournal.com/67297.html %how not to design an mta - more log-structured MTA queues 1.18 +http://fanf.livejournal.com/70432.html %how not to design an mta - address verification 1.19 +http://fanf.livejournal.com/72258.html %how not to design an mta - content scanning 1.20 + 1.21 + 1.22 + 1.23 << concrete decisions based on results of the last 2 chapters >> %FIXME 1.24 1.25 \section{Existing features}