Hi
I thought this error had gone but it seems to be back again. Is there any way
I can help you debug this, or is there a way to get exiscan to dump out the
messages that I could forward to you for analysis.
Many thanks
Gordon
Quoting Tom Kistner <tom@???>:
> 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
>
>
-------------------------------------------------
This mail sent through IMP:
http://horde.org/imp/
