Is anyone using postfix and pine??

[Sjoerd Mullender]

Tom Diehl wrote:
> Hi, 
> I am trying to get postfix and pine working together using the postfix
> rpm that comes with severn and Mike Harris's pine rpm. I can send a message
> from the command line just fine but if I try to use pine it will not send.
> I get the following in the logs:
> 
> Nov  3 00:33:53 tigger postfix/smtpd[2143]: connect from localhost[127.0.0.1]
> Nov  3 00:33:53 tigger postfix/smtpd[2143]: 761723CC2: client=localhost[127.0.0.1]
> Nov  3 00:33:53 tigger postfix/postdrop[2144]: fatal: uid=508: unexpected record type: 84
> Nov  3 00:33:54 tigger postfix/smtpd[2143]: warning: premature end-of-input on /usr/sbin/postdrop while reading input attribute name
> Nov  3 00:35:13 tigger postfix/smtpd[2042]: > localhost[127.0.0.1]: 421 Error: timeout exceeded
> Nov  3 00:35:14 tigger postfix/smtpd[2042]: vstream_fflush_some: fd 1 flush 29
> Nov  3 00:35:14 tigger postfix/smtpd[2042]: timeout after MAIL from localhost[127.0.0.1]
> Nov  3 00:35:14 tigger postfix/smtpd[2042]: vstream_fflush_some: fd 1 flush 0
> Nov  3 00:35:14 tigger postfix/smtpd[2042]: vstream_fflush_some: fd 5 flush 33
> Nov  3 00:35:14 tigger postfix/postdrop[2043]: fatal: uid=508: unexpected record type: 84
> Nov  3 00:35:14 tigger postfix/postdrop[2043]: remove maildrop/4E3623CC0
> Nov  3 00:35:15 tigger postfix/smtpd[2042]: disconnect from localhost[127.0.0.1]
> 
> Google says that sendmail and postdrop binaries are from different postfix versions
> but I rm'd the postfix rpm and reinstalled it. My pine config file is the same one
> I have been using for a couple of years. It works fine on 8.0.
> 
> Anyone else tried this??

I have the same problem with postfix and MH.

After some searching I finally found the answer.  Fedora Core comes with 
postfix 2.0.11.  In the HISTORY entry for version 2.0.12 there is the 
remark:

       Bugfix: the stricter postdrop input filter broke "sendmail
       -bs". Found by Lutz Jaenicke. File: smtpd/smtpd.c.

and this is exactly the problem.

In other words, if Fedora Core were to upgrade the postfix release to 
anything newer than 2.0.11 the bug would disappear.  The current release 
is 2.0.16.

This particular problem was actually introduced in 2.0.11...