[rt-users] Mail suddenly quit -- Email.pm line 405 -- sendmailpipe

[Brian Lawson]

Well in my RT_Config.pm, both $MailCommand and $SendmailPath are set to
sendmailpipe.  I set the $MailCommand in the RT_SiteConfig.pm to be
sendmail and it worked, but I did not set $SendmailPath.  Should they
both be set to the same value? They were both set to the sendmailpipe
when it stopped working.  The documentation in the RT_Config.pm file is
terse in my opinion and doesn't explain how sendmailpipe actually works.

-Brian

-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Kevin
Falcone
Sent: Friday, March 26, 2010 10:19 AM
To: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Mail suddenly quit -- Email.pm line 405 --
sendmailpipe

On Fri, Mar 26, 2010 at 08:21:36AM -0500, Brian Lawson wrote:
> Kevin,
> 
> I didn't change the SendMailPath.  Ahhh.  That might be a problem.  I
> just looked in my RT_Config.pm file (because SendMailPath is not set
in
> RT_SiteConfig.pm) and it has the following: "Set($SendmailPath,
> 'sendmailpipe');"  Since this is case sensitive and the 'm' in 'mail'
is
> lower case, that might be the problem. Correct?

Having SendmailPath set to something other than a path to a sendmail
binary is almost certainly causing errors.
You seem to be confusing SendmailPath and MailCommand, I suggest
reviewing their docs in RT_Congif.pm

-kevin

> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Kevin
> Falcone
> Sent: Thursday, March 25, 2010 1:22 PM
> To: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Mail suddenly quit -- Email.pm line 405 --
> sendmailpipe
> 
> On Thu, Mar 25, 2010 at 11:55:14AM -0500, Brian Lawson wrote:
> >    I got it working by changing sendmailpipe to just sendmail and
> removing the "-t" option on the
> >    commands, but I still want to understand why it quit all of a
> sudden.
> 
> You don't say what version you're running, but most likely your
> SendmailPath was wrong.  sendmailpipe is not a program, but instead it
> tells RT to open a pipe to the sendmail command.
> 
> -kevin
> 
> 
> 
> > 
> >
>
------------------------------------------------------------------------
> ----------------------
> > 
> >    From: rt-users-bounces at lists.bestpractical.com
> >    [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of
> Brian Lawson
> >    Sent: Thursday, March 25, 2010 9:01 AM
> >    To: rt-users at lists.bestpractical.com
> >    Subject: [rt-users] Mail suddenly quit -- Email.pm line 405 --
> sendmailpipe
> > 
> > 
> > 
> >    Newbie here.
> > 
> > 
> > 
> >    I have not changed anything in the RT_Config.pm and
> RT_SiteConfig.pm does not remap
> >    $MailCommand to anything else.
> > 
> >    Suddenly today I see the following message in the syslog:
> > 
> > 
> > 
> >    Mar 25 08:38:28 helpdesk RT: Can't exec "sendmailpipe": No such
> file or directory at
> >    /opt/rt3/bin/../lib/RT/Interface/Email.pm line 405.
> >    (/opt/rt3/bin/../lib/RT/Interface/Email.pm:405)
> > 
> > 
> > 
> >    I have not been able to find the sendmailpipe executable, and do
> not know where it was
> >    previously.
> > 
> > 
> > 
> >    Can anyone help?
> > 
> >    This communication, together with any attachments hereto or links
> contained herein, is for the
> >    sole use of the intended recipient(s) and may contain information
> that is confidential or
> >    legally protected. If you are not the intended recipient, you are
> hereby notified that any
> >    review, disclosure, copying, dissemination, distribution or use
of
> this communication is
> >    STRICTLY PROHIBITED. If you have received this communication in
> error, please notify the
> >    sender immediately by return e-mail message and delete the
original
> and all copies of the
> >    communication, along with any attachments hereto or links herein,
> from your system.
> > 
> >    This communication, together with any attachments hereto or links
> contained herein, is for the
> >    sole use of the intended recipient(s) and may contain information
> that is confidential or
> >    legally protected. If you are not the intended recipient, you are
> hereby notified that any
> >    review, disclosure, copying, dissemination, distribution or use
of
> this communication is
> >    STRICTLY PROHIBITED. If you have received this communication in
> error, please notify the
> >    sender immediately by return e-mail message and delete the
original
> and all copies of the
> >    communication, along with any attachments hereto or links herein,
> from your system.
> 
> > 
> > Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> > Buy a copy at http://rtbook.bestpractical.com
> 
> 
> This communication, together with any attachments hereto or links
contained herein, is for the sole use of the intended recipient(s) and
may contain information that is confidential or legally protected. If
you are not the intended recipient, you are hereby notified that any
review, disclosure, copying, dissemination, distribution or use of this
communication is STRICTLY PROHIBITED. If you have received this
communication in error, please notify the sender immediately by return
e-mail message and delete the original and all copies of the
communication, along with any attachments hereto or links herein, from
your system.
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com

This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system.