annotate thesis/tex/5-Improvements.tex @ 329:c4d78cd40827

new ipc state diagram pic
author meillo@marmaro.de
date Fri, 23 Jan 2009 21:55:37 +0100
parents 2b1da14922f7
children 0e8c19c4b6ba
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
1 \chapter{Improvement plans}
89
3b5ba7331eb5 complete restructuring of whole document
meillo@marmaro.de
parents:
diff changeset
2
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
3 The last chapter came to the result that further development is best done in a double-strategy. First the existing code base should be improved to satisfy the most important needs in order to make it usable for some more time. Then \masqmail\ should get redesigned from scratch and rebuild to gain a secure and modern \MTA\ architecture for the future.
125
aa1fb227e68e unemphasised some terms
meillo@marmaro.de
parents: 109
diff changeset
4
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
5 This chapter finally gives concrete suggestions \emph{how} to realize these plans.
249
32e14e98cd91 small changes
meillo@marmaro.de
parents: 248
diff changeset
6
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
7 The first part covers the short-time goals which base on current code. The second part deals with the long-time goal---the redesign.
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
8
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
9
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
10
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
11
287
6cf649e62d42 minor renames and commenting
meillo@marmaro.de
parents: 285
diff changeset
12 \section{Based on current code}
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
13
249
32e14e98cd91 small changes
meillo@marmaro.de
parents: 248
diff changeset
14 The first three \TODO{}s are implementable by improving the current code or by adding wrappers or interposition filters. The following sections describe solution approaches to do that work.
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
15
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
16
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
17
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
18 \subsection{Encryption}
129
5a122d28f1ca moved some comment lines
meillo@marmaro.de
parents: 125
diff changeset
19
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
20 Encryption should be the first funtionality to add to the current code. This requirement was already discussed on page \pageref{requirement-encryption}. As explained there, \NAME{STARTTLS} encryption---as defined in \RFC\,2487---should be added to \masqmail.
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
21
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
22 Adding encryption requires changes mainly in three source files: \path{smtp_in.c}, \path{smtp_out.c}, and in \path{conf.c}.
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
23
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
24 The first file includes the functionality for the \SMTP\ server. It needs to offer \NAME{STARTTLS} support to clients and needs to initiate the encryption when the client requests it. Additionally, the server should be able to insist on encryption before it accepts any message.
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
25
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
26 The second file includes the functionality for the \SMTP\ client. It should start the encryption by issuing the \NAME{STARTTLS} keyword if the server supports it. It should be possible to send messages only if encryption is possible.
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
27
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
28 The third file controls the configuration files. New configuration option need to be added. The encryption policy for incoming connections needs to be defined. Three choises seem necessary: no encryption, offer encryption, insist on encryption. The encryption policy for outgoing connections should be part of each route setup. The options are the same: never encrypt, encrypt if possible, insist on encryption.
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
29
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
30 \NAME{STARTTLS} uses \NAME{TLS} encryption which is based on certificates. Thus the \MTA\ needs its own certificate. This should be generated during installation. A third party application like \name{openssl} should be taken for this job. The encryption itself should also be done using an available library. Open\NAME{SSL} or a substitute like Gnu\NAME{TLS} does then become a dependency for \masqmail. Gnu\NAME{TLS} seems to be the better choice because the Open\NAME{SSL} license is incompatible to the \NAME{GPL}, under which \masqmail\ and Gnu\NAME{TLS} are covered.
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
31
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
32 User definable paths to \masqmail's secret key, \masqmail's certificate, and the public certificates of trusted \name{Certificate Authorities} (short: \NAME{CA}s) are also nice to have.
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
33
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
34
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
35 << TLS patch of qmail >>
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
36
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
37 %postfix: main.cf
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
38 %
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
39 % smtpd_use_tls = yes
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
40 % smtpd_tls_received_header = no (does not log in received headers)
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
41 %
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
42 % smtpd_tls_key_file = /etc/postfix/key.pem
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
43 % smtpd_tls_cert_file = /etc/postfix/cert.pem
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
44 % smtpd_tls_CA_file = /etc/postfix/CAcert.pem
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
45 %
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
46 % smtp_use_tls = yes (use TLS for sending)
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
47 % smtp_tls_key_file = /etc/postfix/key.pem
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
48 % smtp_tls_cert_file = /etc/postfix/cert.pem
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
49 % smtp_tls_CA_file = /etc/postfix/CAcert.pem
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
50
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
51
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
52
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
53
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
54 \subsection{Authentication}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
55
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
56 Authentication is the second function to add; it is important to restrict the access to \masqmail, especially for mail relay. The requirements for authentication where identified on page \pageref{requirement-authentication}.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
57
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
58 Static access restriction, based on the \NAME{IP} address is already possible by using \name{TCP Wrappers}. This makes it easy to refuse all connections from outside the local net for example, which is a good prevention of being an open relay. More detailed static restrictions, like splitting between mail for the system and mail to relay, should not be added to the current code. This may be a concern for the new design.
277
8a25b6262497 minor changes; added todos
meillo@marmaro.de
parents: 273
diff changeset
59
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
60 Of the dynamic, secret based, authentication methods (\SMTP-after-\NAME{POP}, \SMTP\ authentication, and certificates) the first one drops out as it requires a \NAME{POP} server running on the same or a trusted host. \NAME{POP} servers are rare on workstations and home servers do also not regularly include them. Thus it is no option for \masqmail.
277
8a25b6262497 minor changes; added todos
meillo@marmaro.de
parents: 273
diff changeset
61
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
62 Authentication based on certificates does suffer from the certificate infrastructure that is required. Although certificates are already used for encryption, its management overhead prevented wide spread usage for authentication.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
63
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
64 \SMTP\ authentication (also refered to as \NAME{SMTP-AUTH}) support is easiest received by using a \name{Simple Authentication and Security Layer} (short: \NAME{SASL}) implementation. \person{Dent} sees in \NAME{SASL} the best solution for dynamic authentication of users:
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
65 \begin{quote}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
66 %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.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
67 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.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
68 \hfill\cite[page 44]{dent04}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
69 \end{quote}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
70
324
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
71 These days is \NAME{SMTP-AUTH}, which is defined in \RFC\,2554, supported by most email clients. If encryption is used then even insecure authentication methods like \NAME{PLAIN} and \NAME{LOGIN} become secure.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
72
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
73 \masqmail\ best uses an available \NAME{SASL} library. \name{Cyrus} \NAME{SASL} is used by \postfix\ and \sendmail. It is a complete framework that makes use of existing authentication concepts like \path{/etc/passwd} or \NAME{PAM}. As advantage it can be included in existing user data bases. \name{gsasl} is an alternative. It comes as a library which helps on deciding for a method and on generating the appropriate dialog data; the actual transmission of the data and the authentication against some database is left open to the programmer. \name{gsasl} is used by \name{msmtp} for example. It seems best to give both concepts a try and decide then which one to use.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
74
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
75 Currently, outgoing connections already feature \SMTP-\NAME{AUTH} but only in a hand-coded way. It is to decide wether it remains as it is or gets replaced by the \NAME{SASL} approach, that is used for incoming connections. The decision should be based on the estimated time until the new design is usable.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
76
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
77 Authentication needs code changes at the same places as encryption. The relevant code files are \path{smtp_in.c}, \path{smtp_out.c}, and \path{conf.c}.
277
8a25b6262497 minor changes; added todos
meillo@marmaro.de
parents: 273
diff changeset
78
324
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
79 The server code, to authenticate clients, must be added to \path{smtp_in.c} and the configuration options to \path{conf.c}. Several configuration options should be provided: the authentication policy (no authentication, offer authentication, insist on authentication), the authentication backend (if several are supported), an option to refuse plain text methods (\NAME{PLAIN} and \NAME{LOGIN}), and one to require encryption before authentication.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
80
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
81 If the authentication code for outgoing connects shall be changed too, it must be done in \path{smtp_out.c}. The configuration options are already present.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
82
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
83
324
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
84 About the authentication backend. For a small \MTA\ like \masqmail, it seems preferrable to store the login data in a text file under \masqmail's control. This is the most simple choice for many usage scenarios. But using a central authentication facility has advantages in larger setups too. \name{Cyrus} \NAME{SASL} supports both, so there is no problem. If \name{gsasl} is chosen, it seems best to start with an authentication file under \masqmail's control.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
85
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
86
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
87
317
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
88
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
89
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
90 << Compare static with dynamic authentication: pros and cons; usecases: when to use what; >>
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
91
3b7680af0ebe work in enc and auth
meillo@marmaro.de
parents: 301
diff changeset
92 << how could this be covered by architecture (e.g. smtp submission). >>
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
93
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
94
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
95
324
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
96
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
97
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
98 \subsection{Security}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
99
324
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
100 Improvements to \masqmail's security are an important requirement and are the third task to work on. Retrofitting security \emph{into} \masqmail\ is not or hardly possible as it was explained in section \ref{sec:discussion-further-devel}. But adding wrappers and interposition filters can be a large step towards security.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
101
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
102 At first mail security layers like \name{smap} come to mind. The market share analysis in section \ref{sec:market-share} identified such software. This is an interposition filter that stands between the untrusted network and the \MTA. It accepts mail in replacement for the \MTA\ (also called \name{proxy}) in order to separate the \MTA\ from the untrusted network.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
103
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
104 The work \name{smap} does is described in \cite{cabral01}: \name{smap} accepts messages as proxy for the \MTA\ and puts it into a queue. \name{smapd} a brother program runs as daemon and watches for new messages in the queue which it submits into the \MTA\ then.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
105
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
106 Because the \MTA\ does not listen for connections from extern now, it is not directly attackable. But the \MTA\ can not react on relaying and spam on itself anymore because it has no direct connection to the mail sender. This job needs to be covered by the proxy now. Similar is the situation for encryption and authentication. However, care must be taken that the proxy stays small and simple as its own security will suffer otherwise.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
107
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
108 The advantage is that the \MTA\ itself needs not to bother much with untrusted environments. And a small proxy cares only about that work.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
109
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
110 \name{smap} is non-free software and thus no general choice for \masqmail. A way to achieve a similar setup would be to copy \masqmail\ and strip one copy to the bare minimum what is needed for the proxy job. \name{setuid} could be removed and root privilege too if \name{inetd} is used. This hardens the proxy instance.
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
111
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
112 Mail from extern would then come through the proxy into the system. Mail from the local host and from the local network could be directly accepted by the normal \masqmail, if those locations are considered trusted. But it seems better to have them use the proxy too, or maybe a second proxy instance with different policy.
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
113
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
114 The here described setup comes close to the structure of the incoming channels in the new design which is described in \ref{sec:new-design}. This shows the possibilities of the here chosen approach. %fixme: rethink this sentence
324
8671d9c0f29a wrote more about auth and about security
meillo@marmaro.de
parents: 318
diff changeset
115
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
116
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
117 \subsubsection*{A concrete setup}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
118
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
119 A stripped down proxy needs to be created. It should only be able to receive mail via \SMTP, encrypt the communication, authenticate clients, and send mail out via \SMTP\ to an internal socket (named ``X'' in the figure). This is a straight forward task. The normal \masqmail\ instance runs on the system too. It takes input from \name{stdin} (by calling the \path{sendmail} command) and via \SMTP\ where it listens on an internal socket (named ``X'' in the figure). Outgoing mail is handled without difference to a regular setup. Figure \ref{fig:proxy-setup} depicts the setup.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
120
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
121 \begin{figure}
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
122 \begin{center}
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
123 \includegraphics[scale=0.75]{img/proxy-setup.eps}
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
124 \end{center}
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
125 \caption{A setup with a proxy}
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
126 \label{fig:proxy-setup}
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
127 \end{figure}
288
8341092a7554 rework throughout ch04; minor other stuff
meillo@marmaro.de
parents: 287
diff changeset
128
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
129
298
0d88bf21e152 minor changes
meillo@marmaro.de
parents: 288
diff changeset
130 \subsubsection*{Spam and malware handling}
277
8a25b6262497 minor changes; added todos
meillo@marmaro.de
parents: 273
diff changeset
131
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
132 The presented setup is the same as the one with two \MTA\ instances and a scanner application in between, which was suggested to add spam and malware scanner afterwards to an \MTA. This is a fortunate conincidence, because a scanner like \name{amavis} can simply be put in replace for the internal socket ``X''.
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
133
277
8a25b6262497 minor changes; added todos
meillo@marmaro.de
parents: 273
diff changeset
134
8a25b6262497 minor changes; added todos
meillo@marmaro.de
parents: 273
diff changeset
135
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
136
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
137 \subsubsection*{Conditional compilation}
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
138 << conditional compilation >>
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
139
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
140
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
141
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
142
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
143
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
144
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
145
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
146
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
147
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
148
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
149
184
b0adae481138 moved content
meillo@marmaro.de
parents: 176
diff changeset
150
89
3b5ba7331eb5 complete restructuring of whole document
meillo@marmaro.de
parents:
diff changeset
151
3b5ba7331eb5 complete restructuring of whole document
meillo@marmaro.de
parents:
diff changeset
152
194
e038b2572d12 minor restructuring
meillo@marmaro.de
parents: 184
diff changeset
153
e038b2572d12 minor restructuring
meillo@marmaro.de
parents: 184
diff changeset
154
e038b2572d12 minor restructuring
meillo@marmaro.de
parents: 184
diff changeset
155
285
391793afb4cb itemize -> enumerate at some places
meillo@marmaro.de
parents: 282
diff changeset
156 \section{A new design}
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
157 \label{sec:new-design}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
158
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
159 The last chapter identified the requirements for a modern and secure \masqmail. Now the various jobs of an \MTA\ get assigned to modules of which a new architecture is created. It is inspired by existing \MTA{}s and driven by the identified requirements.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
160
249
32e14e98cd91 small changes
meillo@marmaro.de
parents: 248
diff changeset
161 One wise experience was kept in mind during the design: ``Many times in life, getting off to the right start makes all the difference.'' \cite[page~32]{graff03}.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
162
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
163
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
164
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
165 \subsection{Design decisions}
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
166
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
167 Major design ideas of the design were:
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
168 \begin{enumerate}
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
169 \item compartmentalization throughout
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
170 \item free the internal system from the in and out channels
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
171 \item provide interfaces to add arbitrary protocol handlers afterwards
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
172 \item have a single point where all mail goes through for scanning
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
173 \item concentrate on the mail transfer job; use specialized external programs for other jobs
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
174 \item keep it simple, clear, and general
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
175 \end{enumerate}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
176
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
177
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
178
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
179 \subsubsection*{Incoming channels}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
180
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
181 \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 therefore 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 \cite{hafiz05}. %fixme: specify page
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
182
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
183 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 back door?
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
184 \person{Finch} 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 which puts 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.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
185
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
186 But merging the input channels in the \SMTP\ daemon makes the \MTA\ heavily dependent on \SMTP. 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 the \SMTP\ modules can be removed if it is not needed. And it is better to have more independent modules if each one is simpler then---it makes the modules more complicated if each one needs to implement an \SMTP\ client.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
187
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
188 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. Independent checks in different modules, however, have also the advantage to simply apply different policies. Thus it is possible to run two \SMTP\ modules that listen on different ports; one accessable from the Internet but requires authentication, the other only accessable from the local network but does not require authentication.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
189
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
190 The approach of simple independent modules, one for each incoming channel, should be taken.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
191
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
192 A module which is a \NAME{POP} or \NAME{IMAP} client to import contents of other mail boxes into the system may be added afterwards as it is desired.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
193
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
194
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
195
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
196 \subsubsection*{Outgoing channels}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
197
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
198 Outgoing mail is commonly either sent using \SMTP, piped into local commands (for example \path{uucp}), or delivered locally by appending to a mailbox.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
199
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
200 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 privilege 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\footnote{root privilege is actually not a mandatory requirement, but any other approach has some disadvantages, so commonly root privilege is used.}.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
201
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
202 Local mail delivery should not be done by the \MTA, but by an \NAME{MDA}. This decision was discussed in section \ref{sec:functional-requirements}. This means only an outgoing channel that pipes mail into a local command is required for local delivery.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
203
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
204 Other outgoing channels, one for each supportet protocol, may be designed like it was done in other \MTA{}s.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
205
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
206
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
207
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
208 \subsubsection*{The mail queue}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
209
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
210 The mail queue is the central part of an \MTA. This demands especially for robustness and reliability as a failure here can lead to loosing mail.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
211
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
212 %\sendmail, \exim, \qmail, \name{sendmail X}, and \masqmail\ feature one single mail queue. \postfix\ has more of them.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
213 Common \MTA{}s feature one or more mail queues, they sometimes have effectly several queues within one physical representation.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
214
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
215 \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. \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}.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
216
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
217 \sendmail, \exim, \qmail, and \masqmail\ all use at least two files to store one message in the queue: one file contains the message body, another the envelope and header information. The one containing the mail body is not modified at all. \postfix\ takes a different approach in storing queued messages in an internal format within one file. \person{Finch} suggest yet another approach: storing the whole queue in one single file with pointers to separating positions \cite{finchFIXME}. %fixme: check, cite, and think about
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
218
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
219 All of the presented \MTA{}s use the file system to hold the queue; none uses a database to hold it. A database could improve the reliability of the queue through better persistence. This might be a choice for larger \MTA{}s but is none for \masqmail\ which should be kept small and simple. A running database system does likely require much more resources than \masqmail\ itself does. And as the queue's job is more storing data than running data selection queries, a database does not gain so much that it outweighs its costs.
298
0d88bf21e152 minor changes
meillo@marmaro.de
parents: 288
diff changeset
220
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
221 Hence here the choice is having a directory with simple text files in it. This is straight forward, simple, clear, and general \dots\ and thus a good basis for reliability. It is additionally always of advantage if data is stored in the operation system's natural form, which in the case of \unix\ is plain text.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
222
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
223 Robustness for the queue is covered in the next section. %fixme: ist this sentence neccessary? Is it still correct.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
224
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
225
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
226
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
227 \subsubsection*{Mail sanitizing}
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
228
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
229 Mail coming into the system may be may be malformed, lacking headers, or be an attempt to exploit the system. Care must be taken.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
230
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
231 In \postfix, this is done by the \name{cleanup} module, which invokes \name{rewrite}. The position in the message flow is after the message comes from one of the several incoming channels and before the message is stored into the \name{incoming} queue. \name{cleanup} does a complete check to make the mail header complete and valid.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
232
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
233 \qmail\ has the principle of ``don't parse'' which propagades the avoidance of parsing as possible in the system. The reason is that parsing is a highly complex task which often makes code exploitable.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
234
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
235 Mail should be stored into the queue as it is in \masqmail's new design. A scanning module should then parse the message with high care. It seems best to use a \name{parser generator} for this work. The parsed data should then be modified if needed and written into a second queue. This approach has several advantages. First, the receiving parts of the system do not bother about content, they simply store it into the queue. Second, one single modules does the parsing and generates new messages that contain only valid data. Third, the sending parts of the system will only work on messages that consist of valid data. Of course it must be ensured that each message passes through the \name{scanning} module, but this is required for spam and malware scanning too.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
236
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
237 The mail body will never get modified, except of removing and adding transfer protocol specific requirements like dot stuffing or special line ending characters.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
238
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
239 \person{Jon Postel}'s robustness principle ``Be liberal in what you accept, and conservative in what you send.'', which can be found in this wording in \RFC\,1122 and in different wordings in numerous \RFC{}s, is respected in the \name{scanning} module. It parses the given input in some liberal way and generates clean output. \person{Raymond}'s \name{Rule of Repair} ``Repair what you can -- but when you must fail, fail noisily and as soon as possible.'' can be applied too. But it is important to repair only obvious problems, because repairing functionality is likely a target of attacks.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
240
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
241
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
242
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
243
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
244 \subsubsection*{Aliasing}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
245
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
246 The main question about aliasing is: Where should aliases get expanded?
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
247
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
248 Two facts are important to consider: Addresses expanding to lists of users lead to more envelopes. And aliases changing the reciptient's domain part may make the message unsuitable for a specific online route.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
249
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
250 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. But already accepted messages may get rejected in the second go, because of an replacement address from within the system. This seems not to be wanted.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
251
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
252 Doing the alias expansion in the scanning module appears to be the best solution. Unfortunately a second alias expansion must be made on delivery, because only at that point in time is clear which route is used for the message. This compromise is accepted.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
253
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
254
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
255
287
6cf649e62d42 minor renames and commenting
meillo@marmaro.de
parents: 285
diff changeset
256 \subsubsection*{Route management}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
257
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
258 The online state is only important for the sending modules of the system, thus it should be queried in the \name{queue-out} module which selects ready messages from the \name{outgoing} queue and transfers them to the appropriate sending module. Route-based aliasing, which was described in the last section, %fixme: is this still true?
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
259 should to be done in the same go.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
260
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
261
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
262
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
263
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
264 \subsubsection*{Authentication and Encryption}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
265
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
266 Both topics were discussed several time throughout this thesis, amoung other places on page \pageref{} and \pageref{}.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
267
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
268 Authentication should be done within the receiving modules. Similar should authentication for outgoing connections be handled by the sending modules.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
269
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
270 To encryption applies the same as to authentication here. Only receiving and sending modules should come in contact with it.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
271
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
272 In order to avoid code duplicates, the actual implementation of both functionalities should be provided by a central source which gets invoked by the various modules.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
273
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
274
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
275
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
276
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
277
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
278
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
279 \subsubsection*{Spam and malware handling}
194
e038b2572d12 minor restructuring
meillo@marmaro.de
parents: 184
diff changeset
280
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
281 The two approaches for spam handling were already presented to the reader in section \ref{}. Here they are described in more detail:
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
282
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
283 \begin{enumerate}
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
284 \item 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 taken and no further system load is added. See \RFC2505 (especially section 1.5) for detail.
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
285
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
286 \item 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.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
287 \end{enumerate}
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
288
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
289 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\"ahrend der \SMTP-Phase kommt sowieso kein \MTA\ aus, und es ist eine Frage der Einsch\"atzung, wie weit man diese Phase belasten m\"ochte.'' \cite[page 25]{eisentraut05} (translated: ``No \MTA\ can go without analysis during the \SMTP\ phase anyway, but the amount of stress one likes to put on this phase is left to his discretion.'')
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
290
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
291 Checking before a message is accepted, like \NAME{DNS} blacklists and \name{greylisting}, needs to be invoked from within the receiving modules. Like for authentication and encryption, the implementation of the functionality should be provided by a central source.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
292
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
293 All checking after the message was queued should be done by pushing the message through external scanners like \name{spamassassin}. The \name{scanning} module is the best place to handle this. Hence this module needs interfaces to external scanners.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
294
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
295
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
296 Malware scanning is similar like the second type of spam scanning. The \name{amavis} framework is a popular mail scanning framework that includes all kinds of malware and also spam scanners; it communicates by using \SMTP.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
297
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
298 Providing \SMTP\ in and out channels from the \name{scanning} module to external scanner applications seems to be a desired goal. Using further instances of the already available \name{smtp} and \name{smtpd} modules therefore appears to be the best solution.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
299
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
300
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
301
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
302
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
303
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
304
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
305 \subsubsection*{Archiving}
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
306
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
307 The best point to archive copies of every incoming mail is the \name{queue-in} module, respectively the \name{queue-out} module for copies outgoing mail. But not respected with this approach are the changes that are made by the receiving modules (adding further headers) and sending modules (address rewrites).
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
308
328
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
309 \qmail\ has the ability to log complete \SMTP\ dialogs. Logging the complete data transaction into and out of the system into a separate log file is a great feature which should be implemented into each receiving and sending module. But as it will produce a huge amount of output, it should be cared to disabled it by default.
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
310
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
311
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
312
2b1da14922f7 reworked section about design decisions and here and there further bits
meillo@marmaro.de
parents: 326
diff changeset
313
326
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
314
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
315
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
316
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
317
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
318
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
319
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
320
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
321
802635628c92 various work in ch05
meillo@marmaro.de
parents: 324
diff changeset
322
194
e038b2572d12 minor restructuring
meillo@marmaro.de
parents: 184
diff changeset
323
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
324 \subsection{The resulting architecture}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
325
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
326 The result is a symetric design, featuring the following parts: Any number of handlers for incoming connections to receive mail and pass it to the module that stores it into the incoming queue. A central scanning module take mail from the incoming queue, processes it in various ways and puts it afterwards into the outgoing queue. Another module takes it out there and passes it to a matching transport module that transfers it to the destination. In other words, three main modules (queue-in, scanning, queue-out) are connected by the two queues (incoming, outgoing); on each end are more modules to receive and send mail---for each protocol one. Figure \ref{fig:masqmail-arch-new} depicts the new designed architecture.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
327
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
328 \begin{figure}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
329 \begin{center}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
330 \includegraphics[width=\textwidth]{img/masqmail-arch-new.eps}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
331 \end{center}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
332 \caption{A new designed architecture for \masqmail}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
333 \label{fig:masqmail-arch-new}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
334 \end{figure}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
335
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
336 This architecture is heavily influenced by the ones of \qmail\ and \postfix. Both have different incoming channels that merge in the module that puts mail into the queue; central is the queue (or more of them); and one module takes mail from the queue and passes it to one of the outgoing channels. Mail processing, in any way, is build in in a more explicit way than done in the other two. It is more similar to the \NAME{AR} module of \name{sendmail X}, which is the central point for spam checking.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
337
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
338 Special regard was put on addable support for further mail transfer protocols. This appears to be most similar to \qmail, which was designed to handle multiple protocols.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
339 %fixme: do i need all this ``quesses''??
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
340
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
341
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
342 \subsubsection*{Modules and queues}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
343
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
344 The new architecture consists of several modules and two queues. They are defined in more detail now, and the jobs, identified above, are assigned to them. First the three main modules, then the queues, and afterwards the modules for incoming and outgoing transfer.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
345
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
346
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
347 The \name{queue-in} module creates new spool files in the \name{incoming} queue for incoming messages. It is a process running in background, waiting for connections from one of the receiver modules. When one of them requests for a new spool file, the \name{queue-in} module opens one and returns a positive result. The receiver module then sends the envelope and message, which is written into the spool file by \name{queue-in}. If all went well, another positive result is returend.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
348 %fixme: should be no daemon
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
349
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
350
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
351 The \name{scanning} module is the central part of the system. It takes spooled messages from the \name{incoming} queue, works on them, and writes them to the \name{outgoing} queue afterwards (the message is then removed from the \name{incoming} queue, of course). The main job is the processing done on the message. Headers are fixed and missing ones are added if necessary, aliasing is done, and external processing of any kind is triggered. The \name{scanning} module can run in background and look for new mail in regular intvals or signals may be sent to it by \name{queue-in}. Alternatively it can be called by \name{cron}, for example, to do single runs.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
352
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
353
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
354 The \name{queue-out} module takes messages from the \name{outgoing} queue, queries information about the online connection, and then selects matching routes, creates envelopes for each recipient and passes the messages to the correct transport module. Successfully transfered messages are removed from the \name{outgoing} queue. This module includes some tasks specific to \masqmail.
287
6cf649e62d42 minor renames and commenting
meillo@marmaro.de
parents: 285
diff changeset
355 %fixme: rework route selection
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
356
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
357
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
358 The \name{incoming} queue stores messages received via one of the incoming channels. The messages are in unprocessed form; only envelope data is prepended.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
359
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
360
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
361 The \name{outgoing} queue contains processed messages. The header and envelope information is complete and in valid form.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
362
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
363 \name{Receiver modules} are the communication interface between outside senders and the \name{queue-in} module. Each protocol needs a corresponding \name{receiver module} to be supported. Most popular are the \name{sendmail} module (which is a command to be called from the local host) and the \name{smtpd} module (which listens on port 25). Other modules to support other protocols may be added as needed.
318
426ad56236ce small fixes and todo -> fixme
meillo@marmaro.de
parents: 317
diff changeset
364 %fixme: get invoked by inetd, or better ucspi-tcp (by bernstein) which can limit max number of concurrent connections. and includes tcp-wrappers functionality.
282
bc887e4e3a3e minor changes
meillo@marmaro.de
parents: 277
diff changeset
365
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
366
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
367 \name{Transport modules}, on the oppersite side of the system, are the modules to send outgoing mail; they are the interface between \name{queue-out} and remote hosts or local commands for further processing. The most popular ones are the \name{smtp} module (which acts as the \SMTP\ client) and the \name{pipe} module (to interface gateways to other systems or networks, like fax or uucp). A module for local delivery is not included, as it is in most other \MTA{}s; the reasons are described in FIXME.%fixme
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
368 Thus a \name{mail delivery agent} (like \name{procmail}) is to be used with the \name{pipe} module.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
369
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
370
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
371
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
372 \subsubsection*{Inter-module communication}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
373
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
374 Communication between modules is required to exchange data and status information. It is also called ``Inter-process communication'' (short: \NAME{IPC}), as modules are programs being part of a larger system, and processes are generally seen as programs in execution.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
375
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
376 The connections between \name{queue-in} and \name{scanning}, aswell as between \name{scanning} and \name{queue-out} is provided by the queues, only sending signals to trigger instant runs may be useful. Communication between receiving and transport modules and the outside world are done using the specific protocol they do handle.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
377
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
378 Left is only communication between the receiver modules and \name{queue-in}, and between \name{queue-out} and the transport modules. Data is exchanged done using \unix\ pipes and a simple protocol is used.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
379
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
380 \begin{figure}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
381 \begin{center}
273
92578f124df6 reorganized the input files and sorted old ones out
meillo@marmaro.de
parents: 271
diff changeset
382 \codeinput{input/ipc-protocol.txt}
92578f124df6 reorganized the input files and sorted old ones out
meillo@marmaro.de
parents: 271
diff changeset
383 %\includegraphics[scale=0.75]{img/ipc-protocol.eps}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
384 \end{center}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
385 \caption{State diagram of the protocol used for \NAME{IPC}}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
386 \label{fig:ipc-protocol}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
387 \end{figure}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
388
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
389 % timing
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
390 One dialog consists of the four phases: connection attempt, acceptance reply, data transfer, success reply. The order is always the same. The connection attempt and data transfer are sent by the client process; replies are sent by the server process.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
391 %fixme: split between header and data
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
392
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
393 % semantics
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
394 The connection attempt is simply opening the connection. This starts the dialog. A positive reply by the server leads to the data transfer, but a negative reply refuses the connection and resets both client and server to the state before the connection attempt. If the connection attempt was accepted, the client sends the data ending with a terminator sequence. When this terminator appears, the server process knows the complete data was transfered. The server process takes responsibility of the data in sending a positive success reply. A negative success reply resets both client and server to the state before the connection attempt.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
395
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
396 The data transfered needs to be of specific format. Used is the same format in which messages are spooled in the mail queues. See the following section for details. %fixme: check if it is the following section
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
397 %fixme: split between header and data
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
398
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
399 % syntax
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
400 Data transfer is done sending plain text data. %fixme: utf8 ?
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
401 The terminator sequence used to indicate the end of the data transfer is a single dot on a line on its own. Line separators are the combination of \name{Carriage Return} and \name{Line Feed}, as it is used in various Internet protocols like \SMTP. Replys are one-digit numbers with \texttt{0} meaning success and any other number (\texttt{1}--\texttt{9}) indicate failure. %fixme: What are the octal values?
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
402 %fixme: split between header and data
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
403
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
404 Figure \ref{fig:ipc-protocol} is a state diagram for the protocol.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
405
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
406
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
407
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
408 \subsubsection*{Spool file format}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
409
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
410 The spool file format is basically the same as the one in current \masqmail: one file for the message body, the other for envelope and header information. The data file is stored in a separate data pool. It is written by \name{queue-in}, \name{scanning} can read it if necessary, \name{queue-out} reads it to generate the outgoing message, and deletes it after successful transfer. The header file (including the envelope) is written into the \name{incoming} queue. The \name{scanning} modules reads it, processes it, and writes a modified copy into the \name{outgoing} queue; the file in \name{incoming} is deleted then. \name{queue-out} finally takes the header file from \name{outgoing} to generate the resulting message. This data flow is shown in figure \ref{fig:queue-data-flow}.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
411
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
412 \begin{figure}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
413 \begin{center}
273
92578f124df6 reorganized the input files and sorted old ones out
meillo@marmaro.de
parents: 271
diff changeset
414 %\input{img/queue-data-flow.eps}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
415 \end{center}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
416 \caption{Data flow of messages in the queue}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
417 \label{fig:queue-data-flow}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
418 \end{figure}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
419
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
420 The queue consists of three directories within the queue path. Two, named \name{incoming} and \name{outgoing}, for storing the header files; one, called \name{pool}, to store the message bodies. The files being part of one message share the same unique name. The header files internal structure can be the same as the one of current \masqmail.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
421
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
422 Messages in queues are a header file in \name{incoming} or \name{outgoing} and a data file in \name{pool}. The header file owner's executable bit indicates if the file is ready for further processing: the module that writes the file into the queue sets the bit as last action. Modules that read from the queue can process messages with the bit set.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
423
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
424 No spool files are modified after they are written to disk. Modifications to header files can be made by the \name{scanning} module in the ``move'' from \name{incoming} to \name{outgoing}---it is a create and remove, actually. Further rewriting can happen in \name{queue-out}, as well without altering the file.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
425
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
426 Data files do not change at all within the system. They are written in default local plain text format. Required translation is done in the receiver and transport modules.
249
32e14e98cd91 small changes
meillo@marmaro.de
parents: 248
diff changeset
427 %fixme: why plain text and not db? -> simplicity
32e14e98cd91 small changes
meillo@marmaro.de
parents: 248
diff changeset
428
32e14e98cd91 small changes
meillo@marmaro.de
parents: 248
diff changeset
429 Mark spooled mail messages when processing of the writing module is finished: Either by setting the executable bit (like \postfix\ does), or by changing the owner (an approach for multiple masqmail users).
89
3b5ba7331eb5 complete restructuring of whole document
meillo@marmaro.de
parents:
diff changeset
430
3b5ba7331eb5 complete restructuring of whole document
meillo@marmaro.de
parents:
diff changeset
431
249
32e14e98cd91 small changes
meillo@marmaro.de
parents: 248
diff changeset
432 A sample header file. With comments in paranthesis.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
433
261
b390fb627f10 changed formating of verbatim blocks
meillo@marmaro.de
parents: 249
diff changeset
434 \begin{quote}\footnotesize
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
435 \begin{verbatim}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
436 1LGtYh-0ut-00 (backup copy of the file name)
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
437 MF:<meillo@dream> (envelope: sender)
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
438 RT: <user@example.org> (envelope: recipient)
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
439 PR:local (meta info: protocol)
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
440 ID:meillo (meta info: id/user/ip)
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
441 DS: 18 (meta info: size)
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
442 TR: 1230462707 (meta info: timestamp)
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
443 (following: headers)
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
444 HD:Received: from meillo by dream with local (masqmail 0.2.21) id
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
445 1LGtYh-0ut-00 for <user@example.org>; Sun, 28 Dec 2008 12:11:47 +0100
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
446 HD:To: user@example.org
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
447 HD:Subject: test mail
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
448 HD:From: <meillo@dream>
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
449 HD:Date: Sun, 28 Dec 2008 12:11:47 +0100
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
450 HD:Message-ID: <1LGtYh-0ut-00@dream>
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
451 \end{verbatim}
261
b390fb627f10 changed formating of verbatim blocks
meillo@marmaro.de
parents: 249
diff changeset
452 \end{quote}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
453
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
454
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
455
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
456
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
457 \subsubsection*{Rights and permission}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
458
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
459 The user set required for \qmail\ seems to be too complex. One special user, like \postfix\ uses, is more appropriate. \name{root} privilege and \name{setuid} permission is avoided as much as possible.
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
460
273
92578f124df6 reorganized the input files and sorted old ones out
meillo@marmaro.de
parents: 271
diff changeset
461 Table \ref{tab:new-masqmail-permissions} shows the suggested ownership and permissions of the modules.
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
462
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
463 \begin{table}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
464 \begin{center}
271
c80b6b6fb798 moved tables from input to tbl
meillo@marmaro.de
parents: 261
diff changeset
465 \input{tbl/new-masqmail-permissions.tbl}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
466 \end{center}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
467 \caption{Ownership and permissions of the modules}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
468 \label{tab:new-masqmail-permission}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
469 \end{table}
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
470
273
92578f124df6 reorganized the input files and sorted old ones out
meillo@marmaro.de
parents: 271
diff changeset
471 These are the permissions and ownership used for the queue:
92578f124df6 reorganized the input files and sorted old ones out
meillo@marmaro.de
parents: 271
diff changeset
472 \codeinput{input/new-masqmail-queue.txt}
246
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
473
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
474
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
475
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
476
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
477
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
478 setuid/setgid or not?
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
479
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
480 what can crash if an attacker succeeds?
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
481
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
482 where to drop privelege?
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
483
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
484 how is which process invoked?
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
485
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
486 master process? needed, or wanted?
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
487
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
488 which are the daemon processes?
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
489
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
490
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
491
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
492
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
493
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
494
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
495
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
496 http://fanf.livejournal.com/50917.html %how not to design an mta - the sendmail command
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
497 http://fanf.livejournal.com/51349.html %how not to design an mta - partitioning for security
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
498 http://fanf.livejournal.com/61132.html %how not to design an mta - local delivery
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
499 http://fanf.livejournal.com/64941.html %how not to design an mta - spool file format
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
500 http://fanf.livejournal.com/65203.html %how not to design an mta - spool file logistics
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
501 http://fanf.livejournal.com/65911.html %how not to design an mta - more about log-structured MTA queues
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
502 http://fanf.livejournal.com/67297.html %how not to design an mta - more log-structured MTA queues
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
503 http://fanf.livejournal.com/70432.html %how not to design an mta - address verification
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
504 http://fanf.livejournal.com/72258.html %how not to design an mta - content scanning
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
505
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
506
5cfea0d05e7f appended ch06 to ch05 + restructuring
meillo@marmaro.de
parents: 231
diff changeset
507