Charles Sprickman:
> I think that as long as the script returns the appropriate error
> code on failure you don't have to do anything special; from pipe(8):
>
> In the case of a non-zero exit status, a limited amount of command
> output is logged, and reported in a delivery status notification. When
> the output begins with a 4.X.X or 5.X.X enhanced status code, the
> status code takes precedence over the non-zero exit status (Postfix
> version 2.3 and later).
The expected status codes may be found in /usr/include/sysexits.h.
The text belw shows what they might look like.
Postfix converts these into an appropeiate 4.X.X or 5.X.X enhanced
status code and text, if the command output does not specify one.
Wietse
#define EX_USAGE 64 /* command line usage error */
#define EX_DATAERR 65 /* data format error */
#define EX_NOINPUT 66 /* cannot open input */
#define EX_NOUSER 67 /* addressee unknown */
#define EX_NOHOST 68 /* host name unknown */
#define EX_UNAVAILABLE 69 /* service unavailable */
#define EX_SOFTWARE 70 /* internal software error */
#define EX_OSERR 71 /* system error (e.g., can't fork) */
#define EX_OSFILE 72 /* critical OS file missing */
#define EX_CANTCREAT 73 /* can't create (user) output file */
#define EX_IOERR 74 /* input/output error */
#define EX_TEMPFAIL 75 /* temp failure; user is invited to retry */
#define EX_PROTOCOL 76 /* remote error in protocol */
#define EX_NOPERM 77 /* permission denied */
#define EX_CONFIG 78 /* configuration error */
> Charles
>
> > On Oct 2, 2022, at 6:33 PM, Dan Mahoney <d...@prime.gushi.org> wrote:
> >
> > Hello all,
> >
> > If I am piping my mail to a program (in this case, day job's RT install),
> > is there some way in which I can exit that will cause a message to be
> > bounced back to the sender?
> >
> > Or do I need a full-on milter to do this kind of rejection?
> >
> > -Dan
>
-- End of PGP section, PGP failed!
