I got the Postfix-2.2.2-2 SRPM from the fedora Core 4 repositories and compiled
it on my machine.  That solved the problem.  I haven't had a crash since.

I am also having this same problem with 2.1.5-4.2.RHEL4 on RHEL 4 2.6.9-11.ELsmp
x86_64. I also downloaded postfix-2.2.2-2.src.rpm for Fedora Core 4, but it
won't install. This is what I get when I try to install:
# rpm -i postfix-2.2.2-2.src.rpm
warning: postfix-2.2.2-2.src.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2

The package does not get installed.

When is the 2.1.5 package going to get fixed?

Cory,

You might want to --force it or install the key from fedora into your rpm.  It
looks like it is just complaining because it can't verify the package.

Thanks Shane, I ran rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora to import the
Fedora GPG key. I'm pretty sure it worked without it, I just didn't realize that
it was putting the files in /usr/src/redhat/SOURCES, until I turned up the
verbosity of rpm (-vv).

A working Postfix would have been easier.

Ok, here is what I should know:

1) Is tls used?
2) Is ipv6 in use?
3) If not, is the package working without the additional ipv6 and tls patches
for the customer?
4) Is there a test case? I was not able to reproduce the problem for my own.

Thomas,  thanks for looking into this. To answer your questions.

1. TLS.  Yes, it was used and configured
2. IPv6. It was probably patched for IPv6, but I did not employ it.
3. I did not check the postfix program without the tls and ipv6 patches.
4. This whole bug is kind of a moot point for me right now as the server that
was having the problem has been fixed by installing the FC4 postfix as mentioned
above.  I do not have another server like it to use as a test machine.  This is
a production server.

I assume that a bug like this is hard to track down.  This issue has been solved
for me, so I have no objections to closing this bug.

Thomas, I'm still seeing this problem with 2.1.5-4.2.RHEL4 on at least one host
x86_64. I need to get this fixed, but I want to get a patch, too.

1) Is tls used?
No
2) Is ipv6 in use?
No
3) If not, is the package working without the additional ipv6 and tls patches
for the customer?
No
4) Is there a test case? I was not able to reproduce the problem for my own.
The problem appears to occur whenever we sent a lot of mail. On one host, were
we are sending out bursts of about 20K of messages several times a day, we are
seeing at least two "warning: process /usr/libexec/postfix/smtp pid 9709 killed
by signal 6" messages per mailing.

I'm also seeing tens of thousands of these messages daily "status=deferred
(delivery temporarily suspended: unknown mail transport error)." This appears to
be related, because the other server that shares the mail load, and is running
postfix-2.2.2-2.src.rpm, isn't logging these errors.

Please let me know ASAP what other info you need. 

Is it likely that we'll see an upgrade to the postfix package from fedora core 4
for update 3?

I'm curious b/c I'm seeing the same segfaults on two boxes and I'd like it to go
away. :)

RHEL's postfix-2.2.2 continues to carry this bug for systems that deliver a lot
of messages. I suggest that you use Fedora's postfix-2.2.2-2.src.rpm (or later)
for a reliable version of Postfix on RHEL.

The postfix version in RHEL-4-4 is 2.2.10 and not 2.2.2.

Please verify with postfix-2.2.10.

Sorry, another admin gave me the wrong version information. I have done a lot
more digging to find out why the problem was suddenly so much worse today. What
I found is that we were running postfix-2.1.5-4.2.RHEL4 until yesterday, when
up2date automatically installed postfix-2.1.5-4.2.RHEL4. Stopping and starting
all instances of Postfix resolved the error messages (below).

grep postfix /var/log/up2date:
up2date:[Wed Sep 13 16:18:04 2006] up2date installing packages:
['postfix-2.2.10-1.RHEL4.2']
up2date:[Wed Sep 13 16:18:11 2006] up2date Removing packages from package
profile: ['postfix-2.1.5-4.2.RHEL4']
up2date:[Wed Sep 13 16:18:20 2006] up2date Adding packages to package profile:
['postfix-2.2.10-1.RHEL4.2']
up2date:[Wed Sep 13 16:18:23 2006] up2date deleting
/var/spool/up2date/postfix-2.2.10-1.RHEL4.2.x86_64.hdr
up2date:[Wed Sep 13 16:18:23 2006] up2date deleting
/var/spool/up2date/postfix-2.2.10-1.RHEL4.2.x86_64.rpm


