| rev |
line source |
|
meillo@274
|
1 \clearpage
|
|
meillo@8
|
2 \chapter*{Preface}
|
|
meillo@98
|
3 \addcontentsline{toc}{section}{Preface}
|
|
meillo@8
|
4
|
|
meillo@370
|
5 This thesis is about \masqmail, a small mail transfer agent for workstations and home networks. In October 2007 I had chosen \masqmail\ for my machines because of its small size though it was a ``real'' mail transfer agent. \masqmail\ served me well since then and I have found no reasons to change.
|
|
meillo@8
|
6
|
|
meillo@366
|
7 Unfortunately, the \masqmail\ package in \debian, which is my preferred \NAME{GNU}/Linux distribution, is unmaintained since the beginning of 2008. Unmaintained packages are likely to get dropped out of a distribution if critical bugs appear in them. Although \masqmail\ had no critical bugs, this was a situation I definitely wanted to prevent.
|
|
meillo@302
|
8
|
|
meillo@356
|
9 Using my diploma thesis as a ``power-start'' for maintaining and developing \masqmail\ in the future was a great idea. As it came to my mind I knew this is the thing I \emph{wanted} to do. --- I did it! :-)
|
|
meillo@302
|
10
|
|
meillo@366
|
11 \quad
|
|
meillo@366
|
12
|
|
meillo@370
|
13 The overall goal of this document is to revive \masqmail\ in usage and development. \masqmail\ was not developed further in the last five years although the world of email has changed during this time. Hence quite some work needed to be done.
|
|
meillo@366
|
14
|
|
meillo@370
|
15 I decided to start at the basis and analyze the environment and \masqmail\ throughout to end up in concrete plans of what should be done and how it should be done to turn \masqmail\ into a modern mail transfer agent again.
|
|
meillo@366
|
16
|
|
meillo@370
|
17 The actual implementation of the the proposed changes will follow-up this thesis. Here solutions are identified, described, discussed, and recommended but not implemented. I have been working in the code and have fixed bugs during the time I worked on the thesis, though.
|
|
meillo@101
|
18
|
|
meillo@356
|
19 \quad
|
|
meillo@101
|
20
|
|
meillo@370
|
21 This document is primary written with an audience of \masqmail\ developers and developers of other mail transfer agents in mind. But users of \masqmail\ and everyone who is interested in email systems in general may find this thesis an interesting literature too.
|
|
meillo@101
|
22
|
|
meillo@370
|
23 However, at least basic knowledge about \unix\ and C programming is a prerequisite for chapters three, four, and five. \person{Kernighan} and \person{Pike}'s ``The \NAME{UNIX} Programming Environment'' \cite{kernighan84} is a valuable source to gain information about \unix. Programming in the C language is best learned from \person{Kernighan} and \person{Ritchie}'s ``The C Programming Language'' \cite{k&r}.
|
|
meillo@352
|
24
|
|
meillo@352
|
25
|
|
meillo@352
|
26
|
|
meillo@352
|
27
|
|
meillo@352
|
28
|
|
meillo@33
|
29
|
|
meillo@33
|
30
|
|
meillo@8
|
31
|
|
meillo@316
|
32 \section*{Organization}
|
|
meillo@33
|
33
|
|
meillo@370
|
34 The document consists of six chapters, each covering a delimited part of the overall topic and building upon the content and results of previous chapters. The first three chapters lead into the topic and create a solid base where the second part builds upon. The chapters four and five form the central part of the thesis as they focus on \masqmail.
|
|
meillo@8
|
35
|
|
meillo@370
|
36 Chapter 1 \textbf{introduces} \masqmail\ to the reader. It presents the properties, goals, advantages, and problems of the program. Basic concepts of the email technology are also described and later assumed to be known.
|
|
meillo@352
|
37
|
|
meillo@370
|
38 Chapter 2 \textbf{analyzes the market} of electronic communication and email. This chapter gives sound reasons for the sense of future development of \masqmail\ by showing that email will remain an important technology in the future. It tries to identify future trends too.
|
|
meillo@352
|
39
|
|
meillo@370
|
40 Chapter 3 \textbf{deals with mail transfer agents} (\MTA{}s) which are the most important entities of the email transport structure. \MTA{}s are defined, classified, and the most important ones are presented and compared.
|
|
meillo@352
|
41
|
|
meillo@352
|
42 Chapter 4 \textbf{focuses on \masqmail's present and future}. It is the core of the thesis. Requirements are identified and lead to a list of pending work tasks. Then possible strategies for future development are discussed.
|
|
meillo@352
|
43
|
|
meillo@370
|
44 Chapter 5 \textbf{describes improvement plans} which are based on decisions in chapter four, in more detail. A proposed architecture for a redesigned \masqmail\ is presented, too.
|
|
meillo@352
|
45
|
|
meillo@352
|
46 Chapter 6 \textbf{summarizes} the most important results and closes the thesis.
|
|
meillo@352
|
47
|
|
meillo@352
|
48
|
|
meillo@352
|
49
|
|
meillo@33
|
50
|
|
meillo@98
|
51
|
|
meillo@98
|
52
|
|
meillo@280
|
53 \section*{Conventions}
|
|
meillo@302
|
54 %TODO: check it!
|
|
meillo@280
|
55 The following typographic conventions are used in this thesis:
|
|
meillo@150
|
56
|
|
meillo@304
|
57 \begin{enumerate}
|
|
meillo@316
|
58 \item \emph{Italic shape} is used to emphasize text, to introduce new terms, and for names, including product, host, and user names, as well as email addresses.
|
|
meillo@150
|
59
|
|
meillo@304
|
60 \item For names of persons \textsc{Small Caps} are used.
|
|
meillo@304
|
61
|
|
meillo@356
|
62 \item File and path names, contents of files, and output from programs are displayed in \texttt{Typewriter font}.
|
|
meillo@304
|
63 \end{enumerate}
|
|
meillo@150
|
64
|
|
meillo@302
|
65 References to external resources are marked using one of three styles, distinguished by the type of resource.
|
|
meillo@210
|
66
|
|
meillo@302
|
67 \begin{enumerate}
|
|
meillo@370
|
68 \item References to books, articles, and similar documents look like this: \cite{kernighan84}. The letters represent the author(s) (here \person{Kernighan} and \person{Pike}), while the number represents the year of publication (here 1984).
|
|
meillo@150
|
69
|
|
meillo@370
|
70 \item Websites are different from documents as they are less some text written by some author but more a place where information is gathered. Website may also change from time to time, thus the date of access is given to indicate the version to which was referred. References to websites have such appearance: \citeweb{masqmail:homepage}.
|
|
meillo@210
|
71
|
|
meillo@370
|
72 \item \name{Request for Comments} are those documents that define the Internet. They are referenced directly by their unique number. For instance: \RFC\,821.
|
|
meillo@302
|
73 \end{enumerate}
|
|
meillo@234
|
74
|
|
meillo@302
|
75 The Bibliography is located at the end of the thesis. It also includes a list of the relevant \RFC{}s and how they can be retrieved.
|
|
meillo@150
|
76
|
|
meillo@150
|
77
|
|
meillo@150
|
78
|
|
meillo@150
|
79
|
|
meillo@150
|
80
|
|
meillo@98
|
81 \section*{Acknowledgments}
|
|
meillo@33
|
82 %FIXME: write this at the very end.
|
|
meillo@33
|
83 % dont forget: proove readers, suggestion makers, supporters, ...
|
|
meillo@362
|
84 %\input{/home/meillo/da-various/acknowledgments.tex}
|
|
meillo@356
|
85
|
|
meillo@356
|
86
|
|
meillo@356
|
87
|
|
meillo@356
|
88
|
|
meillo@362
|
89 \vspace{9ex}
|
|
meillo@356
|
90 { \it
|
|
meillo@356
|
91 \hspace*{23em}markus schnalke\\
|
|
meillo@356
|
92 \hspace*{23em}February 2009
|
|
meillo@356
|
93 }
|
