🚀 go-pugleaf

In article <1993Jan28.004111.11089@cc.gatech.edu> peter@cc.gatech.edu (Peter N. Wan) writes:
>
>Some folks are doing "| if ... ; then ... ; else ... ; fi" and you get
>"sh: syntax error at line 1: `end of file' unexpected" and "unknown
>mailer error 2" messages now (didn't used to before).
>
>I found and disabled "OB." so that the blanks in some of the command
>lines aren't being changed to ".", that seems to have fixed some of the
>problems.

The 'OB.' is the major significant difference from SunOS sendmail where
the prog mailer is concerned.  Both use /bin/sh as the delivery agent.
If removing the blank substitute has any effect, it is only because your
users have incorrectly defined their '.forward' entries.

 Wrong:
	| if ... ; then ... ; else ... ; fi

 Right:
	"| if ... ; then ... ; else ... ; fi"

or, even better:
	|" if ... ; then ... ; else ... ; fi"

That is, the programmatic address should be quoted in '.forward'.  A
program alias typically contains characters which are not permitted in
email addresses unless quoted with double quotes ("..").  Sendmail
removes this set of quotes before feeding the command to /bin/sh.

In article <1993Jan28.010556.11365@cc.gatech.edu> peter@cc.gatech.edu (Peter N. Wan) writes:
>
>I forgot to say that some of the other failures are for scripts that seem
>to silently fail when they executed before; these scripts truncate and open
>files in the user's (mostly locked, 0700 mode) directories.

I can't guess what if anything is happening here.  It is often wiser to
put complex commands into a shell script, and have the shell script invoked
by the alias.

>As far as consistency goes, I am still getting "cannot create output" errors
>for the users who just put a path in their .forward (the path goes into
>locked/secured directories as well).

If this didn't happen with SunOS, then SunOS must have weakened the
standard permissions checking.  If you set the files to mode 4600 you
should alleviate this problem.