The exit status is zero.
It looks like 'deliver' really believes that it's inserting the message into
the folder.
If I run deliver -m user.test, then it lets me type into stdin, and when I
hit Ctrl-D, it promptly quits and leaves an exit status of 0.
If I run deliver -m user.test2 (a non-existent user), then it doesn't wait
for stdin, but simply dies. The strange thing is that the exit code is
still 0.
The strangest thing is that if I run deliver -m user.elirov, it gives a
segmentation fault and returns an exit code of 139.
There is nothing special about user.elirov. It doesn't happen on
user.elirov2, but it does happen on user.oawuhf. (just a random string I
happend to type in... user.oawuhfe doesn't dump core)
???
> -----Original Message-----
> From: Lawrence Greenfield [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 22, 2001 8:05 PM
> To: Erez Lirov
> Cc: [EMAIL PROTECTED]
> Subject: Re: LMTP problem
>
>
> From: "Erez Lirov" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Date: Thu, 22 Feb 2001 18:31:33 -0500
>
> I see. Does the deliver program form RFC822 content from a
> plain text file?
> As in:
> deliver -m user.test < mymessage.txt
>
> When I try this, it doesn't give me any errors, but it doesn't
> put anything
> in the user.test mailbox.
>
> When you say no errors, are you including the exit code? The
> important error that deliver gives is the exit code --- 0 is success,
> and all others are a la /usr/include/sysexits.h.
>
> That's the only important measure of whether deliver thinks it's
> succeeding or failing.
>
> Larry
>
