docs/diploma
annotate thesis/pieces/requirements.tex @ 159:da9a8f9f9081
changed layout
author | meillo@marmaro.de |
---|---|
date | Wed, 17 Dec 2008 15:12:42 +0100 |
parents | |
children |
rev | line source |
---|---|
meillo@86 | 1 \chapter{Use cases} |
meillo@86 | 2 |
meillo@86 | 3 Here follow typical use cases for \masqmail. If other \MTA{}s are better suited for certain use cases, it will be mentioned. The use cases are prestage for defining the requirements. |
meillo@86 | 4 |
meillo@86 | 5 %FIXME: rewrite! |
meillo@86 | 6 % How do I write use cases?? |
meillo@86 | 7 % Are use cases the right tool for what I need, at all?? |
meillo@86 | 8 |
meillo@86 | 9 The user writes email with one of the common programs (e.g. \path{/bin/mail} or \name{mutt}). \masqmail\ must provide an interface, to that prepared mail can be handled over. |
meillo@86 | 10 |
meillo@86 | 11 \masqmail\ must deliver mail to its destination. |
meillo@86 | 12 |
meillo@86 | 13 Mail must be send with different settings, if someone uses more than one internet connection. |
meillo@86 | 14 |
meillo@86 | 15 If the machine is offline, no mail, destinated to the internet, must be send. It needs to be queued until an online connection gets established. |
meillo@86 | 16 |
meillo@86 | 17 If the computer goes online, all mail for outside destinations, should be send through the active route. |
meillo@86 | 18 |
meillo@86 | 19 Local mail should be send at once, independent of the online state. |
meillo@86 | 20 |
meillo@86 | 21 \masqmail\ may act as \NAME{SMTP} server. To receive email from other hosts. |
meillo@86 | 22 |
meillo@86 | 23 Mail for local users should be delivered by \masqmail\ itself or passed to \name{mail delivery agent}s. |
meillo@86 | 24 |
meillo@86 | 25 \masqmail\ needs to provide the same interface as \sendmail\ has, for being a drop-in replacement. |
meillo@86 | 26 |
meillo@86 | 27 |
meillo@86 | 28 %TODO: add Schaeffter's ideas here |
meillo@86 | 29 \chapter{Requirements} |
meillo@86 | 30 |
meillo@86 | 31 \section{Structure} |
meillo@86 | 32 \section{Security} |
meillo@86 | 33 \section{Usability} |
meillo@86 | 34 \chapter{Security issues} |
meillo@86 | 35 |
meillo@86 | 36 %TODO: write about: |
meillo@86 | 37 % #ifdefs in code |
meillo@86 | 38 % the single setuid root binary |