Bug 52255 - rawhide pine does not work with sendmail
Summary: rawhide pine does not work with sendmail
Status: CLOSED DUPLICATE of bug 52226
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pine
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-22 01:52 UTC by Stephen John Smoogen
Modified: 2007-04-18 16:36 UTC (History)
0 users

Clone Of:
Last Closed: 2001-08-22 01:52:46 UTC

Attachments (Terms of Use)

Description Stephen John Smoogen 2001-08-22 01:52:42 UTC
Description of Problem:

In trying to test if certain patches had made it in, I upgraded this
evening to various RPMs out of this mornings rawhide. After doing so, pine
no longer would send email. It would begin to do so say [Sending mail 0%]
and then stop.. looking at gdb it was just sitting waiting for sendmail to
do something. Looking at the changelog I am guessing that this is the cause
of it:

* Thu Aug 16 2001 Mike A. Harris <mharris@redhat.com> 4.33-14

- Created sendmail-options patch to remove "-bs", and add "-t -oi"
  to sendmail invocation options.  This gets rid of sendmail complaints
  in maillog of "process foo invoked sendmail with -bs".

Looked in maillog and messages and dont see any errors. I have worked
around the problem by either changing the .pinerc to use the local smtp MX
box.. or to put the line 

sendmail-path=/usr/lib/sendmail -oem -t -oi

which causes sendmail to not hang but also not queue :)

I set up a dummy user to see if it was my .pinerc, but I was able to
replicate it there.

Version-Release number of selected component (if applicable):


Comment 1 Mike A. Harris 2001-08-22 02:19:51 UTC
Filed by Trond, fixed not long after in -15.  I guess you must have
missed that one when you queried bugzilla for already reported and/or
resolved bugs tho...  ;o)  Could happen to anyone...  ;o)


*** This bug has been marked as a duplicate of 52226 ***

Note You need to log in before you can comment on or make changes to this bug.