Bug 117747 - sendmail.postfix and postdrop don't match. "fatal: uid=1241: unexpected record type: 84"
sendmail.postfix and postdrop don't match. "fatal: uid=1241: unexpected recor...
Status: CLOSED NEXTRELEASE
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: postfix (Show other bugs)
3.0
i686 Linux
medium Severity high
: ---
: ---
Assigned To: John Dennis
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-03-07 23:03 EST by Need Real Name
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-03-08 12:40:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2004-03-07 23:03:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
It's know issue of postfix-2.0.11 (pls. refer to
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=108960)

But RHEL-AS-3 doesn't seem to have an updated version of postfix yet.

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

How reproducible:
Always

Steps to Reproduce:
1.install postfix
2.pine
3.
    

Additional info:
Comment 1 John Dennis 2004-03-08 12:40:46 EST
RHEL3 Update 2 will contain a new postfix rpm with the fix. An errata
(RHBA-2003:409-02) was filed for RHEL3. In the interim you may pick up
a new postfix rpm from:

ftp://people.redhat.com/jdennis

I hope this helps.

John
Comment 2 Petri T. Koistinen 2004-05-11 11:07:41 EDT
When RHEL3 Update 2 is availble, is there some schedule or is it secret?
Comment 3 John Dennis 2004-05-11 11:24:39 EDT
RHEL3 U2 is supposed to go live today on RHN at noon EDT but par for
the course there are some unexpected complications and may be delayed
a little bit, short answer "real soon now" :-)

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