Just writing to say that I have the exact same problem on RedHat 7.1
2.0.14 segfaults on lmtpd (sometimes) while 2.0.12 works fine. Using BDB
3.2.9 (although problem was there with 3.1.17 also).
ldd master
libssl.so.1 => /usr/lib/libssl.so.1 (0x40028000)
libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0x40055000)
libdb-3.2.so => /lib/libdb-3.2.so (0x40111000)
libc.so.6 => /lib/i686/libc.so.6 (0x401a8000)
libdl.so.2 => /lib/libdl.so.2 (0x402d8000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
ldd imapd
libsasl.so.7 => /usr/local/lib/libsasl.so.7 (0x40018000)
libssl.so.1 => /usr/lib/libssl.so.1 (0x40032000)
libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0x4005f000)
libdb-3.2.so => /lib/libdb-3.2.so (0x4011b000)
libnsl.so.1 => /lib/libnsl.so.1 (0x401b2000)
libc.so.6 => /lib/i686/libc.so.6 (0x401c9000)
libdl.so.2 => /lib/libdl.so.2 (0x402f9000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x402fe000)
libpam.so.0 => /lib/libpam.so.0 (0x4032c000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
ldd lmtpd
libsasl.so.7 => /usr/local/lib/libsasl.so.7 (0x40018000)
libssl.so.1 => /usr/lib/libssl.so.1 (0x40032000)
libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0x4005f000)
libdb-3.2.so => /lib/libdb-3.2.so (0x4011b000)
libnsl.so.1 => /lib/libnsl.so.1 (0x401b2000)
libc.so.6 => /lib/i686/libc.so.6 (0x401c9000)
libdl.so.2 => /lib/libdl.so.2 (0x402f9000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x402fe000)
libpam.so.0 => /lib/libpam.so.0 (0x4032c000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
ldd /usr/local/lib/libsasl.so.7
libdb-3.2.so => /lib/libdb-3.2.so (0x4001b000)
libdl.so.2 => /lib/libdl.so.2 (0x400b2000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x400b6000)
libpam.so.0 => /lib/libpam.so.0 (0x400e4000)
libc.so.6 => /lib/i686/libc.so.6 (0x400ec000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)
Nicholas Blackaby wrote:
>Hello,
>
> I have having problems concerning lmtpd crashing when using
>Cyrus IMAP version 2.0.14 which do _not_ appear with version
>2.0.12. The same (or similar) problem(s) were reported by (an)other
>poster(s) to this list a couple of weeks ago but there appears to have
>been no discussion since and no resolution? I include details below
>for the information of (i) the developers, and (ii), admins who may
>be considering upgrading to version 2.0.14. I can provide more
>details if necessary.
>
> The problem I have with version 2.0.14 is that lmtpd crashes
>relatively often when called by the deliver program. To be a little
>more precise, as user cyrus on the imap server, in one test I sent
>user "testuser" ten messages in quick succession, by typing the
>command
>
>/usr/cyrus/bin/deliver -a testuser -m -- testuser < /tmp/message
>
>ten times, one after another. I found that seven out of the ten
>messages _were_ delivered to testuser's Cyrus mailstore but three
>of the messages were _lost_ (as if they had disappeared down a
>blackhole). In fact, on inspecting /var/log/imapd.log I find three error
>messages, corresponding to each of those lost messages. One of
>these error messages (with associated text) says:
>
>Jun 19 10:17:22 frosty master[17743]: about to exec
>/usr/cyrus/bin/lmtpd
>Jun 19 10:17:22 frosty service-lmtpunix[17743]: executed
>Jun 19 10:17:24 frosty lmtpd[17743]: accepted connection
>Jun 19 10:17:24 frosty lmtpd[17743]: lmtp connection preauth'd as
>postman
>Jun 19 10:17:25 frosty lmtpd[17743]: accepted connection
>Jun 19 10:17:25 frosty lmtpd[17743]: lmtp connection preauth'd as
>postman
>Jun 19 10:17:26 frosty lmtpd[17743]: accepted connection
>Jun 19 10:17:26 frosty lmtpd[17743]: lmtp connection preauth'd as
>postman
>Jun 19 10:17:26 frosty master[561]: process 17743 exited, signaled
>to death by 11
>
>For information: this problem is reproducable on other hardware and
>so I fnd it unlikely that it is hardware related!
>
>The machine is running RedHat Linux 7.1.
>
>I compiled and installed Berkeley DB version 3.2.9.
>
>I compiled and installed Cyrus SASL version 1.5.24 with configure
>command:
>
>$ CPPFLAGS=-I/usr/local/BerkeleyDB.3.2/include \
> LDFLAGS=-L/usr/local/BerkeleyDB.3.2/lib \
> ./configure --with-plugindir=/usr/local/lib/cyrus-sasl-1.5.24 \
> --with-dblib=berkeley --disable-krb4 --disable-gssapi \
> --with-rc4 --enable-anon --enable-cram --enable-plain \
> --enable-login --with-pam
>
>I compiled and installed Cyrus IMAP 2.0.14 with the configure
>command:
>
>$ ./configure --with-dbdir=/usr/local/BerkeleyDB.3.2 \
> --with-auth=unix --with-sasl=/usr/local/lib/cyrus-sasl-1.5.24 \
> --without-libwrap
>
>Please note that I used the same(*) configuration options with Cyrus
>2.0.12, with the same hardware and the same RedHat 7.1 install,
>and this lmptd crashing problem was not apparent.
>
>(*) The only difference (apart from the version of cyrus imap itself),
>is the "--without-libwrap" option [tcp wrappers] which I chose to use
>with 2.0.14 since I was unable to connect to my 2.0.14 server
>otherwise (has anyone else noticed a problem here, or is it just
>me?).
>
>Thanks,
>Nick.
>--
>Nicholas Blackaby, ISD, UMIST.
>[EMAIL PROTECTED], 0161 200 3208
>
