On Mon, Jun 11, 2007 at 10:46:37AM +0100, Justin Mason wrote:
> Right now we only have one mirror listed, but it's trivial to add more to
> the MIRRORED_BY list. Also, a failed download will not affect anything
> for users, apart from maybe that they may miss a pending update for N
> hours -- ther
> I'm not sure we can right now. (The architecture is there so that we
> could handle it if we wanted to, but we'd better mitigate it if
> possible.)
That's my thinking -- the architecture is already there.
sa-update's DNS polling is incredibly lightweight and can handle millions
of clients upda
On Sun, Jun 10, 2007 at 09:23:14PM +0100, Justin Mason wrote:
> Marc A. Donges writes:
> > sa-update being started from cron.daily is probably a DoS attack against
> > Spamassassin update servers.
> Actually, we can handle it just fine. We know what we're doing ;)
I'm not sure we can right now.
Marc A. Donges writes:
> sa-update being started from cron.daily is probably a DoS attack against
> Spamassassin update servers.
Actually, we can handle it just fine. We know what we're doing ;)
--j.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
Package: spamassassin
Version: 3.2.0-2
Severity: important
sa-update being started from cron.daily is probably a DoS attack against
Spamassassin update servers.
Although it is not the default configuration, many users will activate
automatic rule updates via sa-update with the mechanism provided
5 matches
Mail list logo