Here is a sample of what we were seeing in the maillog with postfix-2.1.5-4.2.RHEL4:
Sep 11 03:12:33 abraham postfix/smtp[10112]: panic: myfree: corrupt or
unallocated memory block
Sep 11 03:12:34 abraham postfix/master[2181]: warning: process
/usr/libexec/postfix/smtp pid 10112 killed by signal 6
Sep 11 03:12:34 abraham postfix/qmgr[2189]: warning: premature end-of-input on
private/smtp socket while reading input attribute name
Sep 11 03:12:34 abraham postfix/qmgr[2189]: warning: private/smtp socket:
malformed response
Sep 11 03:12:34 abraham postfix/qmgr[2189]: warning: transport smtp failure --
see a previous warning/fatal/panic logfile record for the problem description

The "panic: myfree" appears six or seven times a week and the other lines appear
nearly the same number of times -- about 50 times a week -- from delivery of
about 100,000 messages two times a week.


Here are the messages which started immediately after the upgrade to
postfix-2.2.10-1.RHEL4.2.x86_64.rpm:
Sep 13 16:18:09 abraham sendmail[4251]: alias database /etc/aliases rebuilt by root
Sep 13 16:18:10 abraham postfix/master[4298]: fatal: bind 127.0.0.1 port 25:
Address already in use
Sep 13 16:19:56 abraham postfix/master[2310]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:19:56 abraham postfix/master[2181]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:19:56 abraham postfix/master[2238]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:19:56 abraham postfix/master[2366]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:19:56 abraham postfix/master[2181]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:19:56 abraham postfix/master[2310]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:19:56 abraham postfix/master[2238]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:19:56 abraham postfix/master[2366]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:20:02 abraham sendmail[4387]: alias database /etc/aliases rebuilt by root
Sep 13 16:20:03 abraham postfix/master[4433]: fatal: bind 127.0.0.1 port 25:
Address already in use
Sep 13 16:21:04 abraham postfix/master[2181]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:21:04 abraham postfix/qmgr[2189]: warning: unexpected attribute flags
in input from private/rewrite socket
Sep 13 16:21:04 abraham postfix/qmgr[2189]: warning: problem talking to service
rewrite: Success
Sep 13 16:21:04 abraham postfix/master[2181]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:21:05 abraham postfix/qmgr[2189]: warning: unexpected attribute flags
in input from private/rewrite socket
Sep 13 16:21:05 abraham postfix/qmgr[2189]: warning: problem talking to service
rewrite: Success
Sep 13 16:21:06 abraham postfix/master[2181]: warning: master_status_event:
partial status (4 bytes)
Sep 13 16:21:06 abraham postfix/qmgr[2189]: warning: unexpected attribute flags
in input from private/rewrite socket

I was seeing similar messages on other hosts that were just upgraded to
postfix-2.2.10-1.RHEL4.2.x86_64.rpm.
Sep 14 11:06:26 freedom postfix/master[2340]: warning: master_status_event:
partial status (4 bytes)
Sep 14 11:06:26 freedom postfix/master[2340]: warning: master_status_event:
partial status (4 bytes)
Sep 14 11:07:23 freedom postfix/master[2284]: warning: master_status_event:
partial status (4 bytes)
Sep 14 11:08:23 freedom last message repeated 2 times
Sep 14 11:08:23 freedom postfix/master[2284]: warning: master_status_event:
partial status (4 bytes)
Sep 14 11:08:26 freedom postfix/master[2340]: warning: master_status_event:
partial status (4 bytes)
Sep 14 11:09:26 freedom last message repeated 2 times
Sep 14 11:09:26 freedom postfix/master[2340]: warning: master_status_event:
partial status (4 bytes)
Sep 14 11:10:23 freedom postfix/master[2284]: warning: master_status_event:
partial status (4 bytes)
Sep 14 11:11:23 freedom last message repeated 2 times

Could it be that you are using sendmail and postfix at the same time?

Please check.

> Could it be that you are using sendmail and postfix at the same time?

Both Postfix and Sendmail were installed, but Sendmail was not configured or
running. Sendmail has been removed.

Also, postfix-2.2.10-1.RHEL4.2.x86_64.rpm appears to resolve this bug.

According to comment #26 this bug is resolved by postfix-2.2.10-1.RHEL4.2, which
is part of U4.