procmail
[Top] [All Lists]

Re: Non-zero exitcode (153)

2000-10-23 10:46:44
Chuck Mead wrote:
I am seeing some odd behavior with formail... here is some log output:
...
procmail: Non-zero exitcode (153) from " $FORMAIL -A"X-Sorted: Bulk" >>$INET"

Chuck, I'm going to steal something David wrote last week.

| From: "David W. Tamkin" <dattier(_at_)ripco(_dot_)com>
| Subject: Re: vacation problems..sigh
| Date: Wed, 18 Oct 2000 12:28:38 -0500 (CDT)
| Message-Id: <200010181728(_dot_)e9IHScS05937(_at_)ripco(_dot_)com>
| [...]
| The usual reason that shell calls from a procmail rcfile bomb is that the
| person has not set SHELL so procmail looks up the login shell for that user
| and it is one that uses an initialization file; or the person, used to
| his/her login shell, has explicitly set SHELL to it.  Then the initialization
| file (~/.cshrc or ~/.bashrc or whatever) includes some code that depends on
| being connected to a terminal or on the user's being actively logged in.

I don't know if this is the reason behind your problem, but the blank
between the '"' and the '$FORMAIL' suggests to me that a shell was
invoked (maybe because of the sequence '>>$' on that line).

One way to check this would be to make sure formail is in your path
and change the recipe from 

  | $FORMAIL ... >>$INET

to 

  | formail ... >> $INET

which I *think* will skip invoking the shell.  I think David's
suggested fix is better though:

| The solutions are to set SHELL to /bin/sh, which doesn't use such a file; to
| remove terminal-dependent code from the shell initialization file and put it
| into .login or .profile instead; or to wrap all terminal-dependent code in
| the initialization file in an if or case structure that allows it to run only
| on interactive shells.  ...

Jari suggests always using /bin/sh:

    6.4 Always set SHELL and PATH variables [toc]

         [faq] If your login shell is a C shell (csh or tcsh), prepare for
         havoc As a precaution, always put following to the top of your
         .procmailrc.

              SHELL = /bin/sh

See Jari's tips at

    http://www.procmail.org/jari/pm-tips.html

if the server will let you in (it's rather busy at the moment)

hth
-- 
Neither I nor my employer will accept any liability for any problems
or consequential loss caused by relying on this information.  Sorry.
Collin Park                         Not a statement of my employer.

_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>