
meillo@109: \chapter{\masqmail's present and future}
meillo@93: 
meillo@99: <<  plans to get masqmail more popular again (if that is the goal) >> %FIXME
meillo@93: 
meillo@99: <<  concrete decisions based on results of the last 2 chapters >> %FIXME
meillo@93: 
meillo@93: \section{Existing features}
meillo@117: This overview regards \masqmail\ version 0.2.21, the state this document starts off.
meillo@93: 
meillo@93: 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.
meillo@93: 
meillo@93: 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.
meillo@93: 
meillo@93: 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.
meillo@93: 
meillo@93: 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.
meillo@93: 
meillo@93: 
meillo@109: \subsubsection*{masqmail stuff}
meillo@109: 
meillo@109: The \masqmail\ executable can be called under various names for \name{sendmail-compatibility} reasons. This is commonly organized by creating symbolic links with with different names to the \masqmail\ executable. These are \path{/usr/lib/sendmail} and \path{/usr/sbin/sendmail} because many programs expect a \mta\ to be located there. Further more \sendmail\ provides shortcuts by calling it with a different name instead of supplying command line arguments. The best known of it is \path{mailq}, which is equivilent to calling the \MTA\ with the argument \verb+-bq+. \masqmail\ reacts to the names \path{mailq}, \path{smtpd}, \path{mailrm}, \path{runq}, \path{rmail}, and \path{in.smtpd}. The last four are an addition to \sendmail. Not implemented is the name \path{newaliases} because it is not relevant to \masqmail. To provide the command nonetheless, one may write a shell script located at \path{/usr/bin/newaliases}, that simply invokes \verb+masqmail -bi+.
meillo@109: 
meillo@109: %masqmail: mailq, mailrm, runq, rmail, smtpd/in.smtpd
meillo@109: %sendmail: hoststat, mailq, newaliases, purgestat, smtpd
meillo@109: 
meillo@109: \masqmail\ is written in the \NAME{C} programming language. The program, as of version 0.2.21, consists of 34 source code and eight header files, containing about 9,000 lines of code\footnote{Measured with \name{sloccount} by David A.\ Wheeler.}. Additionally, it includes a \name{base64} implementation (about 300 lines) and \name{md5} code (about 150 lines). For systems that do not provide \name{libident}, this library is distributed as well (circa 600 lines); an available shared library however has higher precedence in linking.
meillo@109: 
meillo@109: The only mandatory dependency is \name{glib}---a cross-platform software utility library, originated in the \NAME{GTK+} project. It provides safer replacements for many standard library functions. (The unsafe \verb+sprintf()+ is one example.) Also it offers handy data containers, easy-to-use implementations of data structures, and much more.
meillo@109: 
meillo@109: With \masqmail\ comes the small tool \path{mservdetect}; it helps setting up a configuration that uses the \name{mserver} system to detect the online state. Two other binaries get compiled for testing purposes: \path{readtest} and \path{smtpsend}. All three programms use \masqmail\ source code; they only add a file with a \verb+main()+ function each.
meillo@109: 
meillo@109: \masqmail\ does not provide an interface for modules with additional functionality. There exists no add-on or module system. But the code is separated by function to the various source files, and some functional parts can be included or excluded by defining symbols. This means adding some argument (like \verb+--enable-maildir+) to the \verb+configure+ call. Thus the concerning code gets not removed by the preprocessor.
meillo@93: 
meillo@93: 
meillo@93: \section{Directions to go}
meillo@93: 
meillo@93: \subsection{\masqmail\ in five years}
meillo@93: \label{sec:masqmail-in-5-years}
meillo@93: Now how could \masqmail\ be like in, say, five years?
meillo@93: 
meillo@99: << requirements >> %FIXME
meillo@99: 
meillo@99: << which parts to do >> %FIXME
meillo@99: 
meillo@99: << how to make masqmail future-safe >> %FIXME
meillo@99: 
meillo@99: << how to advertise masqmail >> %FIXME
meillo@99: 
meillo@99: << difference for free software >> %FIXME
meillo@99: 
meillo@99: << why is it worth to revive masqmail? >> %FIXME
meillo@93: 
meillo@93: 
meillo@93: \subsection{A design from scratch}
meillo@99: 
meillo@99: << what would be needed (effort) >> %FIXME
meillo@99: 
meillo@99: << would one create it at all? >> %FIXME
meillo@99: 
meillo@99: << should it be done? >> %FIXME
meillo@93: 
meillo@93: 
meillo@93: 
meillo@93: \section{Work to do}
meillo@93: 
meillo@99: << which parts to take out and do within the thesis >> %FIXME
meillo@93: 




