Bug 79617 - binary dist: sendmail component wrong version
binary dist: sendmail component wrong version
Product: Red Hat Linux
Classification: Retired
Component: postfix (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: John Dennis
Depends On:
  Show dependency treegraph
Reported: 2002-12-13 20:02 EST by Stephen Satchell
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-12 15:21:38 EDT
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 Stephen Satchell 2002-12-13 20:02:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1) Gecko/20020826

Description of problem:
In the binary RPM file postfix-1.1.7-2.i386.rpm an incorrect, out-of-date
version of the "sendmail" binary was built into the RPM.  This results in a
number of rather scary error messages being inserted into /var/log/maillog, but
does not seem to affect mail transport.

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

How reproducible:

Steps to Reproduce:
1. Install binary postfix RPM
2. type "mail <external-mail-address>"
3. type a message, follow with "." on a line by itself.
4. hit CR at the Cc: prompt.
5. watch the messages come on the screen, and look in /var/log/maillog

Actual Results:  Got either one or two error messages: "mail_scan_int: bad
integer: status" and "fatal: root(0): Error writing message file".  The mail
message, however, is sent to its final destination

Expected Results:  ship the message without the bogus complaints.

Additional info: Reproduced on multiple systems, including a laptop system,
running Red Hat 7.3.
Comment 1 John Dennis 2003-06-12 15:21:38 EDT
the postfix rpm's have been significantly updated since this was reported, in a
few days postfix-2.0.11 should appear in rawhide. I don't believe this to be a
problem anymore, at least as of postfix-2.0.6.

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