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 #336887
has caused the Debian Bug report #336887,
regarding exim: massive parrallel delevery attemts should be handled better
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.)
--
336887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336887
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: exim
Severity: wishlist
spohr.debian.org aka bugs.debian.org gets a lot of spam. Sometimes
spammers try to send large ammounts of spam at once from many
locations. spohr is currently suffering such an attack, with over
18000 processes (almost all exim or exim3) and a load average of 64,
but still with 20% idle time. No mail is getting delivered. This
situation is an unintentional greylisting. Eventually the processes
time out and things get back to our normal 100,000 spams/day to filter
out a few hunderd non-spams from. (This has happended before.)
What I would like to see is limits to how many exim processes run and
faster recovery when this type of DDOS attack happens. Since I don't
use exim, I don't know if it can be tuned better. Spohr is currently
running sarge, and the problem happend when it was running woody.
--- 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 ---
