On Fri, Aug 10, 2012 at 3:40 PM, Wietse Venema <wie...@porcupine.org> wrote:
> Pete:
>> Hi Users,
>>
>> I'm hoping this is an obvious fix, but I don't have too much
>> experience with Postfix so before I change something, I want to ask
>> the experts.
>>
>> I am receiving a SOFTBOUNCE status in my Postfix logs:
>>
>> Aug 10 08:21:22 MyServer postfix/local[28836]: 51FA9285F85:
>> to=<jenkins-mybuild@MyServer>, relay=local, delay=248145,
>> delays=248144/0.01/0/0.24, dsn=4.3.0, status=SOFTBOUNCE (Command died
>> with status 3: "/usr/bin/wget -o /dev/null
>> http://myserver:8080/job/mytest/build";)
>>
>> I have a Jenkins CI software instance running on the same server as
>> Postfix.  I want to "send Jenkins an email" when I want the build to
>> fire, and it works beautifully.  The build fires, no problem.  The
>> issue, I presume, is that the SOFTBOUNCE causes Postfix to attempt to
>
> Have you tried Postfix documentation?  The soft_bounce parameter
> in your main.cf file is documented at:
>
> http://www.postfix.org/postconf.5.html#soft_bounce
>
> As documented this requests that Postfix retries the command instead
> of sending an error report to the sender.
>
>> deliver the message every hour and then five minutes after that, so
>> now my build is running every hour and every sixty-five minutes.  The
>> message states "Command died with status 3" but when I run the command
>> manually, I receive no sign of failure and the build is kicked off as
>> it should.
>
> Apparently, there is a difference between running something by hand
> and running it from a Postfix alias. One difference is that the
> command runs with the permissions the "nobody" user; another
> difference is that the process environment is different; for example,
> the PATH setting is probably not the same as that of your personal
> user account, which may cause some commands to fail.
>
> Command execution is documented at http://www.postfix.org/local.8.html;
> look for the section "SYSTEM-WIDE AND USER-LEVEL ALIASING".
>
>         Wietse

Wietse,

Thanks for pointing me in the right direction.  I used the search from
this page: http://www.postfix.org/documentation.html, which didn't
produce any helpful results, but I think it's because I
narrow-mindedly searched for softbounce, not soft_bounce.  Good point
about the differences in running the command from Postfix.  I would
guess there could be as well, but the trigger works so permissions and
paths shouldn't be the issue, but I'll keep an open mind.  I think
it's how I configured the aliasing and I'll read through your
documentation to try to get a better handle on it.

Best,
Pete

Reply via email to