# HG changeset patch
# User meillo@marmaro.de
# Date 1231174929 -3600
# Node ID 6d21f55323b8a63c0481d042a398294f6bf23f79
# Parent  e9e83ad85d71229611c31b69c30621d5d92182f3
minor change

diff -r e9e83ad85d71 -r 6d21f55323b8 thesis/tex/6-NewDesign.tex
--- a/thesis/tex/6-NewDesign.tex	Mon Jan 05 18:01:50 2009 +0100
+++ b/thesis/tex/6-NewDesign.tex	Mon Jan 05 18:02:09 2009 +0100
@@ -47,7 +47,7 @@
 
 The mail queue and the module to manage it are the central part of the whole system. This demands especially for robustness and reliability, as a failure here can lead to loosing mail. An \MTA\ takes over responsibility for mail in accepting it, hence loosing mail messages is absolutely to avoid. This covers any kind of crash situation too. The worst thing acceptable to happen is a mail to be sent twice.
 
-\sendmail, \exim, \qmail, \name{sendmail X}, and \masqmail\ feature one single mail queue. \postfix\ has three of them: \name{incoming}, \name{active}, and \name{deferred}. (The \name{maildrop} queue is excluded, as it is only used for the \texttt{sendmail} command.)
+\sendmail, \exim, \qmail, \name{sendmail X}, and \masqmail\ feature one single mail queue. \postfix\ has more of them.
 
 \MTA\ setups that include content scanning tend to require two separate queues. To use \sendmail\ in such setups requires two independent instances, with two separate queues, running. \exim\ can handle it with special \name{router} and \name{transport} rules, but the data flow gets complicated. Hence an idea is to use two queues, \name{incoming} and \name{active} in \postfix's terminology, with the content scanning within the move from \name{incoming} to \name{active}.