Your message dated Mon, 19 Mar 2007 08:35:32 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#412537: exim.8.gz: mention exit status, etc.
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: exim4-base
Version: 4.63-15
Severity: wishlist
File: /usr/share/man/man8/exim.8.gz

Mention EXIT STATUS: when will exim4 return what value to the shell.

Mention that exim's "sendmail -t with no arguments" is not portable, and
what should one use if one wants it also to work on a postfix machine.

Mention how user not in the trusted user list, and hence not able to
use mailq, can get any idea of if there mail was actually sent or not
or stuck etc., yes, when they haven't got an error reply.

P.S., no way to list or reset these:
  Spool file is locked (another process is handling..)
one can merely stare at them in the logfiles.


--- End Message ---
--- Begin Message ---
On Mon, Mar 19, 2007 at 08:24:30AM +0100, Marc Haber wrote:
> On Tue, Feb 27, 2007 at 12:55:53AM +0800, Dan Jacobson wrote:
> > Mention EXIT STATUS: when will exim4 return what value to the shell.

$ man exim | grep 'return code'
Reformatting exim(8), please wait...
                 The return code  is  zero  if  the  message  is  successfully
                 The return code is 0 if no error was detected; it is 1 if one
                 The return code is 2 if any address failed outright; it is  1
                 The return code is 2 if any address failed outright; it is  1
                 receiving process exits with a return code of zero.  If  not,
                 the return code is 2 if the problem is that the original mes-
                 a non-zero return code, whether or not the error message  was
                 standard error file (stderr).  The return code is 1  for  all

Seems as if this is documented for the command line options that
return meaningful return codes. Closing the bug.

Feel free to re-open with an explanation why this is not enough.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835

--- End Message ---

Reply via email to