>The problem, as I see it, is that this implies that there are ways to
force an assp crash and, therefore, ways create a DDoS attack on assp.
Yes, this is possible - and possibly we are unable to fix this for all
cases. An DDoS attack should be blocked by the firewall in front of assp -
limit the connections per second and the total number of concurrent
connection - use the exportextreme file for IP-address blocking! But we
know, that some strange headers or malformed mails could lead in to a assp
crash - the only way to get rid of most of that problems, is investigating
the maillog.txt and .eml files for equal entries before a crash happens.
If a reason is found, there are several ways to block such mails (IP,
domain, preheaderre, ....) - but how ever, this should be done with the
most early possible check.
>> and don't forget share your knowledge with others <<
And at least - there are (I'm sure) multiple bugs in ASSP.
>I still think that .13 was flakey for me
There are no changes that belongs to the SMTP stuff of assp in the last
versions 13-16 .
Thomas
Von: Trevor Jacques <[email protected]>
An: ASSP development mailing list <[email protected]>
Datum: 19.07.2010 15:33
Betreff: Re: [Assp-test] Versions .13 and .15
> I'm experiencing the opposite behaviour; .15 seems to be quite stable
I've had a little more time since my post to determine what's going on,
and it seems to be the result a multi-week flurry of spam that tanks assp.
I think that flurry has just finished (as of a day or three ago, because
spam number have returned to normal, from about three times normal). This
has happened to me once before. That time, Thomas and I found a way to
nuke the problem. I have not had time to prove my hypothesis for this
time, but assp has been up/stable for three days, but before that it was
crashing every few hours.
The problem, as I see it, is that this implies that there are ways to
force an assp crash and, therefore, ways create a DDoS attack on assp. On
the up side, assp has, almost, reliably restarted. On one crash in this
recent flurry, it trashed its settings, which killed SMTP completely, even
though assp thought that it was still up and working. Using backup config.
files reënabled assp. The trashing of the settings happened with the
previous flurry of spam, also. Just maybe, the trashing of the settings
coïncided with the peak of the flurry, but that would take a lot of
sleuthing to prove, and I don't think I have the time to do so, especially
since assp restarts well enough (trashing of settings notwithstanding).
I still think that .13 was flakey for me, but the implication of the
flurry slowing down is that .15 may not have been flakey, because it may
simply have coïncided with the most recent flurry of spam.
HTH,
T.
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test