# HG changeset patch # User markus schnalke # Date 1336495032 -7200 # Node ID b687d151eed3c177e0f5a023b8e474cb56ca6cca # Parent fc94b960793ec18df3274316cb818bf5ddd64228 Reorganized the content in the Intro and added placeholders for missing parts. diff -r fc94b960793e -r b687d151eed3 ch01.roff --- a/ch01.roff Tue May 08 17:45:02 2012 +0200 +++ b/ch01.roff Tue May 08 18:37:12 2012 +0200 @@ -7,20 +7,31 @@ it headed to. This shall give an overview. +.H1 "Email Prerequisites +.P +XXX Do we really need that? + + .H1 "What is MH? .P MH is an electronic mail system, originating in the RAND Corporation. -Historically, it had been a all-in-one mail system, with Mail Transfer +Historically, it had been a all-in-one mail system, with both Mail Transfer Agent (MTA) and Mail User Agent (MUA). -Later, when electronic mail systems changed, Mail Submission Agent (MSA) +Later, when email setups changed, Mail Submission Agent (MSA) and Mail Retrieval Agent (MRA) facilities were added. The MTA became less important, whereas the MUA became even more the central part. .P -First of all, MH is a style of a mail handling system. +MH defines a mail handling concept. It had started as a design proposal, not as an implementation, and -had in spirit remained so. This is similar to Unix, which much less -is a specific software product, as it is a style of system design. +in spirit had remained this way. This is similar to Unix, which +rather is a style of system design than specific software product. +.P +XXX Link to the Unix phil. +.P +XXX comparision to monolithic mail systems. +.P +XXX Differenciation of MUA and mail system. .U2 "History .P @@ -28,7 +39,7 @@ In 1977, Norman Shapiro and Stockton Gaines had proposed the design of a new mail handling system, called ``Mail Handler'' (MH) for RAND, to superseed their ``Mail System'' (MS). -Two years later, in 1979, XXX took the proposal and implemented a +Two years later, in 1979, Bruce Borden took the proposal and implemented a prototype of MH. It proved successful and replaced MS thereafter. .P A decade later, the University of California had started to use MH. @@ -43,26 +54,6 @@ (nmh), a fork of MH. He intended to modernize MH, improve its MIME capabilities, and this should be done openly within the Internet community. Today, nmh almost completely replaced the original MH. -.P -Three versions of MH are available: -.BU -.B "Old MH" . -In most cases it has been replaced by nmh, but some systems still -provide old MH. As nmh is old MH-compatible, there exist few reasons -not to upgrade to new. -The development of old MH stopped almost completely. -.BU -.B Nmh . -The most widespread version of MH. Backward-compatible to old MH. -Provides new featues, which need to be activated explicitely. -Its development went slowly in the previous years, but had revived -in Fall 2011. -.BU -.B Mmh -A descendent of nmh. Had started as a non-compatible experimental -version, but became de facto a fork. Tries to expand the same -principle concepts in a more modern way. This version of MH is the -subject of this thesis. .U2 "Concepts .P @@ -87,8 +78,38 @@ MH allows the user to automate almost everything and to modify amost any behavior. The system is scriptable and extendable. +.U2 "Available Versions +.P +Three versions of MH are available today: +.BU +.I "Original MH" . +In most cases it has been replaced by nmh, but some systems still +provide old MH. As nmh is old MH-compatible, there exist few reasons +not to upgrade to new. +The development of old MH has stopped after the 6.8.4 release in +February 1996. +.BU +.I nmh . +The most widespread version of MH was forked off version 6.8.3 in December +1996. It incorporated the \fILBL changes\fP. +It provides backward-compatible to old MH by having new featues deactivated +by default. To use them, the user needs to activate them explicitely. +Its development went slowly in the previous years, but had revived +in December 2011. +.BU +.I mmh . +This version is the subject of this thesis. +It is a descendent of nmh. It had started as a non-compatible experimental +version, but became de facto a fork. It tries to expand the same +principle concepts in a more modern way. -.H1 "Understanding of the Code and Community +.U2 "Example Session +.P +Example mail handling session with mmh, but mostly compatible with nmh +and old MH. The look'n'feel is common among them. + + +.H1 "Understanding the Code and Community .P In order to understand the state, goals and dynamics of a project, one needs to know its history. MH comes from a time before the @@ -135,7 +156,38 @@ back-end. -.H1 "My Vision +.H1 "mmh + +.U2 "Motivation +.P +XXX + +.U2 "Why it is worth it +.P +XXX + +.U2 "Target Field +.P +XXX Target field and scenarios +.P +The target user in mind likes Unix and its philosophy. +He likes to use programs that are conceptionally appealing. +He's familiar with the command line and enjoys its power. +He is at least capable of shell scripting and wants to improve his +productivity by scripting the mail system. +His computer and operating system are from post-ANSI C times. +He likes to attach files, exchanges text containing non-ASCII +characters, signs or encrypts his messages. +He does not use bulletin boards anymore, nor non-mbox style mail +drops, nor does he rely on compatibility to nmh. +He already has and MTA/MSA and MRA running or is able to set them +up. +He does not want to have to read a book in order to make his MUA +usable. +.P +XXX Limitations + +.U2 "The Vision .P The general goals of the mmh project are the following: .BU @@ -152,27 +204,10 @@ .BU I plan to remove any optimizations that rises obscurity, unless it appears to be neccessary to make mmh usable at all. -.P -.B "The target user in mind -likes Unix and its philosophy. -He likes to use programs that are conceptionally appealing. -He's familiar with the command line and enjoys its power. -He is at least capable of shell scripting and wants to improve his -productivity by scripting the mail system. -His computer and operating system are from post-ANSI C times. -He likes to attach files, exchanges text containing non-ASCII -characters, signs or encrypts his messages. -He does not use bulletin boards anymore, nor non-mbox style mail -drops, nor does he rely on compatibility to nmh. -He already has and MTA/MSA and MRA running or is able to set them -up. -He does not want to have to read a book in order to make his MUA -usable. - -.H1 "Things to do +.U2 "Work to do .BU -Remove any MTA and MRA facilities. Mmh shall concentrate on the MUA +Remove the MTA and MRA facilities. Mmh shall concentrate on the MUA task. Mail shall enter mmh's mail storage via the system mail drop and it shall leave mmh via the local \fLsendmail\fP command. .BU @@ -195,3 +230,10 @@ Integrate MIME support deeper and more natural into MH. .BU Provide a ready-to-use setup out-of-the-box. + + +.H1 "Goals of this Thesis + +.U2 "Methods +.P +foo diff -r fc94b960793e -r b687d151eed3 preface.roff --- a/preface.roff Tue May 08 17:45:02 2012 +0200 +++ b/preface.roff Tue May 08 18:37:12 2012 +0200 @@ -122,7 +122,10 @@ .\" What audience is expected? +.\" What will not be covered (delimitation). + .\" General required knowledge (C, email, ...) +.\" cf. Email Prerequisites in the Introduction. .H1 "Conventions" no