Jerrad Pierce <jpie...@cambridgeenergyalliance.org> writes: > If you're running postfix, and this is a concern, > you can turn errors into soft-bounces for later recovery.
No, because in this case Postfix hasn't got a clue that anything went wrong. Paul is correct - if you do the straightforward thing and use something like :0 * ^X-Spam-Status: YES ! s...@nsc.liu.se :0 | /opt/rt/3.4.4/bin/rt-mailgate --queue nsc-support --action correspond to let procmail filter out spam, your mail will indeed be silently dropped on the floor if rt-mailgate fails - procmail doesn't propagate rt-mailgate's exit code to the MTA by default. This has bitten me. You have to handle this yourself. I don't have the details available right now, but something like :0 * ^X-Spam-Status: YES ! s...@nsc.liu.se :0w | /opt/rt/3.4.4/bin/rt-mailgate --queue nsc-support --action correspond # if procmail has reached here, delivery has failed. return with a # temporary failure code from <sysexits.h>. # 75 = EX_TEMPFAIL EXITCODE=75 :0 /dev/null should do the trick. (Please note that the above snippet is untested, though.) -- Leif Nixon - Systems expert ------------------------------------------------------------ National Supercomputer Centre - Linkoping University ------------------------------------------------------------ _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
