I searched through the exim-users archive before I posted this
but I didn't find what the cause may be.
I upgraded my Linux Slackware system this weekend and before I did I
saved the /usr/local/Exim directory and all the configuration files before
doing so. After getting everything back up and running I could get mail fine
but couldn't send any. That shows from the first chunk of error messages below.
I did a complete upgrade to Slackware 3.6 Kernel 2.0.35.
So I figured that maybe I got some libraries setup differently in the upgrade
so I rebuilt exim with the latest version from sources and tried it again and
got the second chunk of errors below. The rebuild of Exim went without a
problem. I saved my old configure file which I have been using for about 6 -
8 months now and am using it.
So I went back to sendmail and joined exim-users and here I am.
>From what I can tell from the exim-user archives this has been caused by the
dbm includes in the past. But I didn't see anything about it happening to
Slackware linux systems.
So does anyone have any suggestions as to what the problem may be on this one?
Has anyone else reported this on Slackware Linux?
FIRST chunk)
1999-03-08 17:45:12 queue run: process 8957 crashed with signal 11 while
delivering 10K9dY-0002Je-00
1999-03-08 18:01:30 queue run: process 9021 crashed with signal 11 while
delivering 10K9dY-0002Je-00
Second chunk)
1999-03-08 18:35:40 10K9dY-0002Je-00 SEGV while reading
"T:mail.amaonline.com:208.245.208.3:10K9dY-0002Je-00"
from dbm file: record assumed not to exist
1999-03-08 18:43:13 10K9dY-0002Je-00 SEGV while reading
"T:mail.amaonline.com:208.245.208.3:10K9dY-0002Je-00"
from dbm file: record assumed not to exist
--
*** Exim information can be found at
http://www.exim.org/ ***
