It is chrooted, but when I s/-/n for all the chrooted processes in master.cf and restarted postfix, it didn’t make any difference. I just swapped the original master.cf back in.
I’ll update to add that my aliases were quoted incorrectly to begin with, and having changed that, the full error output now reads:
Command died with status 126: "/opt/rt4/bin/rt-mailgate --queue 'Network Support' --action correspond --url http://rt.ifworld.com". Command output: sh: 1: /opt/rt4/bin/rt-mailgate: Permission deniedOn Tue, Jun 16, 2015 at 12:39:15PM -0700, Aaron C. de Bruyn wrote:
AppArmor? (Or is that just Ubuntu?)
Also, is the postfix process running in a chroot?
Check /etc/postfix/master.cf to see if the service that is doing the
rt-mailgate delivery has a ‘y’ in the chroot column.
On Tue, Jun 16, 2015 at 12:29 PM, Jeff Melton firstname.lastname@example.org wrote:
It’s Debian Wheezy. No SELinux in this case.
On Tue, Jun 16, 2015 at 09:25:02PM +0200, Joop wrote:
On 16-6-2015 17:33, Jeff Melton wrote:
I’m setting up a new RT server, and I’m having some trouble getting
rt-mailgate to accept email piped from postfix.
Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate: Permission denied
You don’t state which OS you’re using but if you’re using CentOS/Rhel
base/derived you could be facing a SELinux problem. Check
/var/log/messages /var/log/audit or see what happens if you run