Mercurial > docs > diploma
comparison thesis/tex/5-Improvements.tex @ 273:92578f124df6
reorganized the input files and sorted old ones out
| author | meillo@marmaro.de |
|---|---|
| date | Thu, 15 Jan 2009 12:29:54 +0100 |
| parents | c80b6b6fb798 |
| children | 8a25b6262497 |
comparison
equal
deleted
inserted
replaced
| 272:2aad3d950640 | 273:92578f124df6 |
|---|---|
| 379 | 379 |
| 380 Left is only communication between the receiver modules and \name{queue-in}, and between \name{queue-out} and the transport modules. Data is exchanged done using \unix\ pipes and a simple protocol is used. | 380 Left is only communication between the receiver modules and \name{queue-in}, and between \name{queue-out} and the transport modules. Data is exchanged done using \unix\ pipes and a simple protocol is used. |
| 381 | 381 |
| 382 \begin{figure} | 382 \begin{figure} |
| 383 \begin{center} | 383 \begin{center} |
| 384 \input{input/ipc-protocol.tex} | 384 \codeinput{input/ipc-protocol.txt} |
| 385 %\includegraphics[scale=0.75]{img/ipc-protocol.eps} | |
| 385 \end{center} | 386 \end{center} |
| 386 \caption{State diagram of the protocol used for \NAME{IPC}} | 387 \caption{State diagram of the protocol used for \NAME{IPC}} |
| 387 \label{fig:ipc-protocol} | 388 \label{fig:ipc-protocol} |
| 388 \end{figure} | 389 \end{figure} |
| 389 | 390 |
| 410 | 411 |
| 411 The spool file format is basically the same as the one in current \masqmail: one file for the message body, the other for envelope and header information. The data file is stored in a separate data pool. It is written by \name{queue-in}, \name{scanning} can read it if necessary, \name{queue-out} reads it to generate the outgoing message, and deletes it after successful transfer. The header file (including the envelope) is written into the \name{incoming} queue. The \name{scanning} modules reads it, processes it, and writes a modified copy into the \name{outgoing} queue; the file in \name{incoming} is deleted then. \name{queue-out} finally takes the header file from \name{outgoing} to generate the resulting message. This data flow is shown in figure \ref{fig:queue-data-flow}. | 412 The spool file format is basically the same as the one in current \masqmail: one file for the message body, the other for envelope and header information. The data file is stored in a separate data pool. It is written by \name{queue-in}, \name{scanning} can read it if necessary, \name{queue-out} reads it to generate the outgoing message, and deletes it after successful transfer. The header file (including the envelope) is written into the \name{incoming} queue. The \name{scanning} modules reads it, processes it, and writes a modified copy into the \name{outgoing} queue; the file in \name{incoming} is deleted then. \name{queue-out} finally takes the header file from \name{outgoing} to generate the resulting message. This data flow is shown in figure \ref{fig:queue-data-flow}. |
| 412 | 413 |
| 413 \begin{figure} | 414 \begin{figure} |
| 414 \begin{center} | 415 \begin{center} |
| 415 \input{input/queue-data-flow.tex} | 416 %\input{img/queue-data-flow.eps} |
| 416 \end{center} | 417 \end{center} |
| 417 \caption{Data flow of messages in the queue} | 418 \caption{Data flow of messages in the queue} |
| 418 \label{fig:queue-data-flow} | 419 \label{fig:queue-data-flow} |
| 419 \end{figure} | 420 \end{figure} |
| 420 | 421 |
| 457 | 458 |
| 458 \subsubsection*{Rights and permission} | 459 \subsubsection*{Rights and permission} |
| 459 | 460 |
| 460 The user set required for \qmail\ seems to be too complex. One special user, like \postfix\ uses, is more appropriate. \name{root} privilege and \name{setuid} permission is avoided as much as possible. | 461 The user set required for \qmail\ seems to be too complex. One special user, like \postfix\ uses, is more appropriate. \name{root} privilege and \name{setuid} permission is avoided as much as possible. |
| 461 | 462 |
| 462 Table \ref{tab:new-masqmail-permissions} shows the suggested ownership and permissions of the modules. Figure \ref{fig:new-masqmail-queue} shows the permissions and ownership used for the queue. | 463 Table \ref{tab:new-masqmail-permissions} shows the suggested ownership and permissions of the modules. |
| 463 | 464 |
| 464 \begin{table} | 465 \begin{table} |
| 465 \begin{center} | 466 \begin{center} |
| 466 \input{tbl/new-masqmail-permissions.tbl} | 467 \input{tbl/new-masqmail-permissions.tbl} |
| 467 \end{center} | 468 \end{center} |
| 468 \caption{Ownership and permissions of the modules} | 469 \caption{Ownership and permissions of the modules} |
| 469 \label{tab:new-masqmail-permission} | 470 \label{tab:new-masqmail-permission} |
| 470 \end{table} | 471 \end{table} |
| 471 | 472 |
| 472 \begin{figure} | 473 These are the permissions and ownership used for the queue: |
| 473 \begin{center} | 474 \codeinput{input/new-masqmail-queue.txt} |
| 474 \input{input/new-masqmail-queue.tex} | |
| 475 \end{center} | |
| 476 \caption{Ownership and permissions of the queue} | |
| 477 \label{fig:new-masqmail-queue} | |
| 478 \end{figure} | |
| 479 | 475 |
| 480 | 476 |
| 481 | 477 |
| 482 | 478 |
| 483 | 479 |