Hi
Many thanks for the answer - I am looking at the port dir I compiled and
yes - it seems to be running rev -24. Has this feature, so to speak,
been around for a while as I have been recompiling the exim port every
time a revision has come out to see if the error would go away to save
bothering anyone. Looking back there has been a number or port updates
in the last two months or so.
Any finally, does this mean mail is getting lost that may have single
base64 encoding somewhere in it?
Many thanks
Gordon
-----Original Message-----
From: Tom Kistner [
mailto:tom@duncanthrax.net]
Sent: 03 March 2003 11:18
To: Gordon McKee
Cc: exim-users@???; Sheldon Hearn
Subject: Re: [Exim] Exited on PID 11
Gordon McKee wrote:
> Ever since I upgraded to exim 4 I get the following errors every night
> in the system log file. I have had a look at the exim log files and
> there is no activity regarding these error. I don't think I am losing
> any mail - but you can never be sure.
>>pid 3621 (exim-4.12-1), uid 26: exited on signal 11
If this is exiscan rev -24 (from BSD ports), this may be a singlepart
base64 encoded message (probably autogenerated by some script).
There is a bug in -24 that will cause a segfault on such messages.
You can
- set exiscan_demime_condition = 0 and wait for the FreeBSD exim
port manager to update the port (hi Sheldon, please don't hit
me *OUCH*).
- get exim-4.12 and exiscan-4.12-25 and compile manually.
To avoid such nastyness in the future, there will be a -STABLE and
-DEVEL version of the exiscan patch soon.
It took me too long to realize the increased popularity of my patch.
Sorry for the fuzz :(
/tom
--
Tom Kistner <tom@???>
ICQ 1501527 dcanthrax@efnet
http://duncanthrax.net
