version 1, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
exim_db |
|
|
2 |
!!!exim_db |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
SEE ALSO |
|
|
7 |
AUTHOR |
|
|
8 |
---- |
|
|
9 |
!!NAME |
|
|
10 |
|
|
|
11 |
|
|
|
12 |
exim_db - program to maintain exim mailer hint databases |
|
|
13 |
!!SYNOPSIS |
|
|
14 |
|
|
|
15 |
|
|
|
16 |
__exim_dumpdb__ ''spooldir database]''__ |
|
|
17 |
exim_tidydb__ ''[[-t time] [[-f] spooldir |
|
|
18 |
database''__ |
|
|
19 |
exim_fixdb__ ''spooldir database'' |
|
|
20 |
!!DESCRIPTION |
|
|
21 |
|
|
|
22 |
|
|
|
23 |
Three utility programs are provided for maintaining the DBM |
|
|
24 |
files that Exim uses to contain its delivery hint |
|
|
25 |
information. Each program requires two arguments. The first |
|
|
26 |
specifies the name of Exim's spool directory, and the second |
|
|
27 |
is the name of the database it is to operate on. These are |
|
|
28 |
as follows: |
|
|
29 |
|
|
|
30 |
|
|
|
31 |
__retry__ |
|
|
32 |
|
|
|
33 |
|
|
|
34 |
the database of retry information |
|
|
35 |
|
|
|
36 |
|
|
|
37 |
__reject__ |
|
|
38 |
|
|
|
39 |
|
|
|
40 |
the database of information about rejected |
|
|
41 |
messages |
|
|
42 |
|
|
|
43 |
|
|
|
44 |
__wait-smtp__ |
|
|
45 |
|
|
|
46 |
|
|
|
47 |
the database of information about messages waiting for SMTP |
|
|
48 |
hosts |
|
|
49 |
|
|
|
50 |
|
|
|
51 |
__serialize-smtp__ |
|
|
52 |
|
|
|
53 |
|
|
|
54 |
the database of information about current connections to |
|
|
55 |
hosts which are restricted to one connection at |
|
|
56 |
once |
|
|
57 |
|
|
|
58 |
|
|
|
59 |
The entire contents of a database are written to the |
|
|
60 |
standard output by the __exim_dumpdb__ program, which has |
|
|
61 |
no options or arguments other than the spool and database |
|
|
62 |
names. For example, to dump the retry database: |
|
|
63 |
|
|
|
64 |
|
|
|
65 |
''exim_dumpdb /var/spool/exim retry'' |
|
|
66 |
|
|
|
67 |
|
|
|
68 |
Two lines of output are produced for each |
|
|
69 |
entry: |
|
|
70 |
|
|
|
71 |
|
|
|
72 |
T:mail.ref.book:242.242.242.242 146 77 Connection refused |
|
|
73 |
31-Oct-1995 12:00:12 02-Nov-1995 12:21:39 02-Nov-1995 20:21:39 * |
|
|
74 |
The first item on the first line is the key of the record. It starts with one of the letters D, R, or T, depending on whether it refers to a directing, routing, or transport retry. For a local delivery, the next part is the local address; for a remote delivery it is the name of the remote host, followed by its failing IP address. Then there follows an error code, an additional error code, and a textual description of the error. |
|
|
75 |
|
|
|
76 |
|
|
|
77 |
The three times on the second line are the time of first |
|
|
78 |
failure, the time of the last delivery attempt, and the |
|
|
79 |
computed time for the next attempt. The line ends with an |
|
|
80 |
asterisk if the cutoff time for the last retry rule has been |
|
|
81 |
exceeded. |
|
|
82 |
|
|
|
83 |
|
|
|
84 |
Each output line from exim_dumpdb for the reject database |
|
|
85 |
consists of a date and time, followed by the letter T or F, |
|
|
86 |
followed by the address that was rejected, followed by the |
|
|
87 |
name of the host that sent the bad address (as given in the |
|
|
88 |
SMTP HELO command). The letter is F if only one previous |
|
|
89 |
rejection of this address has been done recently, and T if a |
|
|
90 |
second has occurred, causing rejection of the MAIL FROM |
|
|
91 |
command, and subsequently rejection of the RCPT TO |
|
|
92 |
commands. |
|
|
93 |
|
|
|
94 |
|
|
|
95 |
Each output line from __exim_dumpdb__ for the |
|
|
96 |
''wait-smtp'' database consists of a host name followed |
|
|
97 |
by a list of ids for messages that are or were waiting to be |
|
|
98 |
delivered to that host. If there are a very large number for |
|
|
99 |
any one host, continuation records, with a sequence number |
|
|
100 |
added to the host name, may be seen. The data in these |
|
|
101 |
records is often out of date, because a message may be |
|
|
102 |
routed to several alternative hosts, and Exim makes no |
|
|
103 |
effort to keep cross references. |
|
|
104 |
|
|
|
105 |
|
|
|
106 |
Each output line from __exim_dumpdb__ for the |
|
|
107 |
serialize-wmtp database consists of a host name preceded by |
|
|
108 |
the time that Exim made a connection to that host. Exim |
|
|
109 |
keeps track of connections only for those hosts or networks |
|
|
110 |
that have been configured for serialization. |
|
|
111 |
|
|
|
112 |
|
|
|
113 |
The __exim_tidydb__ utility program is used to tidy up |
|
|
114 |
the contents of the databases. If run with no options, it |
|
|
115 |
removes all records from a database that are more than 30 |
|
|
116 |
days old. The cutoff date can be altered by means of the |
|
|
117 |
__-t__ option, which must be followed by a time. For |
|
|
118 |
example, to remove all records older than a week from the |
|
|
119 |
retry database: |
|
|
120 |
|
|
|
121 |
|
|
|
122 |
''exim_tidydb -t 7d /var/spool/exim retry'' |
|
|
123 |
|
|
|
124 |
|
|
|
125 |
For the ''wait-smtp database'' , the __-f__ option can |
|
|
126 |
also be used (it has no effect for other databases). This |
|
|
127 |
causes a check to be made to ensure that message ids in |
|
|
128 |
database records are those of messages that are still on the |
|
|
129 |
queue. Other message ids are removed, and if this leaves |
|
|
130 |
records empty, they are also removed. |
|
|
131 |
|
|
|
132 |
|
|
|
133 |
The __exim_tidydb__ utility outputs comments on the |
|
|
134 |
standard output whenever it removes information from the |
|
|
135 |
database. It is suggested that it be run periodically on all |
|
|
136 |
three databases, but at a quiet time of day, since it |
|
|
137 |
requires a database to be locked (and therefore inaccessible |
|
|
138 |
to Exim) while it does its work. |
|
|
139 |
|
|
|
140 |
|
|
|
141 |
The __exim_fixdb__ program is a utility for interactively |
|
|
142 |
modifying databases. Its main use is for testing Exim, but |
|
|
143 |
it might also be occasionally useful for getting round |
|
|
144 |
problems in a live system. It has no options, and its |
|
|
145 |
interface is somewhat crude. On entry, it prompts for input |
|
|
146 |
with a |
|
|
147 |
__ |
|
|
148 |
|
|
|
149 |
|
|
|
150 |
If 'd' is typed at the next prompt, the entire record is |
|
|
151 |
deleted. For the ''reject, wait-smtp,'' and |
|
|
152 |
''serialize-smtp'' databases, that is the only operation |
|
|
153 |
that can be carried out. For the retry database, each field |
|
|
154 |
is output preceded by a number, and data for individual |
|
|
155 |
fields can be changed by typing the field number followed by |
|
|
156 |
new data, for example: |
|
|
157 |
|
|
|
158 |
|
|
|
159 |
|
|
|
160 |
|
|
|
161 |
resets the time of the next delivery attempt. Time values |
|
|
162 |
are given as a sequence of digit pairs for year, month, day, |
|
|
163 |
hour, and minute. Colons can be used as optional |
|
|
164 |
separators. |
|
|
165 |
!!SEE ALSO |
|
|
166 |
|
|
|
167 |
|
|
|
168 |
There is extensive documentation available in |
|
|
169 |
''/usr/share/doc/exim'' and in the info system regarding |
|
|
170 |
exim. Please be sure to have the __exim-doc__ package |
|
|
171 |
installed. |
|
|
172 |
!!AUTHOR |
|
|
173 |
|
|
|
174 |
|
|
|
175 |
This manual page was stitched together by Christoph Lameter |
|
|
176 |
---- |