Exim users,
I've run into a problem with Exim 3.22 after upgrading to Solaris 8. I'm
not exactly sure what is going on, but it appears that many copies of the
same bounced message (different message IDs however) generated by Exim are
getting frozen and stored under /var/spool/exim/input. These frozen
messages are stored as body only, no header, and they are filling up the
/var filesystem very fast:
-rw------- 1 exim mail 155648 Dec 18 16:35 16GNCp-0007IZ-00-D
-rw------- 1 exim mail 155648 Dec 18 16:35 16GNCr-0007JG-00-D
-rw------- 1 exim mail 155648 Dec 18 16:35 16GNCt-0007JR-00-D
-rw------- 1 exim mail 155648 Dec 18 16:35 16GNCu-0007JT-00-D
-rw------- 1 exim mail 155648 Dec 18 16:35 16GNCy-0007JX-00-D
-rw------- 1 exim mail 155648 Dec 18 16:35 16GND0-0007Jd-00-D
-rw------- 1 exim mail 155648 Dec 18 16:35 16GND2-0007Je-00-D
etc., etc.
When issuing:
bash-2.03# exim -Mvb 16GSyC-0006Vt-00 | more
16GSyC-0006Vt-00-D
wishes,
Human contact: <postmaster\@>
MULTIPLEFOOTER
my $single_bounce_footer = <<SINGLEFOOTER;
You may reply to this email and it will be read by someone who will do
their best to help you. You may Tue, 18 Dec 2001 22:44:21 +0000Received:
from ns1.registed.net ([212.83.156.100] helo=serapwin.fr.wo
rldonline.com)
by mozart.singapore.sinet.slb.com with esmtp (Exim 3.22 #1)
id 16GSyC-0006Vt-00
for BBOCHRAWNA@???: from ns1.registed.net
([212.83.156.100] helo=serapwin.fr.worldonline.com)
by mozart.singapore.sinet.slb.com with esmtp (Exim 3.22 #1)
id 16GSyC-0006Vt-00
for BBOCHRAWNA@???; Tue, 18 Dec 2001 22:44:21 +0000
lpradal@???.83.1BBOCHRAWNA@???)
> \&ail_inswith esmtp no
for BBOCHRAWNA@???,
one_no_mail => \&fail_one_no_mail,
multiple => \&fail_multiple,
too_many => \&fail_multiple,
invalid_entry => \&fail_entry,
);
my %failure_reason = (
insane => 'invalid address',
none => 'no from (helo=serapwin.fr.worldonline.com)
'single match but no email address',
multiple => 'few matches',
too_many => 'too many matches',
invalid_entry => 'invalid database entry',
);
# failure_reason called by autoreply transport to make X-LDAP-Alias header
sub failure_reason {
if ( !defined $re
ÿ ;¯ ùðùðº`º`x¤x°¨¼¨¯ [Lùð[Xº`Ïì
xäh¨tèô^L$0<HT`lx¨´ÀÌØäð
The rest of the body is the same garbage as line above.
It seems like the perl rules file (exim.pl) is failing somewhere. Does
anyone have any ideas? Thanks.
Regards,
Steve Romero