forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: Apache mail problem
Date Wed, 18 May 2005 10:20:34 GMT
Ferdinand Soethe wrote:
> 
> Thorsten Scherler wrote:
> 
> > @all I think apache mail suffers from a worm called "sober". The next
> > attack is expected to happen in 10 days (around 26/27 May). It is once
> > again a windows only thing. More information (in German) can be found
> > http://www.spiegel.de/netzwelt/technologie/0,1518,356236,00.html.
> 
> If Thorsten is correct about this (is he?), it is about time to start thinking
> about solutions.

That is correct. Apache handles huge volumes of email
and consequently huge volumes of this crap.

The ASF is a volunteer organisation. If you want to help
then join the infrastructure mailing list (ASF committers only).
http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure

There is plenty that we can do to help, even if only to answer
the many questions that people ask and turn that into the
FAQ documentation at www.apache.org/dev/

Doing those mundane tasks will enable the ASF volunteers
who do know about mail systems to get on with the job.

Of course, they have have already been "thinking" about
solutions and implementing. Otherwise we would still
be in the grips of that mail storm. They dealt with it on IRC.

> Don't know about you (except for Nicola Ken who only
> reads mail once a day :-) but I'm not too happy about these delays and
> the perspective for this to happen a couple of times each month.

These delays over the last two days were wreaking havoc
on the opensource mailing lists. Answers to questions
were delayed, so more questions. The best thing to do
was to stop using email and get on with some local work
or go watch television, definitely not try to carry on
an email discussion :-)

I reckon that it is best not to commit to svn during such
a storm. Our trunk got broken twice yesterday, and people
could not immediately fix it.

--David


Mime
View raw message