All the logs said were "message id xxxx is frozen" over and over again.
I thought I might be getting mail-bombed also. It turns out that all
the messages frozen in the queue were from several weeks ago (long
story: trip to Madagascar, nis server failed, local user names could not
be resolved, cron spewed undeliverable email each minute for weeks...).
I think what was happening was that tidydb (launched from cron job each
night) was simply looping over all the messages in the queue and
emitting "message frozen" log entries---they were not new incoming
messages at all. In the end "cd /var/spool/exim; for f in `ls | perl
-ne 'next if /-D$/;s/-H$//;print $_'`; do exim -Mrm $f; done" did the
trick. Thanks to all that responded.
Cheers,
Tim
Suresh Ramasubramanian wrote:
>Timothy H. Keitt <exim-users> [29/06/01 14:20 -0400]:
>
>
>>1) exim is churning away with 20-40% cpu usage and load between 1 and 2
>>on an otherwise unladen machine
>>2) my exim logs are growing huge; tail -f shows several new entriers per
>>second saying "message frozen"
>>
>
>All of them bounces (with null sender)? It is likely that a spammer forged
>your domain in a spam and left your MX to accept all the bounces.
>
>Or one of your users is being mailbombed
>
>Or you have a mail loop.
>
>Can't tell without log excerpts, or a crystal ball.
>
> -suresh
>
>--
>## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
--
Timothy H. Keitt
Department of Ecology and Evolution
State University of New York at Stony Brook
Stony Brook, New York 11794 USA
Phone: 631-632-1101, FAX: 631-632-7626
http://life.bio.sunysb.edu/ee/keitt/
