source: pkg/security/vinnie/main/exim4/trunk/debian/manpages/exinext.8 @ 7377

Revision 7377, 2.5 KB checked in by alanbach-guest, 3 years ago (diff)
  • Added exim4 to Vinnie security
1.\"                                      Hey, EMACS: -*- nroff -*-
2.\" First parameter, NAME, should be all caps
3.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
4.\" other parameters are allowed: see man(7), man(1)
5.TH EXINEXT 8 "March 26, 2003"
6.\" Please adjust this date whenever revising the manpage.
8.\" Some roff macros, for reference:
9.\" .nh        disable hyphenation
10.\" .hy        enable hyphenation
11.\" .ad l      left justify
12.\" .ad b      justify to both left and right margins
13.\" .nf        disable filling
14.\" .fi        enable filling
15.\" .br        insert line break
16.\" .sp <n>    insert n+1 empty lines
17.\" for manpage-specific macros, see man(7)
18.\" \(oqthis text is enclosed in single quotes\(cq
19.\" \(lqthis text is enclosed in double quotes\(rq
21exinext \- Finding individual retry times
23.B exinext
24.I address|message-id
27A utility called
28.B exinext
29(mostly a Perl script) provides the ability to fish specific information
30out of the retry database.
31Given a mail domain (or a complete address), it looks up the hosts for
32that domain, and outputs any retry information for the hosts or for the
34At present, the retry information is obtained by running
35.B exim_dumpdb
36(see below) and processing the output.
37For example:
39  exinext piglet@milne.fict.example
40  kanga.milne.fict.example: error 146: Connection refused
41    first failed: 21-Feb-1996 14:57:34
42    last tried:   21-Feb-1996 14:57:34
43    next try at:  21-Feb-1996 15:02:34
44  roo.milne.fict.example: error 146: Connection refused
45    first failed: 20-Jan-1996 13:12:08
46    last tried:   21-Feb-1996 11:42:03
47    next try at:  21-Feb-1996 19:42:03
48    past final cutoff time
50You can also give
51.B exinext
52a local part, without a domain, and it will give any retry information for
53that local part in your default domain.
54A message id can be used to obtain retry information pertaining to a
55specific message.
56This exists only when an attempt to deliver a message to a remote host
57suffers a message-specific error (see section 42.2).
58.B exinext
59is not particularly efficient, but then it isn't expected to be run very often.
62This manual page needs a major re-work. If somebody knows better groff
63than us and has more experience in writing manual pages, any patches
64would be greatly appreciated.
67.BR exim (8),
71This manual page was stitched together from spec.txt by
72Andreas Metzler <ametzler at>,
73for the Debian GNU/Linux system (but may be used by others).
Note: See TracBrowser for help on using the repository browser.