1 \clearpage

2 \chapter*{Preface}

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

4

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

6

7 << \textbf{say what you want to say} >>

8

9 << the overall goal of the document >>

10

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

12

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

14

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

16

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

18

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

20

21 usage examples:

22

23 debian popcon stats

24

25 << hikernet >>

26

27

28 \subsubsection*{Audience}

29

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

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

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

33

34 In each topic, basic knowledge is preconditioned.

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

36

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

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

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

40

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

42 . %FIXME: references

43 explain about administrating \unix.

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

45

46

47

48 \section*{Organisation}

49

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

51

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

53

54

55

56 \section*{Conventions}

57 %TODO: check it!

58 The following typographic conventions are used in this thesis:

59

60 \emph{Italic shape} is used to emphasize text and for all kinds of names, including command names, file name, hostnames, usernames, and email addresses, except names of persons for which \textsc{Small Caps} are used.

61

62 Source code, contents of files, and output from programs is displayed in \texttt{Typewriter font}.

63

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

65

66 \begin{enumerate}

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

68

69 \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}.

70

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

72 \end{enumerate}

73

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

75

76

77

78

79

80 \section*{Acknowledgments}

81 %FIXME: write this at the very end.

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

83 % FIXME: if too long, think about a page in the appendix