[EXIM] V2.10 on Solaris 2.5.1 segfaults with -Mg

Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: Harald Meland
Fecha:  
A: exim-users
Asunto: [EXIM] V2.10 on Solaris 2.5.1 segfaults with -Mg
Whenever I try to "cancel" any frozen message with the "-Mg" command
line option, Exim 2.10 segfaults on me -- and the "message cancelled"
report does not contain the original message (see example below).

I haven't found any core files anywhere (I have looked in the spool
and log dirs).

With -v, the output (up to the segmentation fault) goes like this:

  ulrik$ exim -v -Mg 0zs5sG-0001K1-00
  delivering message 0zs5sG-0001K1-00
  LOG: 0 MAIN
    Unfrozen by forced delivery
  LOG: 0 MAIN
    cancelled by hmeland
  Exim version 2.10 debug level 1 uid=7411 gid=7411
  probably ndbm
  Segmentation Fault


With -d9, the output becomes:

  ulrik$ exim -d9 -Mg 0zs5sG-0001K1-00
  Exim version 2.10 debug level 9 uid=29578 gid=330
  probably ndbm
  set_process_info:  6533 2.10 delivering specified messages
  delivering message 0zs5sG-0001K1-00
  set_process_info:  6533 2.10 delivering 0zs5sG-0001K1-00
  Opened spool file 0zs5sG-0001K1-00-H
  user=exim uid=7411 gid=7411 sender=
  sender_local=0 resent=no ident=exim
  Non-recipients:
  Empty Tree
  ---- End of tree ----
  recipients_count=1
  body_linecount=19 message_linecount=28
  LOG: 0 MAIN
    Unfrozen by forced delivery
  Delivery address list:
    test.of.nonexistant.address@??? 
  LOG: 0 MAIN
    cancelled by hmeland
  search_tidyup called

>>>>>> Local deliveries >>>>>>

search_tidyup called
>>>>>> Remote deliveries >>>>>>

set_process_info: 6533 2.10 tidying up after delivering 0zs5sG-0001K1-00
Processing retry items
Succeeded addresses:
Failed addresses:
test.of.nonexistant.address@???: no retry items
Deferred addresses:
end of retry processing
Exim version 2.10 debug level 9 uid=7411 gid=7411
probably ndbm
sender address =
set_process_info: 6534 2.10 accepting a local non-SMTP message from <>
Sender:
search_tidyup called
sending error message to: postmaster@ulrik
>>Original headers:

X-Failed-Recipients: test.of.nonexistant.address@???
From: Mail Delivery System <Mailer-Daemon@ulrik>
To: postmaster@ulrik
Subject: Mail delivery failed

  rewrite_one_header: type=F:
    From: Mail Delivery System <Mailer-Daemon@ulrik>
  rewrite_one_header: type=T:
    To: postmaster@ulrik
  search_tidyup called

>>Final headers:

  P Received: from exim by ulrik with local (Exim 2.10 #1)
          id 0zs68F-0001hO-00
          for postmaster@ulrik; Mon, 21 Dec 1998 15:16:23 +0100
    X-Failed-Recipients: test.of.nonexistant.address@???
  F From: Mail Delivery System <Mailer-Daemon@ulrik>
  T To: postmaster@ulrik
    Subject: Mail delivery failed
  I Message-Id: <E0zs68F-0001hO-00@ulrik>
    Date: Mon, 21 Dec 1998 15:16:23 +0100


Segmentation Fault

For the purposes I would prefer to use -Mg for[1], -Mrm also sort of
gets the work done[2]. However, segfaults are not nice -- does anyone
know whether this problem is due to me misconfiguring something, or is
it a bug somewhere in Exim?


[1] Removing those pesky frozen error messages due to my relays not
    knowing which localparts are valid in any domain
[2] But as -Mg doesn't work, I havent't been able to experience what
    the differences between the two options are.
-- 
Harald
------- Start of forwarded message -------
From: Mail Delivery System <Mailer-Daemon@???>
To: postmaster@???
Subject: Mail delivery failed
Message-Id: <E0zs6BM-0001lh-00@ulrik>
Date: Mon, 21 Dec 1998 15:19:36 +0100


This message was created automatically by mail delivery software.

A message sent by

<>

could not be delivered to all of its recipients. The following address(es)
failed:

  test.of.nonexistant.address@???:
    delivery cancelled by administrator


------ This is a copy of the message, including all the headers. ------


------- End of forwarded message -------

--
*** Exim information can be found at http://www.exim.org/ ***