1 \clearpage

2 \chapter*{Preface}

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

4

5 << preface text (about 1 page) >> %FIXME

6

7 goal: revive masqmail; make it future save; clean it up; add some missing features; release a new version

8

9 << write about the motivation to cover this topic: what is it I want? >> %FIXME

10

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

12

13 << make the topic more concrete and limit it >> %FIXME

14

15 << have text by oliver here? >> %TODO

16

17 usage examples:

18

19 debian popcon stats

20

21 << hikernet >>

22

23

24 \subsubsection*{Audience}

25

26 This document is targeted for \masqmail\ users and for people interested in mail systems in general.

27 Security problems in electronic mail, \unix\ and the C programming language will also be discussed.

28 Additional ones planning to take over an unmaintained software project will find real life experience in here.

29

30 In each topic, basic knowledge is preconditioned.

31 Nevertheless introductions are given and sources for further reading will be mentioned.

32

33 This work focuses on the \unix\ operating system.

34 Experience in usage, administration and program development is assumed.

35 This includes the basic toolchain (e.g.\ \name{tar}, \name{grep}, etc.), user, file and permission management, as well as writing, compiling and installing programs written in the C language.

36

37 General information about \unix\ can be found in \cite{kernighan84} %FIXME: references

38 . %FIXME: references

39 explain about administrating \unix.

40 And developing programs in C may be learned from \cite{k&r} and \cite{rochkind85}. %FIXME: references

41

42 %TODO: should I tell them to send email to me when having questions? Or somewhere else?

43

44

45 \section*{Organisation}

46

47 << write about organisation of the book: parts, chapters, sections. And more thats useful to know. >> %FIXME

48

49 << explain where the main part lies (theory vs. implementation) >> %FIXME:

50

51 << write about the bundled CD, and tell what's included >> %TODO

52

53

54 \section*{Conventions}

55 %TODO: check if this tells what is really used!

56 %FIXME: make it complete!

57 %FIXME: remove everything not needed. Maybe write only a few sentences text.

58 The following typographic conventions are used in this thesis:

59

60 \begin{tabular}{ p{0.25\textwidth} p{0.7\textwidth} }

61 \emph{Italics} &

62 is used for names, including command names, file name, hostnames, usernames and email addresses.

63 Further more it is used to emphasize text.

64 \\ &\\

65

66 \texttt{Constant Width} &

67 is used for source code, contents of files and output from programs.

68 \\ &\\

69

70 \person{Small Caps} &

71 are used to indicate names of persons.

72 \\ &\\

73 \end{tabular}

74

75 References to external resources are marked using one of three styles:

76

77 \begin{tabular}{ p{0.25\textwidth} p{0.7\textwidth} }

78 \cite{kernighan84} &

79 is a reference to a book, an article, or a similar document. The Bibliography is located at the end of the thesis.

80 \\ &\\

81

82 \citeweb{masqmail:homepage} &

83 is a reference to a website. Websites differ from documents as they are less of a text written by some author, but more a place where information is gathered.

84 \\ &\\

85

86 \RFC821 &

87 is a reference to the \name{Request For Comments}, here the one numbered 821. \RFC{}s are only referenced in this way. A list of relevant \RFC{}s and how they can be retrieved is available in the Appendix. %fixme: add ref

88 \\ &\\

89 \end{tabular}

90

91

92

93

94

95 \section*{Acknowledgments}

96 %FIXME: write this at the very end.

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

98 % FIXME: if too long, include a file on the CD and refer on it here