Am 2008-01-09 22:34:05, schrieb Arturo 'Buanzo' Busleiman:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sam Varshavchik wrote:
| Each delivery attempt requires a hit to your account database, there's
| no way around it. If you keep your accounts in an mysql or a postgresql
| database,
Michelle Konzack wrote:
Am 2008-01-09 22:34:05, schrieb Arturo 'Buanzo' Busleiman:
Those queries can be sped up with some cache, indexes and maintenance. How
many records do you have in your account tables, Michelle?
186 from my @home network and arround 23.000 from my customers
Am 2008-01-16 11:03:11, schrieb Gordon Messmer:
What's your table schema look like? (Be sure to include your indexes.)
I am using pam authentification with libpam-pgsql and libnss-pgsql
Presumably on the same LAN?
Yes, but only on a 3Com SuperStack III Switch with 100 MBit.
Thanks,
Michelle Konzack writes:
Am 2008-01-16 11:03:11, schrieb Gordon Messmer:
What's your table schema look like? (Be sure to include your indexes.)
I am using pam authentification with libpam-pgsql and libnss-pgsql
Well there's your problem right there. PAM does this in a rather simplistic,
Hello *,
from the spamassassin list I have gotten this:
- Forwarded message from Bookworm [EMAIL PROTECTED] -
Date: Mon, 31 Dec 2007 13:51:40 -0600
From: Bookworm [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: DDOS, Dictionary Attack... not sure what it is...
Mike Cisar wrote:
Hi
Michelle Konzack writes:
courier-mta does reject all of this crap but the System- and CPU-Load
are nearly at 100%. and since courier and my SDSL can not handel this
mass of crap my MX is hit to and continue sending this crap to me
constantly.
Is there a way to reject the messages with much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sam Varshavchik wrote:
| Each delivery attempt requires a hit to your account database, there's
| no way around it. If you keep your accounts in an mysql or a postgresql
| database, that means a query per message delivery attempt.
Those queries can
Hi.
Am Donnerstag, 10. Januar 2008 schrieb Sam Varshavchik:
Finally, explore using popular blacklists of compromised IP addresses.
There are several blacklists that claim to list only machines that have
been verified as compromised/trojaned. There's very little downside to it,
and the risk of
