1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
<!--
$FML: filesystem.sgml,v 1.1 2005/07/23 01:57:38 fukachan Exp $
-->
<sect1 id="troubleshoot.filesystem">
<title>
When The File System Error Ocuurs
</title>
<para>
When the file system error occurs, &fml8; exit abnormally to make MTA
re-deliver the message again to &fml8; or &fml8; re-delivers it by
itself without saving the article on the file system. So &fml8; do not
lost received messages whereas both log or summary file lack
something.
</para>
<para>
Describe below what happans when the file system error occurs in the
delivery process.
</para>
<sect2>
<title>
When Passed From MTA MTA To &fml8;
</title>
<para>
&fml8; reads a message and writes it into the disk once. If succeeded,
it processes more. If failed, &fml8; exits abnormally as
exit(EX_TEMPFAIL) for MTA to re-deliver it. See
<link linkend="message.queue.incoming">
<xref linkend="message.queue.incoming">
</link>
for more details.
</para>
<para>
In this case, incoming message queue may have a incomplete message.
&fml8; tries to remove it in abnormal exit.
Even if failed, the queue management system removes it later.
</para>
</sect2>
<sect2>
<title>
If Updating Of The Article Sequence Number Failed
</title>
<para>
In normal case, &fml8; updates the article sequence number and
re-reads it and compares it again.
If the check fails, &fml8; exit(EX_TEMPFAIL) for MTA to re-deliver it.
</para>
<caution>
<para>
The article sequence number updated. After that, &fml8; does not do
exit(EX_TEMPFAIL) to deliver the message on memory as could as
possible.
</para>
</caution>
</sect2>
<sect2>
<title>
When Saving Of Article Failed
</title>
<caution>
<para>
In this stage, the article sequence has been updated.
</para>
</caution>
<para>
In this case, &fml8; does not create a new article file but the original
message is already on the disk. The header of the article differs from
the original one but the body content is same. So &fml8; tries to
link(2) the original mail in the incoming queue to the article file to
save the content.
<footnote>
<para>
If it could be, it is useful to implement another command which fixes
the article header later. It is not implemented.
</para>
</footnote>
</para>
<para>
&fml8; tries to deliver the message on memory.
</para>
<para>
If the delivery process exits abnormally,
distribution of article ends incompletely
since &fml8; can not use outgoing queue due to file system error.
</para>
</sect2>
<sect2>
<title>
Delivery Process
</title>
<para>
&fml8; saves the message into the outgoing queue, after succeeded, the
delivery process runs.
</para>
<para>
When &fml8; fails to write the outgoing queue,
&fml8; exits incompletely.
</para>
<para>
See
<link linkend="message.queue.outgoing">
<xref linkend="message.queue.outgoing">
</link>
for more details.
</para>
</sect2>
</sect1>
|
