On Thu, 5 Dec 1996, Bruce Rodger wrote:
> If a user has a .forward file which contains something like
>
> |/some/file/which/does/not/exist
>
> the message disappears into a black hole....
Hmm. Yes, it would.
> If you remove ignore_status, messages get frozen.
Are you sure? That doesn't happen for me. I get
** |/some/non/exist/file <ph10@???> D=userforward
T=address_pipe: Child process of address_pipe transport returned 2 for
command /some/non/exist/file
on the log. True, it then tries to generate a delivery failure:
<= <> R=0vVxb9-0000pi-00 U=exim P=local S=1328
Error message sent to Philip.Hazel@???
and *this* gets frozen because it was also addressed to me....
** |/some/non/exist/file <ph10@???> D=userforward
T=address_pipe: Child process of address_pipe transport returned 2 for
command /some/non/exist/file
Frozen (delivery error message)
... but if the message had been from some other user a failure report
would have gone back. Are you seeing different behaviour from this? If
so, I'll need more information to diagnose it.
> Any suggestions/comments? Is this a sensible behaviour? would returning the
> message to the sender make more sense?
It is supposed to return the message to the sender if ignore_status is
not set. (But the possibility of bugs is never zero...)
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
