We are doing LDAP queries, but we can't cache them. Long story.
We're using round robin MX. Everything is setup correctly. It just seems
like the relay servers can't handle it.
How can you tell that you handled 2.1 million messages? is there some
kind of program that can analyze the log?
I
More ram and use round robin MX records?
I have a 850mz PIII that did 2.1 Million messages today (yes, it gets a
little tired when it hits 6mm per day, no I am not a sadist, just
wanted to see how much a 850Mhz PII count take)
Try relying more on postfix filters for the 'this can't possibly be
g
Firstly, thank you for all previous help.
I have set up Postfix+amavisd-new on a few servers. However, some of
them seem to suffer from renegade amavisd children processes. After
running fine for a while, suddenly an amavisd child process will grab
all free CPU cycles. The process repeats itse
Mark Martinec wrote:
Here is one way of doing it:
$QUARANTINEDIR = '/var/spool/amavis/';
$spam_quarantine_method = 'local:spam/%m.gz';
$virus_quarantine_method= 'local:virus/%m';
$banned_files_quarantine_method = 'local:banned/%m';
$bad_header_quarantine_method = 'local:b
hi all,
We've got two 3 ghz 1 gb RAM relay servers (relay1 and relay2) at work.
We recently combined our two mail servers into one, which means these
two relay servers are now doing virtual user table translation and
amavis (spamassassin and clamav) scanning for about 6,000 accounts.
Relay2
Hans,
> The only part that still bothers me is I'd like to keep the spam and
> virus mails separate. I have made a /var/spool/amavis/spam/ directory
> for that. How do I define 'spam-quarantine' ?
Here is one way of doing it:
$QUARANTINEDIR = '/var/spool/amavis/';
$spam_quarantine_method
> ...My guess is the emji.net headers were there prior to blast.com accepting
> this message. ...
> So it looks like existing X-Spam headers are not removed unless spam
> scanning is enabled. It does not mean blast.com is scanning.
Indeed. There is no need to remove such pre-existing headers
unl
Matt wrote:
> Hi,
> I have two identical servers running SA 3.1.0-rc2 and amavisd-new 2.3.0.
> On one server, the results of a spam check will add the actual score for
> each test in the headers, like below:
> tests=[AWL=-0.040, BAYES_00=-2.599, FORGED_RCVD_HELO=0.135, SPF_PASS=-0.001]
> On the o
Hi,
I have two identical servers running SA 3.1.0-rc2 and amavisd-new 2.3.0.
On one server, the results of a spam check will add the actual score for
each test in the headers, like below:
tests=[AWL=-0.040, BAYES_00=-2.599, FORGED_RCVD_HELO=0.135, SPF_PASS=-0.001]
On the other server, I just ge
Adam Kennedy (akennedy) writes:
>
> Would Amavis benefit from a dual proc setup under Linux 2.6? I'm getting
> ready to upgrade some servers, and I was wondering if anyone has seen
> any improvement with using dual proc over single proc.
Definitely, IF you have the RAM to go with it.
-
* Clifton Royston <[EMAIL PROTECTED]>:
> If you're running SA, definitely. It will eat pretty much all the
> CPU you can throw at it, and any modern *nix kernel will make good use
> of both CPUs.
Virusscanning will benefit, too.
--
Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTE
On Tue, Sep 06, 2005 at 02:59:16PM -0500, Adam Kennedy wrote:
> Would Amavis benefit from a dual proc setup under Linux 2.6? I'm getting
> ready to upgrade some servers, and I was wondering if anyone has seen
> any improvement with using dual proc over single proc.
If you're running SA, definite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Would Amavis benefit from a dual proc setup under Linux 2.6? I'm getting
ready to upgrade some servers, and I was wondering if anyone has seen
any improvement with using dual proc over single proc.
- --
Northern Indiana ESC
Adam Kennedy - [EMAIL PROTE
Anne wrote:
> I turned of spam checking in /etc/amavis.conf:
> @bypass_spam_checks_maps = (1); # uncomment to DISABLE anti-spam code
> because I just want virus checking. I see this in my log on startup:
> Sep 6 13:50:46 hedwig amavis[15431]: ANTI-SPAM codeNOT loaded
> but I still ge
I turned of spam checking in /etc/amavis.conf:
@bypass_spam_checks_maps = (1); # uncomment to DISABLE anti-spam code
because I just want virus checking. I see this in my log on startup:
Sep 6 13:50:46 hedwig amavis[15431]: ANTI-SPAM codeNOT loaded
but I still get these headers when I
tir, 06.09.2005 kl. 14.50 skrev Gregory Mokhin:
> I've got a mail server where mostly spam in Russian is coming. It
> never gets through SpamAssassin. There is nothing special in
> SpamAssassin rules to block it - it just works. Make sure if
> everything is fine with your installation and bayes da
Hi,
Something I did in the wee hours of the morning fixed it. Spam is now
sent to /var/spool/amavis/virusmails/ At some point it was gzipping
the mails too!
$spam_quarantine_to = 'spam-quarantine';
The only part that still bothers me is I'd like to keep the spam and
virus mai
Hi Mike,
I've got a mail server where mostly spam in Russian is coming. It
never gets through SpamAssassin. There is nothing special in
SpamAssassin rules to block it - it just works. Make sure if
everything is fine with your installation and bayes database. If you
need a bunch of Russian spam mes
Hi,
This morning I have several enteries like following in /var/log/syslog
==
Sep 6 01:03:20 mailgate1 amavis[363]: [ID 702911 mail.error] (00363-07)
TROUBLE in check_mail: parts_decode_ex
t FAILED: run_command (open pipe): Can't fork at
/usr/local/lib/perl
tir, 06.09.2005 kl. 12.07 skrev Mark Martinec:
> > Hmmm ... I do that with Postfix header_ and mime_header_check PCRE
> > content filters in cleanup, after all the amavisd-new filtering.
> > amavisd-new discards only 8-bit non-mime shit (and does it very well,
> > Postfix doesn't).
>
> Postfix he
Tonni,
> Hmmm ... I do that with Postfix header_ and mime_header_check PCRE
> content filters in cleanup, after all the amavisd-new filtering.
> amavisd-new discards only 8-bit non-mime shit (and does it very well,
> Postfix doesn't).
Postfix header/body/mime-header checks are (and should) normal
> ... should quarantine spam above $sa_kill_level_deflt unless something
> else in the config is not set right, or it is not able to write a
> file due to permission problems
Just a general comment: errors encountered by amavisd-new do not get
silently ignored: if there was a file protection probl
Amavis setup was working just fine for about a week after switching from
amavis-milter to Petr's amavisd-milter, then earlier today all of a sudden
I noticed no mail was coming in, look in the logs and I see this...
Sep 6 00:53:10 stage2 amavisd-milter[10209]: j867qwKD010376: mlfi_eom:
could not
23 matches
Mail list logo
