From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031101 Firebird/0.7+ Description of problem: A bug was introduced in version 2.0.11 of postfix and fixed in version 2.0.12. The description of the fix is: Bugfix: the stricter postdrop input filter broke "sendmail -bs". Found by Lutz Jaenicke. File: smtpd/smtpd.c. This bug manifests itself with the error message fatal: uid=XXX: unexpected record type: 84 and the refusal to send the message. The problem is in the interaction between smtpd and postdrop, both of which are started by sendmail. Smtpd sends a timestamp to postdrop which postdrop doesn't expect. Postdrop then produces the error message and exits. Please update postfix to a newer version. Version-Release number of selected component (if applicable): 2.0.11-5 How reproducible: Always Steps to Reproduce: 1.Send a message with MH or pine configured to use the local postfix installation. 2. 3. Additional info:
yes, I'm seeing this too. :( also reproducible by using the same protocol as nmh's "post" command, as follows (SMTP commands are me btw): $ /usr/lib/sendmail -bs -odb -oem -om 220 jmason.org ESMTP Postfix MAIL FROM:<jm> 250 Ok RCPT TO:<jm.org> 250 Ok DATA From: <jm> To: <jm.org> Subject: tseting foo . 354 End data with <CR><LF>.<CR><LF> postdrop: fatal: uid=500: unexpected record type: 84 451 Error: queue file write error QUIT 221 Bye $
oh, btw, come to think of it I may have set up the /usr/lib/sendmail symlink myself. It's a symlink to /etc/alternatives/mta, identical to /usr/sbin/sendmail.
I have built a new rpm from the 2.0.16 postfix source, I have not the opportunity to test it because of other demands and I don't want this to drag out, I'm sorry. To expedite the update process I would encourage those of you with an interest in this bug to try testing the following rpm and give me some feedback ftp://people.redhat.com/jdennis/postfix-2.0.16-1.i386.rpm Thanks, John
I can't install this rpm because it depends on libcom_err.so.3 which I don't have installed and can't find on the Fedora Core 1 CDs.
Me too, I'm afraid.
I rebuilt the rpm using the official fedora environment and replaced it on the ftp site, this should resolve the dependency problem you encountered. Give it a go, my apologies for a false start.
This seems to fix the bug.
yep, works for me too. thanks!
Thank you Sjoerd and Justin! Your help is appreciated. I am going to close the bug and push the new package through the fedora update process.
*** Bug 110671 has been marked as a duplicate of this bug. ***