On Jan 29, 2007, at 21:52 , Shane Chrisp wrote:
I know this is not exactly vpopmail related, but as its a vpopmail
related tool i thought others here would like to be made aware of
this.
I have been using vhostadmin for a while now, and have just noticed
that
it is vulnerable to a xss
Or turn off Register_global, and then MODULES_DIR would only exist in
$_GET[]. I chalk this one up to a bad PHP configuration:
http://www.php.net/register_globals
While it would not stop attacks that could cause you to include stuff
if other variables are not checked before blindly
I have also posted this to vchkpw list:
I have a server with qmail running some 600 email accounts over some
30 domains. I recently installed simscan, Spamassassin and ClamAv.
It all works really well, but during peak hours (say 300 to 500k per
sec inbound traffic) Thee server starts to
On Tue, 2007-01-30 at 19:14 -0600, Max Esquivel wrote:
I have also posted this to vchkpw list:
I have a server with qmail running some 600 email accounts over some
30 domains. I recently installed simscan, Spamassassin and ClamAv.
It all works really well, but during peak hours (say
On Wed, 2007-01-31 at 11:22 -0500, Darrel O'Pry wrote:
On Tue, 2007-01-30 at 19:14 -0600, Max Esquivel wrote:
I have also posted this to vchkpw list:
I have a server with qmail running some 600 email accounts over some
30 domains. I recently installed simscan, Spamassassin and ClamAv.
Thanks all for the suggestions. Been looking at things in more detail:
1) Im not sure how many sessions we are handling. I do now we were
maxing out at 120 connections per sec at peak times.
2) we do have spamc and spamd running.
spamd --max-children 25 -x -v -d
Max Esquivel wrote:
Thanks all for the suggestions. Been looking at things in more detail:
1) Im not sure how many sessions we are handling. I do now we were
maxing out at 120 connections per sec at peak times.
2) we do have spamc and spamd running.
spamd --max-children 25 -x -v -d
On Wed, 2007-01-31 at 13:11 -0500, Rick Macdougall wrote:
Max Esquivel wrote:
Thanks all for the suggestions. Been looking at things in more detail:
1) Im not sure how many sessions we are handling. I do now we were
maxing out at 120 connections per sec at peak times.
2) we do
