Hi
I am using the latest Debian Sarge exim-daemon-heavy package:
Exim version 4.32 #1 built 26-Apr-2004 09:57:22
Copyright (c) University of Cambridge 2004
Berkeley DB: Sleepycat Software: Berkeley DB 3.2.9: (June 16, 2003)
Support for: iconv() IPv6 PAM Perl GnuTLS
Lookups: lsearch wildlsearch nwildlsearch cdb dbm dbmnz dnsdb dsearch
ldap ldapdn ldapm mysql nis nis0 passwd pgsql
Authenticators: cram_md5 plaintext spa
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram
redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Fixed never_users: 0
Contains exiscan-acl patch revision 17 (c) Tom Kistner
[
http://duncanthrax.net/exiscan/]
Configuration file is /etc/exim4/exim4.conf
I am also using exiscan-acl to spam(assassin) and virus scan (clamav)
all incoming messages that get past the helo, mail, and rcpt acls. I
reject about 90 000 emails per day based on the above and let through
(to the Exchange box) about 9000 emails.
However, every week or so Exim will inexplicably die. I understand
that there was a problem in earlier versions of Exim4 where roughly one
in a million emails could potentially cause it to crash (unless I dreamt
that -- and with my current jetlag I wouldn't be surprised if I did.)
As I understand it a bugfix for this should have worked its way into
Debian Sarge by now. If this is a case, then perhaps I have done
something wrong in configuring Exim.
Is there anything I could check right now to help troubleshoot this.
I'll sanitise my config in anticipation of being asked show it.
Any help would be much appreciated. I have resorted to tailing mainlog
and seeing when last an entry was made and trying to restart in the
event that the last entry was more than x number of seconds ago. The
trouble is that cron cannot seem to use the /etc/init.d/exim4 script --
I think, maybe, it is having difficulty switching users to the exim
user...? The monitoring script works well from the commandline.
Cheers,
Ryan
