Mercurial > docs > diploma

annotate thesis/tex/4-MasqmailsFuture.tex @ 175:aab8499c9f2f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
moved ch06s content into other chapters to remove it
author meillo@marmaro.de
date Fri, 26 Dec 2008 15:54:46 +0100
parents c51f1be54224
children 7781ad0811f7
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
109
de590ff06051 changes suggested by schaeffter
meillo@marmaro.de
parents: 99
diff changeset
1 \chapter{\masqmail's present and future}
93
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
2
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
3 \section{Existing code base}
142
1b0ba5151d1b person names in small caps
meillo@marmaro.de
parents: 140
diff changeset
4 Here regarded is version 0.2.21 of \masqmail. This is the last version released by Oliver \person{Kurth}, and the basis for my thesis.
1b0ba5151d1b person names in small caps
meillo@marmaro.de
parents: 140
diff changeset
5
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
6
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
7 \subsubsection*{Features}
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
8
142
1b0ba5151d1b person names in small caps
meillo@marmaro.de
parents: 140
diff changeset
9 \masqmail\ accepts mail on the command line and via \SMTP. Mail queueing and alias expansion is supported. \masqmail\ is able to deliver mail to local mailboxes (in \name{mbox} or \name{maildir} format) or pass it to a \name{mail delivery agent} (like \name{procmail}). Mail destinated to remote locations is sent using \SMTP\ or can be piped to commands, being gatesways to \NAME{UUCP} or \NAME{FAX} for example.
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
10
142
1b0ba5151d1b person names in small caps
meillo@marmaro.de
parents: 140
diff changeset
11 Outgoing \SMTP\ connections feature \SMTP-\NAME{AUTH} and \SMTP-after-\NAME{POP} authentication, but incoming connections do not. Using wrappers for outgoing connections is supported. This offers a two way communication through a wrapper application like \name{openssl}.
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
12 %todo: what about SSL/TLS encryption?
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
13
142
1b0ba5151d1b person names in small caps
meillo@marmaro.de
parents: 140
diff changeset
14 \masqmail\ focuses on non-permanent online connections, thus a concept of online routes is used. One may configure any amount of routes to send mail. Each route can have criterias, like matching \texttt{From:} or \texttt{To:} headers, to determine if mail is allowed to be sent using it. Mail to destinations outside the local net gets queued until \masqmail\ is informed about the existance of a online connection.
1b0ba5151d1b person names in small caps
meillo@marmaro.de
parents: 140
diff changeset
15
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
16 The \masqmail\ executable can be called under various names for sendmail-compatibility reasons. This is organized by symbolic links with different names pointing to the \masqmail\ executable. The \sendmail\ names are \path{/usr/lib/sendmail} and \path{/usr/sbin/sendmail} because many programs expect the \mta\ to be located there. Further more \sendmail\ supports calling it with a different name instead of supplying command line arguments. The best known of this shortcuts is \path{mailq}, which is equivilent to calling it with the argument \verb+-bq+. \masqmail\ recognizes the names \path{mailq}, \path{smtpd}, \path{mailrm}, \path{runq}, \path{rmail}, and \path{in.smtpd}. The first two are inspired by \sendmail. Not implemented is the name \path{newaliases} because \masqmail\ does not generate binary representations of the alias file.\footnote{A shell script located named \path{newaliases}, that invokes \texttt{masqmail -bi}, can provide the command to satisfy other software needing it.} \path{hoststat} and \path{purgestat} are missing for sendmail-compatibility.
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
17 %masqmail: mailq, mailrm, runq, rmail, smtpd/in.smtpd
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
18 %sendmail: hoststat, mailq, newaliases, purgestat, smtpd
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
19
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
20 Additional to the \mta\ job, \masqmail\ also offers mail retrieval services with being a \NAME{POP3} client. It can fetch mail from different remote locations, dependent on the active online route.
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
21
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
22
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
23
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
24 \subsubsection*{The code}
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
25
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
26 \masqmail\ is written in the C programming language. The program, as of version 0.2.21, consists of 34 source code and eight header files, containing about 9,000 lines of code\footnote{Measured with \name{sloccount} by David A.\ Wheeler.}. Additionally, it includes a \name{base64} implementation (about 300 lines) and \name{md5} code (about 150 lines). For systems that do not provide \name{libident}, this library is distributed as well (circa 600 lines); an available shared library however has higher precedence in linking.
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
27
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
28 The only mandatory dependency is \name{glib}---a cross-platform software utility library, originated in the \NAME{GTK+} project. It provides safer replacements for many standard library functions. It also offers handy data containers, easy-to-use implementations of data structures, and much more.
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
29
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
30
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
31 With \masqmail\ comes the small tool \path{mservdetect}; it helps setting up a configuration that uses the \name{mserver} system to detect the online state. Two other binaries get compiled for testing purposes: \path{readtest} and \path{smtpsend}. All three programms use \masqmail\ source code; they only add a file with a \verb+main()+ function each.
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
32
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
33
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
34 \masqmail\ does not provide an interface to plug in modules with additional functionality. There exists no add-on or module system. The code is only separated by function to the various source files. Some functional parts can be included or excluded by defining symbols. Adding maildir support at compile time, means giving the option \verb+--enable-maildir+ to the \path{configure} call. This preserves the concerning code to get removed by the preprocessor. Unfortunately the \verb+#ifdef+s are scattered through all the source, leading to a FIXME(holperig) code base.
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
35
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
36
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
37
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
38
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
39
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
40 \section{\masqmail\ next generation}
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
41
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
42 \subsection{Requirements}
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
43
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
44 Following is a list of current and future requirements to make \masqmail\ ready for the future.
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
45
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
46
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
47 \subsubsection*{Large message handling}
155
0b17f6e5edae new books; websites to books
meillo@marmaro.de
parents: 149
diff changeset
48 Trends in the market for electronic communication go towards consolidated communication, hence email will be used more to transfer voice and video messages. This leads to larger messages. The store-and-forward transport of email is not good suited for large data. Thus new protocols, like \NAME{QMTP} (described in section %\ref{FIXME}
0b17f6e5edae new books; websites to books
meillo@marmaro.de
parents: 149
diff changeset
49 ), may become popular.
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
50
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
51
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
52 \subsubsection*{Ressource friendly software}
149
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
53 The merge of communication hardware and the move of email services from providers to homes, demands smaller and more resource-friendly software. The amount of mail will be lower, even if much more mail will be sent. More important will be the energy consumption and heat emission. These topics increased in relevance during the past years and they are expected to become more central. \masqmail\ is not a program to be used on large servers, but to be used on small devices. Thus focusing on energy and heat, not on performance, is the direction to go.
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
54
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
55
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
56 \subsubsection*{New mail transfer protocols}
149
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
57 Large messages demand more efficient transport through the net. As well is a final solution needed to defeat the spam problem. New mail transport protocols may be the only good solutions for both problems. They also can improve reliability, authentication, and verification issues. \masqmail\ should be able to support new protocols as they appear and are used.
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
58
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
59
149
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
60 \subsubsection*{Spam handling}
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
61 Spam is a major threat. According to the \NAME{SWOT} analysis, the goal is to reduce it to a bearable level. Spam fighting is a war are where the good guys tend to lose. Putting too much effort there will result in few gain. Real success will only be possible with new---better---protocols and abandonning the weak legacy technologies. Hence \masqmail\ should be able to provide state-of-the-art spam protection, but not more.
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
62
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
63
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
64 \subsubsection*{Security}
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
65 \MTA{}s are critical points for computer security, as they are accessable from external networks. They must be secured with high effort. Properties like high priviledge level, work load influenced from extern, work on unsafe data, and demand for reliability, increase the security needed. Unsecure and unreliable \mta{}s are of no value. \masqmail\ needs to b e secure enough for its target field of operation.
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
66
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
67
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
68 \subsubsection*{Easy configuration}
149
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
69 Having \mta{}s on many home servers and clients, requires easy and standardized configuration. The common setups should be configurable with single actions by the user. Complex configuration should be possible, but focused must be the most common form of configuration: choosing one of several standard setups.
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
70
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
71
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
72
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
73
137
c60b164bfd3c rearranging of ch04
meillo@marmaro.de
parents: 133
diff changeset
74
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
75
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
76 \subsection{Discussion on architecture}
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
77
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
78 A program's architecture is probably the most influencing design decision, and has the greatest impact on the program's future capabilities. %fixme: search quote ... check if good
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
79
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
80 \masqmail's current artitecture is monolitic like \sendmail's and \exim's. But more than the other two, is it one block of interweaved code. \sendmail\ provides now, with its \name{milter} interface, standardized connection channels to external modules. \exim\ has a highly structured code with many internal interfaces, like the one for supported authentication ``modules''. \masqmail\ has none of them; it is what \sendmail\ was in the beginning: a single large block.
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
81
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
82 Figure \ref{fig:masqmail-arch} is an attempt to depict \masqmail's internal structure.
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
83
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
84 \begin{figure}
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
85 \begin{center}
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
86 \input{input/masqmail-arch.tex}
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
87 \end{center}
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
88 \caption{Internal architecture of \masqmail}
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
89 \label{fig:masqmail-arch}
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
90 \end{figure}
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
91
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
92 \sendmail\ improved its old architecture, for example by adding the milter interface. \exim\ was designed and is carefully maintained with a modular-like code structure in mind. \qmail\ started from scratch with a ``security-first'' approach, \postfix\ improved on it, and \name{sendmail X}/\name{MeTA1} tries to adopt the best of \qmail\ and \postfix, to completely replace the old \sendmail\ architecture. \person{Hafiz} \cite{hafiz05}. describes this evolution of \mta\ architecture very well.
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
93
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
94 Every one of the popular \MTA{}s is more modular, or became more modular over time, than \masqmail\ is. Modern requirements like spam protection and future requirements like the use of new mail transport protocols demand modular designs for keeping the software simple. Simplicity is a key property for security.
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
95
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
96 \person{Hafiz} agrees:
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
97 \begin{quote}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
98 The goal of making software secure can be better achieved by making the design simple and easier to understand and verify. \cite[page64]{hafiz05}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
99 \end{quote}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
100 He identifies the security of \qmail\ to come from it's \name{compartmentalization}, which goes hand in hand with modularity:
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
101 \begin{quote}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
102 A perfect example is the contrast between the feature envy early \sendmail\ architecture implemented as one process and the simple, modular architecture of \qmail. The security of \qmail\ comes from its compartmentalized simple processes that perform one task only and are therefor testable for security. \cite[page 64]{hafiz05}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
103 \end{quote}
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
104 As well does \person{Dent}: ``The modular architecture of Postfix forms the basis for much of its security.''\cite[page 7]{dent04}
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
105
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
106 Modularity is needed for supporting modern \MTA\ requirements, providing a clear interface to add further functionality without increasing the overall complexity much. Modularity is also an enabler for security. Security comes from good design, as \person{Graff} and \person{van Wyk} explain:
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
107 \begin{quote}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
108 Good design is the sword and shield of the security-conscious developer. Sound design defends your application from subversion or misuse, protecting your network and the information on it from internal and external attacks alike. It also provides a safe foundation for future extensions and maintainance of the software.
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
109 %
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
110 %Bad design makes life easier for attackers and harder for the good guys, especially if it contributes to a false sends of security while obscuring pertinent failings.
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
111 \cite[page 55]{graff03}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
112 \end{quote}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
113
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
114 \person{Hafiz} adds: ``The major idea is that security cannot be retrofitted into an architecture.''\cite[page 64]{hafiz05}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
115
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
116 All this leads to one logical step: The rewrite of \masqmail\ using a modern, modular architecture, to get a modern \MTA\ satisfying nowadays needs.
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
117
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
118
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
119
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
120
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
121 \subsection{Jobs of an MTA}
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
122
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
123 This section tries to identify the needed modules for a modern \MTA. They are later the pieces of which the new architecture is built of.
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
124
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
125 The basic job of a \mta\ is to tranport mail from a sender to a recipient. This is the definition of such a program and this is how \person{Dent}\cite[page 19]{dent04} and \person{Hafiz} \cite[pages 3-5]{hafiz05} generally see its design.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
126
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
127 An \MTA\ therefor needs at least a mail receiving facility and a mail sending facility. Additionally probably all \MTA\ developers (excluded the only forwarders), see the need for a mail queue. A mail queue removes the need to deliver at once a message is received. They also provide fail-safe storage of mails until they are delivered.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
128
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
129
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
130
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
131 \subsubsection*{Incoming channels}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
132
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
133 \sendmail-compatible \mta{}s must support at least two incoming channels: mail submitted using the \sendmail\ command, and mail received via the \SMTP\ daemon. It is therefor common to split the incoming channel into local and remote. This is done by \qmail\ and \postfix. The same way is \person{Hafiz}'s view.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
134
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
135 In contrast is \name{sendmail X}: Its locally submitted messages go to the \SMTP\ daemon, which is the only connection towards the mail queue. %fixme: is it a smtp dialog? or a second door?
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
136 \person{fanf} proposes a similar approach. He wants the \texttt{sendmail} command to be a simple \SMTP\ client that contacts the \SMTP\ daemon of the \MTA\ like it is done by connections from remote. The advantage here is one single module where all \SMTP\ dialog with submitters is done. Hence one single point to accept or refuse incoming mail. Additionally does the module to put mail into the queue not need to be \name{setuid} or \name{setgid} because it is only invoked from the \SMTP\ daemon. The \MTA's architecture would become simpler and common tasks are not duplicated in modules that do similar jobs.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
137
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
138 But merging the input channels in the \SMTP\ daemon makes the \MTA\ heavily dependent on \SMTP\ being the main mail transfer protocol. To \qmail\ and \postfix\ new modules to support other ways of message receival may be added without change of other parts of the system. Also is it better to have more independent modules if each one is simpler then.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
139
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
140 With the increasing need for new protocols in mind, it seems better to have single modules for each incoming channel, although this leads to duplicated acceptance checks.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
141
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
142
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
143 \subsubsection*{Outgoing channels}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
144
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
145 Outgoing mail is commonly either sent using \SMTP, piped into local commands (for example \texttt{uucp}), or delivered locally by appending to a mailbox.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
146
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
147 Outgoing channels are similar for \qmail, \postfix, and \name{sendmail X}: All of them have a module to send mail using \SMTP, and one for writing into a local mailbox. Local mail delivery is a job that requires root priveledge to be able to switch to any user in order to write to his mailbox. Modular \MTA{}s do not need \name{setuid root}, but the local delivery process (or its parent) needs to run as root.
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
148
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
149 As mail delivery to local users, is \emph{not} included in the basic job of an \MTA{}, why should it care about it? In order to keep the system simple and to have programs that do one job well, the local delivery job should be handed over to a specialist: the \name{mail delivery agent}. \NAME{MDA}s know about the various mailbox formats and are aware of the problems of concurrent write access and thelike. Hence handling the message and the responsiblity over to a \NAME{MDA}, like \name{procmail} or \name{maildrop}, seems to be the right way to go.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
150
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
151 This means an outgoing connection that pipes mail into local commands is required. Other outgoing channels, one for each supportet protocol, may be designed like it was done in other \MTA{}s.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
152
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
153
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
154
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
155 \subsubsection*{Mail queue}
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
156
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
157 Mail queues are probably used in all \mta{}s, excluding the simple forwarders. A mail queue is a essential requirement for \masqmail, as it is to be used for non-permanent online connections. This means, mail must be queued until a online connection is available to send the message.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
158
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
159 The mail queue and the module to manage it are the central part of the whole system. This demands especially for robustness and reliability, as a failure here can lead to loosing mail. An \MTA\ takes over responsibility for mail in accepting it, hence loosing mail messages is absolutely to avoid. This covers any kind of crash situation too. The worst thing acceptable to happen is a mail to be sent twice.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
160
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
161 \sendmail, \exim, \qmail, \name{sendmail X}, and \masqmail\ feature one single mail queue. \postfix\ has three of them: \name{incoming}, \name{active}, and \name{deferred}. (The \name{maildrop} queue is excluded, as it is only used for the \texttt{sendmail} command.)
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
162
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
163 \MTA\ setups that include content scanning tend to require two separate queues. To use \sendmail\ in such setups requires two independent instances, with two separate queues, running. \exim\ can handle it with special \name{router} and \name{transport} rules, but the data flow gets complicated. Hence an idea is to use two queues, \name{incoming} and \name{active} in \postfix's terminology, with the content scanning within the move from \name{incoming} to \name{active}.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
164
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
165
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
166
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
167 \subsubsection*{Sanitize mail}
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
168
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
169 Mail coming into the system often lacks important header lines. At least the required ones must be added from the \MTA. A good example is the \texttt{Message-Id:} header.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
171 In \postfix, this is done by the \name{cleanup} module, which invokes \name{rewrite}. The position in the message flow is after coming from one of the several incoming channels and before the message is stored into the \name{incoming} queue. Modules that handle incoming channels may also add headers, for example the \texttt{From:} and \texttt{Date:} headers. \name{cleanup}, however, does a complete check to make the mail header complete and valid.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
172
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
173 Apart from deciding where to sanitize the mail header, is the question where to generate the envelope. The envelope specifies the actual recipient of the mail, no matter what the \texttt{To:}, \texttt{Cc:}, and \texttt{Bcc:} headers tell. Multiple reciptients lead to multiple different envelopes, containing all the same mail message.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
174
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
175
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
176
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
177 \subsubsection*{Choose route to use}
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
178
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
179 One key feature of \masqmail\ is its ability to send mail out in different ways. The decision is based on the current online state and whether a route may be used for a message or not. The online state can be retrieved in tree ways, explained in \ref{sec:fixme}. A route to send is found by checking every available route for being able to transfer the current message, until one matches.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
180
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
181 This functionality should be implemented in the module that is responsible to invoke one of the outgoing channel modules (for example the one for \SMTP\ or the pipe module).
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
182
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
183 \masqmail\ can rewrite the envelope's from address and the \texttt{From:} header, dependent on the outgoing route to use. This rewrite must be done \emph{after} it is clear which route a mail will take, of course, so this may be not the module where other header editing is done.
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
184
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
185
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
186
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
187 \subsubsection*{Aliasing}
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
188
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
189 Where should aliases get expanded? They appear in different kind. Important are the ones available in the \path{aliases} file. Aliases can be:
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
190 \begin{itemize}
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
191 \item a different local user (e.g.\ ``\texttt{bob: alice}'')
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
192 \item a remote user (e.g.\ ``\texttt{bob: john@example.com}'')
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
193 \item a list of users (e.g.\ ``\texttt{bob: alice, john@example.com}'')
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
194 \item a command (e.g.\ ``\texttt{bob: |foo}'')
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
195 \end{itemize}
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
196 Addresses expanding to lists of users lead to more envelopes. Aliases changing the reciptients domain part may require a different route to use.
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
197
172
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
198 Aliasing is often handled in expanding the alias and reinjecting the mail into the system. Unfortunately, the mail is processed twice then; additionally does the system have to handle more mail this way. If it is wanted to check the new recipient address for acceptance and do all processing again, then reinjecting it is the best choice.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
199
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
200
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
201
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
202 \subsubsection*{Authentication}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
203
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
204 One thing to avoid is being an \name{open relay}. Open relays allow to relay mail from everywhere to everywhere. This is a major source of spam. The solution is restricting relay\footnote{Relaying is passing mail, that is not from and not for the own system, through it.} access.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
205
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
206 Several ways to restrict access are available. The most simple one is restrictiction by the \NAME{IP} address. No extra complexity is added this way, but static \NAME{IP} addresses are mandatory. This kind of restriction may be enabled using the operating system's \path{hosts.allow} and \path{hosts.deny} files. To allow only connections to port 25 from localhost or the local network \texttt{192.168.100.0/24} insert the line ``\texttt{25: ALL}'' into \path{hosts.deny} and ``\texttt{25: 127.0.0.1, 192.168.100.}'' into \path{hosts.allow}.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
207
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
208 If static access restriction is not possible, for example if mail from locations with changing \NAME{IP} addresses wants to be accepted, some kind of authentication mechanism is required. Three common kinds exist:
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
209 \begin{enumerate}
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
210 \item \SMTP-after-\NAME{POP}: uses authenication on the \NAME{POP} protocol to permit incoming \SMTP\ connections for a limited time afterwards.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
211 \item \SMTP authentication: is an extension to \SMTP. Authentication can be requested before mail is accepted.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
212 \item Certificates: confirm the identity of someone.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
213 \end{enumerate}
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
214 The first mechanism requires a \NAME{POP} (or \NAME{IMAP}) server running on the same host (or a trusted one), to enable the \SMTP\ server to use the login dates on the \NAME{POP} server. This is a common practice used by mail service providers, but is not adequate for the environments \masqmail\ is designed for.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
215
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
216 Certificate based authentication, like provided by \NAME{TLS}, suffers from the overhead of certificate management. But \NAME{TLS} provides encryption too, so is useful anyway.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
217
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
218 \SMTP\ authentication (also refered to as \NAME{SMTP-AUTH}) suppoert is easiest received by using a \name{Simple Authentication and Security Layer} implementation. \person{Dent} sees in \NAME{SASL} the best solution for authenticating dynamic users:
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
219 \begin{quote}
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
220 %None of these add-ons is an ideal solution. They require additional code compiled into your existing daemons that may then require special write accesss to system files. They also require additional work for busy system administrators. If you cannot use any of the nonauthenticating alternatives mentioned earlier, or your business requirements demand that all of your users' mail pass through your system no matter where they are on the Internet, SASL is probably the solution that offers the most reliable and scalable method to authenticate users.
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
221 None of these [authentication methods] is an ideal solution. They require additional code compiled into your existing daemons that may then require special write accesss to system files. They also require additional work for busy system administrators. If you cannot use any of the nonauthenticating alternatives mentioned earlier, or your business requirements demand that all of your users' mail pass through your system no matter where they are on the Internet, \NAME{SASL} is probably the solution that offers the most reliable and scalable method to authenticate users.
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
222 \cite[page 44]{dent04}
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
223 \end{quote}
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
224
170
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
225 %either by
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
226 %- network/ip address
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
227 % easiest: restricting by static IP addresses (Access control via hosts.allow/hosts.deny)
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
228 %or
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
229 %- some kind of auth (for dynamic remote hosts)
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
230 % adds complexity
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
231 % - SASL
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
232 % - POP/IMAP: pop-before-smtp, DRAC, WHOSON
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
233 % - TLS (certificates)
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
234
204683bfb4e7 wrote much about modules of an MTA
meillo@marmaro.de
parents: 167
diff changeset
235
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
236
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
237 \subsubsection*{Encryption}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
238
172
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
239 Electronic mail is very weak to sniffing attacks, because all data transfer is unencrypted. This concerns the message's content, as well as the email addresses in header and envelope, but also authentication dialogs that may transfer plain text passwords (\NAME{PLAIN} and \NAME{LOGIN} are examples). Adding encryption is therefor wanted.
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
240
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
241 The common way to encrypt \SMTP\ dialogs is using \name{Transport Layer Security} (short: \TLS, successor of \NAME{SSL}). \TLS\ encrypts the datagrams of the \name{transport layer}. This means it works below the application protocols and can be used by any of them\citeweb{wikipedia:tls}.
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
242
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
243 \TLS\ allows to create secure tunnels through which arbitrary programs can communicate. Hence one can add secure communication afterwards to programs without changing them. \name{OpenSSL} for example---a free implementation---allows traffic to be piped into a command; a secure tunnel is created and the traffic is forwarded through it. Or a secure tunnel can be set up between a local and a remote port; this tunnel can then be used by any application.
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
244
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
245 The \NAME{POP} protocol, for example, is good suited for such tunneling, but \SMTP\ is is not generally. Outgoing \SMTP\ client connections can be tunneled without problem---\masqmail\ already provides a configure option called \texttt{wrapper} to do so. Tunneling incomming connections to a server leads to problems with \SMTP. As data comes encrypted through the tunnel to the receiving host and gets then decrypted and forwarded on local to the port the application listens on. From the \MTA's view, this makes all connections appear to come from localhost, unfortunately. Figure \ref{fig:stunnel} depicts the data flow.
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
246
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
247 \begin{figure}
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
248 \begin{center}
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
249 \input{input/stunnel.tex}
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
250 \end{center}
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
251 \caption{Data flow using \name{stunnel}}
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
252 \label{fig:stunnel}
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
253 \end{figure}
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
254
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
255 For incoming connections, \NAME{STARTTLS}---defined in \RFC2487---is what \mta{}s implement.
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
256
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
257 \masqmail\ is already able to encrypt outgoing connections, but encryption of incoming connections, using \NAME{STARTTLS} should be implemented. This only affects the \SMTP\ server module.
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
258
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
259 %TLS/SSL prevents attackers to listen on the cable
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
260 %but it does not prevent man-in-the-middle attacks
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
261 %signed certificates help here
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
262 % or PGP encryption
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
263
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
264
172
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
265 %do not use stunnel wit SMTP:
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
266 %because all incoming mail would be from 127.0.0.1 !!
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
267 %use STARTTLS instead
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
268
172
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
269 %postfix: main.cf
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
270 %\begin{verbatim}
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
271 % smtpd_use_tls = yes
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
272 % smtpd_tls_received_header = no (does not log in received headers)
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
273 %
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
274 % smtpd_tls_key_file = /etc/postfix/key.pem
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
275 % smtpd_tls_cert_file = /etc/postfix/cert.pem
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
276 % smtpd_tls_CA_file = /etc/postfix/CAcert.pem
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
277 %
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
278 % smtp_use_tls = yes (use TLS for sending)
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
279 % smtp_tls_key_file = /etc/postfix/key.pem
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
280 % smtp_tls_cert_file = /etc/postfix/cert.pem
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
281 % smtp_tls_CA_file = /etc/postfix/CAcert.pem
5c873e6478ef wrote about encryption
meillo@marmaro.de
parents: 170
diff changeset
282 %\end{verbatim}
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
283
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
284
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
285
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
286
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
287 \subsubsection*{Spam prevention}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
288
173
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
289 Spam is a major threat to email, as described in section \ref{sec:swot-analysis}. The two main problems are forgable sender addresses and that it is cheap to send hundreds of thousands of messages. Hence, spam senders can operate in disguise and have minimal cost.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
290
173
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
291 As spam is not just a nuisance for end users, but also for the infrastructure---the \mta{}s---by increasing the amount of mail messages, \MTA{}s need to protect themself. Two approaches are used.
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
292
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
293 First refusing spam during the \SMTP\ dialog. This is the way it was meant by the designers of the \SMTP\ protocol. They thought checking the sender and reciptient mail addresses would be enough, but as they are forgable it is not. More and more complex checks need to be done. Checking needs time, but \SMTP\ dialogs time out if it takes too long. Thus only limited time can be used, during the \SMTP\ dialog, for checking if a message seems to be spam. The advantage is that acceptance of bad messages can be simply refused---no responsibility for the message is takes and no further system load is added.
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
294
173
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
295 Second checking for spam after the mail was accepted and queued. Here more processing time can be invested, so more detailed checks can be done. But, as responsibility for messages was taken by accepting them, it is no choice to simply delete spam mail. Checks for spam do not lead to sure results, they just indicate the possibility the message is unwanted mail. \person{Eisentraut} indicates actions to take after a message is recognized as probably spam \cite[pages 18--20]{eisentraut05}. The only acceptable one, for mail the \MTA\ is responsible for, is adding further or rewriting existent header lines. Thus all further work on the message is the same as for non-spam messages.
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
296
173
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
297 Modern \MTA{}s use both techniques in combination. Checks during the \SMTP\ dialog tend to be implemented in the \mta\ to make it fast; checks after the message was queued are often done using external programs (\name{spamassassin} is a well known one). \person{Eisentraut} sees the checks during the \SMTP\ dialog to be essentiell: ``Ganz ohne Analyse während der SMTP-Phase kommt sowieso kein MTA aus, und es ist eine Frage der Einschätzung, wie weit man diese Phase belasten möchte.''\cite[page 25]{eisentraut05} (translated: ``No \MTA\ can go without analysis during the \SMTP\ dialog, anyway, and it is a question of estimation how much to stress this period.'')
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
298
173
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
299 \NAME{DNS} blacklists (short: \NAME{DNSBL}) and \name{greylisting} are checks to be done before accepting the message. Invoking \name{spamassassin}, to add headers containing the estimated spam probability, is best to be invoked after the message is queued.
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
300
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
301
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
302
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
303
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
304 \subsubsection*{Virus checking}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
305
173
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
306 Related to spam is malicous content (short: \name{malware}) like viruses, worms, trojan horses. They, in contrast to spam, do not affect the \MTA\ itself, as they are in the mail body. The same situation in the real world is post offices opening letters to check if they contain something that could harm the recipient. This is not a mail transport concern. Apart of not being the right program to do the job, the \MTA\---the one which is responsible for the recipient---is at a good position to do this work.
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
307
173
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
308 In any way should malware checking be done by external programs that may be invoked by the \mta. But using mail deliver and processing agents, like \name{procmail}, appear to be better suited locations to invoke content scanners.
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
309
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
310
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
311
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
312 AMaViS (amavisd-new): email filter framework to integrate spam and virus scanner
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
313 \begin{verbatim}
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
314 internet -->25 MTA -->10024 amavis -->10025 MTA --> reciptient
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
315 | |
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
316 +----------------------------+
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
317 \end{verbatim}
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
318
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
319 postfix and exim can habe both mta servises in the same instance, sendmail needs two instances running.
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
320
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
321 MailScanner:
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
322 incoming queue --> MailScanner --> outgoing queue
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
323
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
324 postfix: with one instance possible, exim and sendmail need two instances running
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
325
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
326
173
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
327 %message body <-> envelope, header
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
328 %
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
329 %anti-virus: clamav
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
330 %postfix: via amavis
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
331 %exim: via content-scanning-feature called from acl
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
332 %sendmail: with milter
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
333 %procmail
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
334 %
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
335 %virus scanner work on file level
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
336 %amavis receives mail via smtp or pipe, splits it in its parts (MIME) and extracks archives, the come the virus scanners
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
337 %if the mail is okay, it goes via smtp to a second mta
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
338
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
339 %what amavis recognizes:
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
340 %- invalid headers
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
341 %- banned files
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
342 %- viruses
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
343 %- spam (using spam assassin)
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
344 %
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
345 %mimedefang: uses milter interface with sendmail
c51f1be54224 wrote about spam prevention and malware checking
meillo@marmaro.de
parents: 172
diff changeset
346
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
347
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
348
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
349 \subsubsection*{Archiving}
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
350
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
351
165
a7fd6d974d3c added lots of notes about spam, malware, auth, ...
meillo@marmaro.de
parents: 163
diff changeset
352 \texttt{always\_bcc} feature of postfix
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
353
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
354
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
355
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
356 \section{A new architecture}
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
357
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
358
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
359 (ssl)
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
360 -> msg-in (local or remote protocol handlers)
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
361 -> spam-filter (and more)
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
362 -> queue
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
363 -> msg-out (local-delivery by MDA, or remote-protocol-handlers)
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
364 (ssl)
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
365
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
366
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
367
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
368
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
369
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
370 http://fanf.livejournal.com/50917.html %how not to design an mta - the sendmail command
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
371 http://fanf.livejournal.com/51349.html %how not to design an mta - partitioning for security
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
372 http://fanf.livejournal.com/61132.html %how not to design an mta - local delivery
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
373 http://fanf.livejournal.com/64941.html %how not to design an mta - spool file format
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
374 http://fanf.livejournal.com/65203.html %how not to design an mta - spool file logistics
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
375 http://fanf.livejournal.com/65911.html %how not to design an mta - more about log-structured MTA queues
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
376 http://fanf.livejournal.com/67297.html %how not to design an mta - more log-structured MTA queues
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
377 http://fanf.livejournal.com/70432.html %how not to design an mta - address verification
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
378 http://fanf.livejournal.com/72258.html %how not to design an mta - content scanning
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
379
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
380
149
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
381
93
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
382
132
a83a29e10b10 new books
meillo@marmaro.de
parents: 129
diff changeset
383
93
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
384
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
385
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
386
109
de590ff06051 changes suggested by schaeffter
meillo@marmaro.de
parents: 99
diff changeset
387
149
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
388
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
389
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
390
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
391
149
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
392
ccf0de1ae337 new content and rework
meillo@marmaro.de
parents: 146
diff changeset
393
93
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
394
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
395
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
396
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
397
99
d24fdd3d5990 added lots of comments and annotations about what to do
meillo@marmaro.de
parents: 93
diff changeset
398
161
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
399 \section{Directions to go}
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
400
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
401 This section discusses about what shapes \masqmail\ could have---which directions the development could go to.
18b7b517e2dd wrote about discussion on architecture
meillo@marmaro.de
parents: 155
diff changeset
402
93
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
403
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
404
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
405
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
406
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
407 \subsubsection*{\masqmail\ in five years}
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
408
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
409 Now how could \masqmail\ be like in, say, five years?
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
410
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
411 ---
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
412
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
413 A design from scratch?
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
414 << what would be needed (effort) >>
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
415 But how is the effort of this complete rewrite compared to what is gained afterwards?
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
416
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
417 << would one create it at all? >>
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
418
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
419 ---
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
420
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
421 << plans to get masqmail more popular again (if that is the goal) >>
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
422
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
423 << More users >>
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
424
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
425
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
426
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
427
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
428
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
429
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
430
93
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
431 \section{Work to do}
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
432
146
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
433 << short term goals --- long term goals >>
2c4673d983c3 wrote about requirements (related to directions to go)
meillo@marmaro.de
parents: 142
diff changeset
434
163
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
435 do it like sendmail: first do the most needed stuff on the old design to make it still usable. Then design a new version from scratch, for the future.
5681a18270b5 new content about architecture; some restructuring
meillo@marmaro.de
parents: 161
diff changeset
436
140
002fd18820cc small changes
meillo@marmaro.de
parents: 137
diff changeset
437 << which parts to take out and do within the thesis >>
93
a6f8a93abd64 new chapter 4 (split ch5); added lots of annotations
meillo@marmaro.de
parents:
diff changeset
438
167
74151e26ba6a this is the correct message for the last commit
meillo@marmaro.de
parents: 166
diff changeset
439