1 \clearpage

2 \chapter*{Preface}

3 \addcontentsline{toc}{section}{Preface}

4

5 This thesis is about \masqmail, a small mail transfer agent for workstations and home networks. I chose \masqmail\ in October 2007 because of its small size while it is still a ``real'' mail transfer agent. \masqmail\ served me well since then and I found no reasons to change.

6

7 Unfortunately, the \masqmail\ package in \debian, which is my preferred \NAME{GNU}/Linux distribution, is unmaintained since the beginning of 2008. Unmaintained packages with critical bugs are likely to get dropped out of a distribution. Although \masqmail\ has had no critical bugs then, this was a situation I definately wanted to prevent.

8

9 Using my diploma thesis as a ``power-start'' to maintaining and developing \masqmail\ in the future was a great idea. As it came to my mind, while lying in bed, I knew this is the thing I \emph{wanted} to do. --- I did it! :-)

10

11

12 \vspace{3ex}

13 %\subsubsection*{Goal of the document}

14

15 The overall goal of this document is revive \masqmail\ in usage and development. \masqmail\ was not developed for over five years but the world of email changed during this time. Hence quite some work needs to be done.

16

17 I chose to start down at the basis and analyse the environment and \masqmail\ throughoutly, to end in concrete plans of what should be done how to let \masqmail\ become a modern mail transfer agent again.

18

19 The actual implementation of the the proposed changes goes beyond this thesis. Here are solutions described but not implemented. I did work in the code and have fix bugs during the time I wrote on the thesis, though.

20

21

22 \vspace{3ex}

23

24 %\subsubsection*{Audience}

25

26 This document is primary written with an audience of \masqmail\ developers or 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.

27

28 However, at least basic knowledge about \unix\ and the C programming language is preconditioned for the chapters three, four, and five. The required knowledge about \unix\ can be gained from \person{Kernighan} and \person{Pike}'s ``The \NAME{UNIX} Programming Environment'' \cite{kernighan84}. Programming in the C language is best learned from \person{Kernighan} and \person{Ritchie}'s ``The C Programming Language'' \cite{k&r}.

29

30

31

32

33

34 %<< \textbf{say what you want to say} >>

35 %

36 %<< preface == target of the book, related to the reader >> %FIXME

37 %

38 %<< have text by Oliver here? >> %TODO

39

40

41

42 %<< hikernet >>

43

44

45 %how to get the masqmail source code

46

47

48

49

50

51

52

53

54 \section*{Organization}

55

56 This document is organized in six chapters. Each chapter covers a delimited part of the overall topic and builds upon the knowledge and results of the previous ones. The first three chapters lead into the topic and create a solid base to build the second part upon. Chapter four and five are the central part of the thesis as they focus on \masqmail.

57

58 Chapter 1 \textbf{introduces} \masqmail\ to the reader. It presents the properties, goals, advantages, and problems of the program. General knowledge about the email technology is also describes and later assumed to be know.

59

60 Chapter 2 \textbf{analyses the market} of electronic communication and email. This chapter provides a secure basis by showing that email will remain an important technology in the future. It tries to identify future trends too.

61

62 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 important ones presented and compared.

63

64 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.

65

66 Chapter 5 \textbf{describes improvement plans}, as defined in chapter four, in more detail. A proposed architecture for a redesigned \masqmail\ is presented too.

67

68 Chapter 6 \textbf{summarizes} the most important results and closes the thesis.

69

70

71

72

73

74

75 \section*{Conventions}

76 %TODO: check it!

77 The following typographic conventions are used in this thesis:

78

79 \begin{enumerate}

80 \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.

81

82 \item For names of persons \textsc{Small Caps} are used.

83

84 \item File and path names, source code excerpts, contents of files, and output from programs are displayed in \texttt{Typewriter font}.

85 \end{enumerate}

86

87 References to external resources are marked using one of three styles, distinguished by the type of resource.

88

89 \begin{enumerate}

90 \item References to books, articles, and similar documents looks like this: \cite{kernighan84}. The letters represent the author(s) (here \person{Kernighan} and \person{Pike}), the number represents the year of publication (here 1984).

91

92 \item Websites differ from documents as they are less of a text written by some author but more a place where information is gathered. They are only indicated by numbers, like for example: \citeweb{masqmail:homepage}.

93

94 \item \name{Request for Comments}---documents that define Internet standards---are referenced in a third way, by specifying the unique number of the \RFC\ directly: \RFC821.

95 \end{enumerate}

96

97 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.

98

99

100

101

102

103 \section*{Acknowledgments}

104 %FIXME: write this at the very end.

105 % dont forget: proove readers, suggestion makers, supporters, ...