Mercurial > docs > diploma
comparison thesis/tex/1-Introduction.tex @ 229:c5f44219bc5d
added text parts to intro
author | meillo@marmaro.de |
---|---|
date | Fri, 09 Jan 2009 14:22:06 +0100 |
parents | aab8499c9f2f |
children | d60e5843db7f |
comparison
equal
deleted
inserted
replaced
228:265f3f9dd44a | 229:c5f44219bc5d |
---|---|
2 \label{chap:introduction} | 2 \label{chap:introduction} |
3 | 3 |
4 << say what you want to say >> | 4 << say what you want to say >> |
5 | 5 |
6 << the overall goal of the document >> | 6 << the overall goal of the document >> |
7 | |
8 | |
9 | |
10 \section{What's an MTA?} | |
11 | |
12 The basic job of a \mta\ is to transport mail from senders to recipients. This is the definition of such kind of software, and this is how \MTA{}s are generally seen \cite[page 19]{dent04} \cite[pages 3-5]{hafiz05}. | |
13 | |
14 An \MTA\ therefore needs at least a mail receiving facility and a mail sending facility. | |
15 | |
16 << structure diagram of an MTA (and of masqmail) >> | |
17 | |
18 | |
7 | 19 |
8 | 20 |
9 | 21 |
10 \section{The \masqmail\ project} | 22 \section{The \masqmail\ project} |
11 \label{sec:masqmail} | 23 \label{sec:masqmail} |
56 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. | 68 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. |
57 | 69 |
58 A better setup is to run \masqmail\ on every machine %FIXME | 70 A better setup is to run \masqmail\ on every machine %FIXME |
59 | 71 |
60 | 72 |
73 \subsubsection{Online detection and routes} | |
74 \label{sec:masqmail-routes} | |
75 | |
61 --- | 76 --- |
62 | 77 |
63 As \masqmail\ is focused on non-permanent Internet connections, online state can be queried by three methods: reading from a file, reading the output of a command, or by asking an \name{mserver}. Each method may return a string indicating one of the available routes being online, or returning nothing to indicate offline state. | 78 As \masqmail\ is focused on non-permanent Internet connections, online state can be queried by three methods: reading from a file, reading the output of a command, or by asking an \name{mserver}. Each method may return a string indicating one of the available routes being online, or returning nothing to indicate offline state. |
64 | 79 |
65 Delivery to recipients on the local host or in local nets is done at once; delivery to recipients on the Internet is only done when being online, and queued otherwise. Each online route may have a different mail server to which mail is relayed. Return address headers are modified appropriate if wished. | 80 Delivery to recipients on the local host or in local nets is done at once; delivery to recipients on the Internet is only done when being online, and queued otherwise. Each online route may have a different mail server to which mail is relayed. Return address headers are modified appropriate if wished. |
66 | 81 |
67 --- | 82 --- |
83 | |
84 \masqmail\ focuses on non-permanent online connections, thus a concept of online routes is used. One may configure any number of routes to send mail. Each route can have criteria, like matching \texttt{From:} or \texttt{To:} headers, to determine if some message is allowed to be sent over it. Mail to destinations outside the local network gets queued until an online connections is available. | |
68 | 85 |
69 | 86 |
70 | 87 |
71 | 88 |
72 | 89 |