Mercurial > docs > diploma

comparison thesis/tex/5-Improvements.tex @ 285:391793afb4cb

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
itemize -> enumerate at some places
author meillo@marmaro.de
date Thu, 15 Jan 2009 22:45:51 +0100
parents bc887e4e3a3e
children 6cf649e62d42
comparison
equal deleted inserted replaced
284:591217f50f69 285:391793afb4cb
130 130
131 131
132 132
133 133
134 134
135 \section{The new design} 135 \section{A new design}
136 136
137 The last chapter identified the requirements for a modern and securt \masqmail. Now the various jobs of an \MTA\ get assigned to modules, of which the new architecture is created. It is inspired by existing \MTA{}s and driven by the identified requirements. 137 The last chapter identified the requirements for a modern and securt \masqmail. Now the various jobs of an \MTA\ get assigned to modules, of which the new architecture is created. It is inspired by existing \MTA{}s and driven by the identified requirements.
138 138
139 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}. 139 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}.
140 140
204 204
205 205
206 \subsubsection*{Aliasing} 206 \subsubsection*{Aliasing}
207 207
208 Where should aliases get expanded? They appear in different kind. Important are the ones available in the \path{aliases} file. Aliases can be: 208 Where should aliases get expanded? They appear in different kind. Important are the ones available in the \path{aliases} file. Aliases can be:
209 \begin{itemize} 209 \begin{enumerate}
210 \item a different local user (e.g.\ ``\texttt{bob: alice}'') 210 \item a different local user (e.g.\ ``\texttt{bob: alice}'')
211 \item a remote user (e.g.\ ``\texttt{bob: john@example.com}'') 211 \item a remote user (e.g.\ ``\texttt{bob: john@example.com}'')
212 \item a list of users (e.g.\ ``\texttt{bob: alice, john@example.com}'') 212 \item a list of users (e.g.\ ``\texttt{bob: alice, john@example.com}'')
213 \item a command (e.g.\ ``\texttt{bob: |foo}'') 213 \item a command (e.g.\ ``\texttt{bob: |foo}'')
214 \end{itemize} 214 \end{enumerate}
215 Addresses expanding to lists of users lead to more envelopes. Aliases changing the reciptients domain part may require a different route to use. 215 Addresses expanding to lists of users lead to more envelopes. Aliases changing the reciptients domain part may require a different route to use.
216 216
217 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. 217 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.
218 218
219 219