Bug 78956 - Sendmail fails to work if started by postfix
Sendmail fails to work if started by postfix
Product: Red Hat Linux
Classification: Retired
Component: postfix (Show other bugs)
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: wdovlrrw
Depends On:
  Show dependency treegraph
Reported: 2002-12-03 17:41 EST by Karl F. Larsen
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-03 17:41:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Karl F. Larsen 2002-12-03 17:41:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
When I boot up the computer it comes up normal but sendmail does not work for
e-mail. Trying to test a new rpm of sendmail I got it started working properly.
Later I discovered any rpm of senmail works if I start it manually after booting up.

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

How reproducible:

Steps to Reproduce:
1.Boot up the computer
2.Send an e-mail
3.use #sendmail -q to send the e-mail

Actual Results:  The manual #sendmail -q does send out all the stored mail.

Expected Results:  Sendmail should send out any mail it gets.

Additional info:
Comment 1 Karl F. Larsen 2002-12-04 17:12:11 EST
        It is now apparent that there is nothing wrong with Sendmail or
Postfix. What is wrong is my inability to understand either system. This is
compounded by the Red Hat manuals which are mutually counter-dict-ave. The
Mail Transport Agent Switcher does not work as shown in the manual. When I
use #/sbin/service postfix stop it fails. I'm convinced that some
interaction between postfix and sendmail account for my problem. I have
wasted 3 days of work trying to fix this problem and must now just quit.

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