14MB per session? I haven't admined email for a while so I may be out of
touch, but it seems like that server should be able to process gigantic
volumes of mail. Not just "a lot" or even "really a lot". What mail setup
is it running? Throttling connections is the right way to go though.
Spoolin
14MB per session? I haven't admined email for a while so I may be out of
touch, but it seems like that server should be able to process gigantic
volumes of mail. Not just "a lot" or even "really a lot". What mail setup
is it running? Throttling connections is the right way to go though.
Spoolin
has anyone got perl + apache2 working on sid sucessfully? i've got
libapache2-mod-perl2 installed as well as apache2, and perl+cgi pages
show up displaying text. i've enabled perl.load and restarted apache but
its still not working:
fargo# ls -l /etc/apache2/mods-enabled/
total 0
lrwxrwxrwx
has anyone got perl + apache2 working on sid sucessfully? i've got
libapache2-mod-perl2 installed as well as apache2, and perl+cgi pages
show up displaying text. i've enabled perl.load and restarted apache but
its still not working:
fargo# ls -l /etc/apache2/mods-enabled/
total 0
lrwxrwxrwx
Dale E Martin said:
> Perhaps SA would be better implemented in something else, but like
> everyone
> else says, memory is cheap. Whatever makes the SA developers most
> effective is fine by me at this point.
As the other post mentioned, try SA+mimedefang if you need to run it on a
box with low
Dale E Martin said:
> Perhaps SA would be better implemented in something else, but like
> everyone
> else says, memory is cheap. Whatever makes the SA developers most
> effective is fine by me at this point.
As the other post mentioned, try SA+mimedefang if you need to run it on a
box with low
> there are couple of solutions to original problem of mr Dale Martin,
> some mentoined by others, like limiting number of connections etc. or
I was the one who said ultimately we throttled our mail via limiting
concurrent connections etc and we've been fine for some time.
> adding ram. the real
Please don't misunderstand it as a recommendation for less RAM:
We've tested a combination of sendmail-mimedefang-spamassassin
(the latter two backported from testing) on a maschine with only
64MB and a PII:
At a threshold of about 18000 mails per day out of a mixture from
large mails, worms, vir
On Monday 24 May 2004 13.57, Matej Kovac wrote:
[]
> test what takes
> so long for spamassassin, and report it.
Please file a bug against spamassassin and tell them using perl is a
bug. Perhaps even Severity: important since it affects performance
severely.
Seriously, what was your point of
> there are couple of solutions to original problem of mr Dale Martin,
> some mentoined by others, like limiting number of connections etc. or
I was the one who said ultimately we throttled our mail via limiting
concurrent connections etc and we've been fine for some time.
> adding ram. the real
--Friday, May 21, 2004 01:23:52 +1000 Russell Coker <[EMAIL PROTECTED]>:
[...]
> My idea was to have a
> cron job watch the FTP logs to launch rsync. That way rsync would only try
> to copy the files that were most recently updated. There would be a daily
> rsync cron job to cover for any pro
Please don't misunderstand it as a recommendation for less RAM:
We've tested a combination of sendmail-mimedefang-spamassassin
(the latter two backported from testing) on a maschine with only
64MB and a PII:
At a threshold of about 18000 mails per day out of a mixture from
large mails, worms, vir
On Monday 24 May 2004 13.57, Matej Kovac wrote:
[]
> test what takes
> so long for spamassassin, and report it.
Please file a bug against spamassassin and tell them using perl is a
bug. Perhaps even Severity: important since it affects performance
severely.
Seriously, what was your point of
--Friday, May 21, 2004 01:23:52 +1000 Russell Coker <[EMAIL PROTECTED]>:
[...]
> My idea was to have a
> cron job watch the FTP logs to launch rsync. That way rsync would only try
> to copy the files that were most recently updated. There would be a daily
> rsync cron job to cover for any pro
On Fri, May 21, 2004 at 02:48:32PM +0100,
Brett Parker <[EMAIL PROTECTED]> wrote
a message of 55 lines which said:
> So, in summary, change:
> for LOG in `syslogd-listfiles`
> to:
> for LOG in `syslogd-listfiles -s "mail.*"`
> in /etc/cron.daily/sysklogd
It worked. Many thanks.
Norton AntiVirus a détecté un virus dans une pièce jointe que vous
(debian-isp@lists.debian.org) avez envoyée à COMEXT CCI Libourne.
Pour garantir que les destinataires pourront utiliser les fichiers envoyés,
lancez une analyse des virus sur votre ordinateur, nettoyez les fichiers
infectés, pui
On Fri, May 21, 2004 at 02:48:32PM +0100,
Brett Parker <[EMAIL PROTECTED]> wrote
a message of 55 lines which said:
> So, in summary, change:
> for LOG in `syslogd-listfiles`
> to:
> for LOG in `syslogd-listfiles -s "mail.*"`
> in /etc/cron.daily/sysklogd
It worked. Many thanks.
17 matches
Mail list logo
