| rev |
line source |
|
meillo@26
|
1 \chapter{Introduction}
|
|
meillo@42
|
2 \label{chap:introduction}
|
|
meillo@26
|
3
|
|
meillo@96
|
4 << say what you want to say >>
|
|
meillo@92
|
5
|
|
meillo@102
|
6 << the overall goal of the document >>
|
|
meillo@92
|
7
|
|
meillo@92
|
8
|
|
meillo@92
|
9
|
|
meillo@92
|
10 \section{The \masqmail\ project}
|
|
meillo@102
|
11 \label{sec:masqmail}
|
|
meillo@96
|
12
|
|
meillo@96
|
13 << about masqmail (some history) >>
|
|
meillo@96
|
14
|
|
meillo@96
|
15 (include history of email, definition of MTA and sendmail-compatibility in text)
|
|
meillo@96
|
16
|
|
meillo@132
|
17 The \masqmail\ program was written by \person{Oliver Kurth}, starting in 1999. His aim was to create a small \mta\ which is especially focused on computers with dial-up connections to the internet. \masqmail\ is easy configurable for situations which are rarely solveable with the common \MTA{}s.
|
|
meillo@102
|
18
|
|
meillo@102
|
19 \masqmail\ queues mail for destinations outside the local network if no connection to the internet is online. If the machine goes online, this mail is sent. Mail to local machines is sent immediately.
|
|
meillo@102
|
20
|
|
meillo@102
|
21 While the other \MTA{}s are more general purpose \MTA{}s, \masqmail\ aims on special situations only. Nevertheless can it handle ordinary mail transfers too.
|
|
meillo@102
|
22
|
|
meillo@102
|
23 \masqmail\ is released under the \GPL, which makes it \freesw. The latest stable version is 0.2.21 from November 2005.
|
|
meillo@102
|
24
|
|
meillo@102
|
25 The program's new homepage \citeweb{masqmail:homepage} provides further information about this \MTA.
|
|
meillo@96
|
26
|
|
meillo@92
|
27
|
|
meillo@92
|
28 \subsubsection{Target field}
|
|
meillo@132
|
29 Its original author, \person{Oliver Kurth}, sees \masqmail\ so:
|
|
meillo@92
|
30 \begin{quote}
|
|
meillo@92
|
31 MasqMail is a mail server designed for hosts that do not have a permanent internet connection eg. a home network or a single host at home. It has special support for connections to different ISPs. It replaces sendmail or other MTAs such as qmail or exim.
|
|
meillo@92
|
32 \end{quote}
|
|
meillo@92
|
33
|
|
meillo@92
|
34 \masqmail\ is inteded to cover a specific niche: non-permanent internet connection and different \NAME{ISP}s.
|
|
meillo@92
|
35
|
|
meillo@92
|
36 Although it can basically replace other \MTA{}s, it is not generally aimed to do so. The package description of \debian\citeweb{packages.debian:masqmail} states this more clearly by changing the last sentence to:
|
|
meillo@92
|
37 \begin{quote}
|
|
meillo@92
|
38 In these cases, MasqMail is a slim replacement for full-blown MTAs such as sendmail, exim, qmail or postfix.
|
|
meillo@92
|
39 \end{quote}
|
|
meillo@92
|
40 \masqmail\ is a good replacement ``in these cases'', but not generally, since is lacks features essential for running on mail servers. It is primarily not secure enough for being accessable from untrusted locations.
|
|
meillo@92
|
41
|
|
meillo@92
|
42 The program is best used in home networks, which are non-permanently connected to the internet. \masqmail\ sends mail to local destinations, like users on the same machine and on other machines in the local net, immediately. Email to recipients outside the local net are queued when offline and sent when a online connection gets established.
|
|
meillo@92
|
43
|
|
meillo@92
|
44 Further more does \masqmail\ respect online connections through different \NAME{ISP}s; a common thing for dial-up connections. In particular can different sender addresses be set, dependent on the \NAME{ISP} that is used. This prevents mail to be likely classified as spam.
|
|
meillo@92
|
45
|
|
meillo@92
|
46
|
|
meillo@92
|
47
|
|
meillo@92
|
48 \subsubsection{Typical usage}
|
|
meillo@92
|
49 This section describes situations that make senseful use of \masqmail.
|
|
meillo@92
|
50
|
|
meillo@92
|
51 A home network consisting of some workstations without a server. The network is connected to the internet by dial-up or broadband. Going online is initiated by computers inside the local net. \NAME{IP} addresses change at least once every day.
|
|
meillo@92
|
52
|
|
meillo@92
|
53 Every workstation would be equiped with \masqmail. Mail transfer within the same machine or within the local net works straight forward. Outgoing mail to the internet is sent, to the concerning \NAME{ISP} for relaying, whenever the router goes online. Receiving of mail from outside needs to be done by a mail fetch program, like the \masqmail\ internal \NAME{POP3} client or \name{fetchmail} for example. The configuration for \masqmail\ would be the same on every computer, except the hostname.
|
|
meillo@92
|
54
|
|
meillo@92
|
55 For the same network but having a server, one could have \masqmail\ running on the server and using simple forwarders (see \ref{subsec:relay-only}) to the server on the workstations. This setup does only support mail transfer to the server, but not back to a workstation; also sending mail to another user on the same workstation is not possible.
|
|
meillo@92
|
56
|
|
meillo@92
|
57 A better setup is to run \masqmail\ on every machine %FIXME
|
|
meillo@92
|
58
|
|
meillo@92
|
59
|
|
meillo@92
|
60
|
|
meillo@92
|
61 \subsubsection{What makes it special}
|
|
meillo@92
|
62
|
|
meillo@92
|
63 As main advantage, \masqmail\ makes it easy to set up an \MTA\ on workstations or notebooks without the need to do complex configuration or to be an mail server expert.
|
|
meillo@92
|
64
|
|
meillo@92
|
65 Workstations use %FIXME
|
|
meillo@92
|
66
|
|
meillo@96
|
67 \textbf{Alternatives?}
|
|
meillo@92
|
68 % http://anfi.homeunix.org/sendmail/dialup10.html
|
|
meillo@92
|
69
|
|
meillo@92
|
70
|
|
meillo@92
|
71
|
|
meillo@96
|
72 << explain why masqmail is old and why it is interesting/important however! >> %FIXME
|
|
meillo@96
|
73
|
|
meillo@96
|
74
|
|
meillo@96
|
75
|
|
meillo@92
|
76 \section{Problems to solve}
|
|
meillo@92
|
77
|
|
meillo@96
|
78 << what problems has masqmail? >> %FIXME
|
|
meillo@96
|
79
|
|
meillo@96
|
80 << what's the intention of this document? >> %FIXME
|
|
meillo@96
|
81
|
|
meillo@96
|
82 << why is it worth the effort? >> %FIXME
|
|
meillo@96
|
83
|
|
meillo@96
|
84
|
|
meillo@96
|
85
|
|
meillo@96
|
86
|
|
meillo@97
|
87 \section{How to read this document}
|
|
meillo@96
|
88
|
|
meillo@96
|
89 \subsubsection*{Conventions used}
|
|
meillo@96
|
90 %TODO: check if this tells what is really used!
|
|
meillo@96
|
91 %FIXME: make it complete!
|
|
meillo@96
|
92 %FIXME: remove everything not needed. Maybe write only a few sentences text.
|
|
meillo@96
|
93 The following typographic conventions are used in this book:
|
|
meillo@96
|
94
|
|
meillo@96
|
95 \begin{tabular}{ p{0.15\textwidth} p{0.8\textwidth} }
|
|
meillo@96
|
96 \emph{Italic} &
|
|
meillo@96
|
97 is used for names, including command names, file name, hostnames, usernames and email addresses.
|
|
meillo@96
|
98 Further more it is used to emphasize text.
|
|
meillo@96
|
99 \\ &\\
|
|
meillo@96
|
100
|
|
meillo@96
|
101 \texttt{Constant Width} &
|
|
meillo@96
|
102 is used for source code, contents of files and output from programs.
|
|
meillo@96
|
103 \\ &\\
|
|
meillo@96
|
104
|
|
meillo@96
|
105 \texttt{\$} &
|
|
meillo@96
|
106 indicates the the user shell prompt.
|
|
meillo@96
|
107 \\ &\\
|
|
meillo@96
|
108
|
|
meillo@96
|
109 \texttt{\#} &
|
|
meillo@96
|
110 indicates the the root shell prompt.
|
|
meillo@96
|
111 \\
|
|
meillo@96
|
112 \end{tabular}
|
|
meillo@96
|
113
|
|
meillo@96
|
114
|
|
meillo@96
|
115
|
|
meillo@96
|
116
|
|
meillo@96
|
117 \section{Further reading}
|
|
meillo@96
|
118
|
|
meillo@96
|
119 << specify the really important external documents here >> %FIXME
|
|
meillo@96
|
120
|
|
meillo@96
|
121 << write about the bundled CD, and tell what's included >> %FIXME
|
|
meillo@96
|
122
|
|
meillo@96
|
123 \NAME{RFC}s, other books, source code, websites
|
|
meillo@96
|
124
|
|
meillo@96
|
125
|
