Your message dated Wed, 16 Apr 2008 17:40:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line exim has been removed from Debian, closing #214960
has caused the Debian Bug report #214960,
regarding exim cronjob can be an incremental denial of service
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
214960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214960
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: exim
Version: 3.35-1woody2
Severity: important
The default cron job spawns a queue runner every 15 minutes without
checking whether there are a lot of queue runners already active.
If the queue contains some messages being directed to broken domains
(which is what a lot of spam originators want to look like)
this can create transients of very high load and fast logfile growth.
In the steady state there will be one queue runner held up on every
broken domain name; for a thousand messages this is a thousand processes.
The load due to those messages is low, since the processes just sit
around for a long time and then time out, before starting the next msg.
Even when a large fraction of those blocked runners give up at the
same time, they cannot do much before getting blocked from work again.
However, this also implies that each queue runner will examine every
legitimate message as well, generating "retry time not reached" notes
in the various log files. However, when any change in nameserver
data or internet routing triggers the blocked queue runners into
flowing through, this can be the dominant source of runtime load
a massive stream "retry time not reached" will be generated.
The number of log entries is approximately half the broken messages
_times_ half the total queue length ... nominally all at once.
I think there may be some value to restricting the number of parallel
queue running processes that the cron job might choose to start up.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux calexico 2.2.20 #1 Sat Apr 20 11:45:28 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages exim depends on:
ii cron 3.0pl1-72 management of regular background p
ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an
ii libdb2 2:2.7.7.0-7 The Berkeley database routines (ru
ii libident 0.22-2 simple RFC1413 client library - ru
ii libldap2 2.0.23-6.3 OpenLDAP libraries.
ii libpam0g 0.72-35 Pluggable Authentication Modules l
ii libpcre3 3.4-1.1 Philip Hazel's Perl Compatible Reg
--- End Message ---
--- Begin Message ---
Version: 3.36-18.2+rm
The exim package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/420191 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
Barry deFreese
--- End Message ---
