[rt-users] Postfix sendmail returning status code 75
falcone at bestpractical.com
Wed Jul 31 12:10:00 EDT 2013
On Wed, Jul 31, 2013 at 12:00:56PM +0200, Nathan Cutler wrote:
> 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).
What kind of monitoring do you have on the box? Often, this is a
memory problem (the running out kind).
> 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
> 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.
PerlOptions +Parent was required because they ran two perl processes
in a single mod_perl host. Are you doing that?
> 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?
What's in your postfix error logs when this happens?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 235 bytes
Desc: not available
More information about the rt-users