[rt-users] Postfix sendmail returning status code 75

Nathan Cutler presnypreklad at gmail.com
Wed Jul 31 06:00:56 EDT 2013

I'm having a devil of a time with this. We're running RT 4.0.13 on
SUSE Linux Enterprise Server 11 SP2. The MTA is Postfix.

Seemingly for no reason, outgoing emails from RT start failing.
Cleaning the Mason cache and restarting Apache2 seems to solve the
problem temporarily (some hours, but by the next morning at the latest
the problem returns).

Each time it drops an email in this way, RT writes the following two
log messages:

RT: <rt-4.0.13-7424-1375250475-1273.35071-4-0 at suse.de>:
`/usr/sbin/sendmail -oi -t` exited with code 75

RT: <rt-4.0.13-7424-1375250475-1273.35071-4-0 at suse.de>: Could not send
mail with command `/usr/sbin/sendmail -oi -t`:
<rt-4.0.13-7424-1375250475-1273.35071-4-0 at suse.de>:
`/usr/sbin/sendmail -oi -t` exited with code 75 at /usr/lib
/perl5/vendor_perl/5.10.0/RT/Interface/Email.pm line 487.  Stack:
7]   [/usr/lib/perl5/vendor_perl/5.10.0/RT/Action/SendEmail.pm:292]
:114]   [/usr/lib/perl5/vendor_perl/5.10.0/RT/ScripAction.pm:232]
[/usr/lib/perl5/vendor_perl/5.10.0/RT/Scrip.pm:475]   [/usr

I have the following options in RT_SiteConfig.pm:

Set($MailCommand, "sendmailpipe");
Set($SendmailArguments, '-oi -t');

I read this thread where someone had a very similar problem:


In their case, adding "PerlOptions +Parent" to their vhost
configuration file solved the problem, but I did that and it doesn't
help in my case.

If I don't restart Apache, the problem seems to get worse over time.

I have prepared a wrapper for sendmail that will log the exact
messages that are causing this to happen, but I haven't deployed it
yet. (Still testing it.)

Since status code 75 is only a temporary error whereby Postfix is
(apparently) just saying that it is queuing the message to send later,
I'm wondering if I could just patch RT to ignore status code 75 and
treat it the same as success?

Any other ideas?


More information about the rt-users mailing list