[Exim] SEGV in test release

Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: Chris Edwards
Fecha:  
A: exim-users
Asunto: [Exim] SEGV in test release
Hi,

We've stumbled across a domain - marin.ntnu.no - which appears to give the
3.092 testing version some trouble. Doing:

    exim -bt u@???


crashes roughly 1 in 3 times I try it. The localpart appears not to
matter.

Note that the latest released version - exim 3.03 - behaves correctly
every time with this test.

MX records for the site look somewhat odd:

marin.ntnu.no.  85224   MX      5 mari1.marin.ntnu.no.
marin.ntnu.no.  85224   MX      10 mari1.marin.ntnu.no.
marin.ntnu.no.  85224   MX      20 runix.runit.sintef.no.
marin.ntnu.no.  85224   MX      10 runix.runit.sintef.no.


though presumably this is legal. My first thought was it could be related
to the order in which the DNS returns the records. Repeatedly trying the
"exim -bt" gives:

ORDER          RESULT


 5 10 20 10    Always crashes
10 20 10  5    Sometimes crashes
20 10  5 10    Always works
10  5 10 20    Always works


Strangest of all is the "10 20 10 5" case which sometimes works, sometimes
fails.

We are running exim on Solaris 7, and the problem occurs even with the
out-of-box config file. The DNS server was running bind 8.2.1. Now its
running bind 8.2.2-P5 after the recent cert advisory. This made no
difference to the exim problem.

Chris


exim -d11 -bt u@???
Exim version 3.092 debug level 11 uid=0 gid=1
probably ndbm
Caller is an admin user
Caller is a trusted user
sender address = root@???
Address testing: uid=0 gid=1 euid=0 egid=1
>>>>>>>>>>>>>>>>>>>>>>>>

Testing u@???
marin.ntnu.no in local_domains? no (end of list)
address u@???
local_part=u domain=marin.ntnu.no
domain is not local
>>>>>>>>>>>>>>>>>>>>>>>>

routing u@???, domain marin.ntnu.no
lookuphost router called for u@???
  dns lookup: route_domain = marin.ntnu.no
;; res_querydomain(marin.ntnu.no, <Nil>, 1, 15)
;; res_query(marin.ntnu.no, 1, 15)
;; res_mkquery(0, marin.ntnu.no, 1, 15)
;; res_send()
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34972
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;;      marin.ntnu.no, type = MX, class = IN
;; Querying server (# 1) address = 130.209.12.9
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34972
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 3, ADDITIONAL: 4
;;      marin.ntnu.no, type = MX, class = IN
marin.ntnu.no.          22h27m47s IN MX  5 mari1.marin.ntnu.no.
marin.ntnu.no.          22h27m47s IN MX  10 mari1.marin.ntnu.no.
marin.ntnu.no.          22h27m47s IN MX  20 runix.runit.sintef.no.
marin.ntnu.no.          22h27m47s IN MX  10 runix.runit.sintef.no.
marin.ntnu.no.          22h27m47s IN NS  neptun.marin.ntnu.no.
marin.ntnu.no.          22h27m47s IN NS  ludvig.ntnu.no.
marin.ntnu.no.          22h27m47s IN NS  runix.runit.sintef.no.
mari1.marin.ntnu.no.    22h27m47s IN A  129.241.141.51
runix.runit.sintef.no.  22h29m4s IN A   129.241.1.5
neptun.marin.ntnu.no.   22h27m47s IN A  129.241.140.10
ludvig.ntnu.no.         35m33s IN A     129.241.190.190
DNS lookup of marin.ntnu.no (MX) succeeded
Segmentation Fault (core dumped)