docs/masqmail-cs
diff masqmail.tex @ 4:1197518aa221
content about ch04
author | meillo@marmaro.de |
---|---|
date | Tue, 03 Mar 2009 13:40:07 +0100 |
parents | 40968008fe7c |
children | 282b52d9de09 |
line diff
1.1 --- a/masqmail.tex Mon Mar 02 15:15:06 2009 +0100 1.2 +++ b/masqmail.tex Tue Mar 03 13:40:07 2009 +0100 1.3 @@ -336,36 +336,36 @@ 1.4 1.5 1.6 1.7 -\frame{\ft{planned was} 1.8 - 1.9 -1) purpose and structure of an MTA/of masqmail 1.10 - 1.11 -2) security analysis 1.12 - 1.13 -3) code improvements 1.14 - 1.15 -4) documentation, test, distribution 1.16 - 1.17 -With the goal to release a new version and get it into Debian 1.18 - 1.19 -} 1.20 - 1.21 - 1.22 -\frame{\ft{however, it resulted in} 1.23 - 1.24 -1) introduction 1.25 - 1.26 -2) market analysis 1.27 - 1.28 -3) mail transfer agents 1.29 - 1.30 -4) masqmail's present and future 1.31 - 1.32 -5) improvement plans 1.33 - 1.34 -Became pretty theoretic (I don't worry) 1.35 - 1.36 -} 1.37 +%\frame{\ft{planned was} 1.38 +% 1.39 +%1) purpose and structure of an MTA/of masqmail 1.40 +% 1.41 +%2) security analysis 1.42 +% 1.43 +%3) code improvements 1.44 +% 1.45 +%4) documentation, test, distribution 1.46 +% 1.47 +%With the goal to release a new version and get it into Debian 1.48 +% 1.49 +%} 1.50 +% 1.51 +% 1.52 +%\frame{\ft{however, it resulted in} 1.53 +% 1.54 +%1) introduction 1.55 +% 1.56 +%2) market analysis 1.57 +% 1.58 +%3) mail transfer agents 1.59 +% 1.60 +%4) masqmail's present and future 1.61 +% 1.62 +%5) improvement plans 1.63 +% 1.64 +%Became pretty theoretic (I don't worry) 1.65 +% 1.66 +%} 1.67 1.68 1.69 1.70 @@ -473,7 +473,15 @@ 1.71 1.72 \frame{\ft{market shares} 1.73 1.74 -FIXME 1.75 +\input{tbl/mta-market-share.tbl} 1.76 + 1.77 +} 1.78 + 1.79 + 1.80 + 1.81 +\frame{\ft{comparison} 1.82 + 1.83 +\input{tbl/mta-comparison.tbl} 1.84 1.85 } 1.86 1.87 @@ -545,30 +553,55 @@ 1.88 1.89 \frame{\ft{functional requirements} 1.90 1.91 +\input{tbl/func-requirements.tbl} 1.92 + 1.93 } 1.94 1.95 \frame{\ft{non-functional requirements} 1.96 1.97 -} 1.98 - 1.99 -\frame{\ft{architectural requirements} 1.100 +\input{tbl/nonf-requirements.tbl} 1.101 1.102 } 1.103 1.104 -\frame{\ft{fulfilled requirements} 1.105 +\frame{\ft{work tasks} 1.106 + 1.107 +TODO\,1: Encryption 1.108 + 1.109 +TODO\,2: Authentication 1.110 + 1.111 +TODO\,3: Security 1.112 + 1.113 +TODO\,4: Reliability 1.114 + 1.115 +TODO\,5: Spam handling 1.116 + 1.117 +TODO\,6: Extendability 1.118 + 1.119 1.120 } 1.121 1.122 -\frame{\ft{work to do} 1.123 + 1.124 +\frame{\ft{further development} 1.125 + 1.126 +- improve existing code 1.127 + 1.128 +- add wrappers and interposition filters 1.129 + 1.130 +- redesign and rewrite from scratch 1.131 1.132 } 1.133 1.134 1.135 -\frame{\ft{further development} 1.136 +\frame{\ft{architecture} 1.137 + 1.138 +\begin{center} 1.139 +\includegraphics[width=0.8\textwidth]{fig/callgraph.eps} 1.140 +\end{center} 1.141 1.142 } 1.143 1.144 1.145 + 1.146 \frame{\ft{the result} 1.147 1.148 ``one fits all'' is not possible