|
89
|
1 \chapter{Improvements}
|
|
|
2
|
|
|
3
|
|
|
4 \section{Existing features}
|
|
|
5 This overview regards \masqmail version 0.2.21, the state this document starts off.
|
|
|
6
|
|
|
7 First of all \masqmail\ is an \MTA. Therefor it accepts mail on the command line and via \SMTP. Mail queueing and alias expansion is supported. \masqmail\ is able to deliver mail to local mailboxes (in \name{mbox} or \name{maildir} format) or pass it to a \name{mail delivery agent} (like \name{procmail}). Mail destinated to remote locations is sent via \SMTP. Outgoing \SMTP\ connections feature \name{SMTP-Auth} and \name{SMTP-after-POP} authentication, but incoming \SMTP\ does not.
|
|
|
8
|
|
|
9 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.
|
|
|
10
|
|
|
11 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.
|
|
|
12
|
|
|
13 Additional to the \mta\ job, \masqmail\ also offers mail retrieval services with being a \NAME{POP3} client. Thus it can fetch mail from remote locations, dependent on the active online route.
|
|
|
14
|
|
|
15
|
|
|
16
|
|
|
17
|
|
|
18 \section{Directions to go}
|
|
|
19
|
|
|
20 \subsection{\masqmail\ in five years}
|
|
|
21 \label{sec:masqmail-in-5-years}
|
|
|
22 Now how could \masqmail\ be like in, say, five years?
|
|
|
23 %requirements
|
|
|
24 %which parts to do
|
|
|
25 %how to make masqmail future-safe
|
|
|
26
|
|
|
27 %how to advertise masqmail
|
|
|
28 %difference for free software
|
|
|
29 %why is it worth to revive masqmail?
|
|
|
30
|
|
|
31
|
|
|
32 \subsection{A design from scratch}
|
|
|
33 %what would be needed
|
|
|
34 %would one create it at all?
|
|
|
35
|
|
|
36
|
|
|
37
|
|
|
38 \section{Work to do}
|
|
|
39
|
|
|
40
|
|
|
41 \section{Implementation}
|
|
|
42
|
|
|
43
|
|
|
44 \section{Work done}
|
|
|
45
|
|
|
46
|
|
|
47 \section{Test and validation}
|
|
|
48
|
