Sébastien,
> Feb 25 18:24:49 serverA amavis[28006]: (28006-01) body type: unlabeled,
> but 8-bit header (h=1, b=0)
> Feb 25 18:24:49 serverA amavis[28006]: (28006-01) body hash:
> fa3e690a09535a8d0c9890746fd4a937
> Feb 25 18:24:49 serverA amavis[27936]: Net::Server: Starting "1" children
Tha
Aaron,
> It appears as if the anti-virus program is always called before
> SpamAssassin. Is that in fact correct?
Right.
> If so, is there a means to change the order (e.g., to call SA first,
> then only call AV if the message is not deemed to be spam)?
No. The order is officially unspecified
At this point, my amavisd-new install (2.5.3 on Centos5) is not working
correctly. Perhaps the problem I am having is a bug, as I have a very similar
installation elsewhere that does work.
I have amavisd setup to use a Pgsql database for lookups:
@lookup_sql_dsn = ( ['DBI:Pg:dbname=postfix', '
Hi,
2008/2/25, Temin, Aaron L. <[EMAIL PROTECTED]>:
>
>
> Hi.
>
> It appears as if the anti-virus program is always called before
> SpamAssassin. Is that in fact correct? If so, is there a means to
> change the order (e.g., to call SA first, then only call AV if the
> message is not deemed t
Hi.
It appears as if the anti-virus program is always called before
SpamAssassin. Is that in fact correct? If so, is there a means to
change the order (e.g., to call SA first, then only call AV if the
message is not deemed to be spam)?
Thank you very much.
Aaron
Aaron Temin
The MITRE Corporat
Feb 25 18:24:06 serverA amavis[27916]: logging initialized, log level 5,
syslog: amavis.mail
Feb 25 18:24:06 serverA amavis[27916]: starting. /usr/sbin/amavisd at
serverA.toto.com amavisd-new-2.5.3 (20071212), Unicode aware,
LANG="en_US.UTF-8"
Feb 25 18:24:06 serverA amavis[27916]: user=102, EUI
Feb 25 18:24:06 serverA amavis[27916]: logging initialized, log level 5,
syslog: amavis.mail
Feb 25 18:24:06 serverA amavis[27916]: starting. /usr/sbin/amavisd at
serverA.toto.com amavisd-new-2.5.3 (20071212), Unicode aware,
LANG="en_US.UTF-8"
Feb 25 18:24:06 serverA amavis[27916]: user=102, EUI
Sébastien,
> Since 2 or 3 weeks we have problem with amavisd-new on postfix. We got
> several lines like this :
> (!)_DIE: Suicide in child_init_hook: BDB no dbS: Lock table is out of
> available locker entries, . at (eval 51) line 30.\n
Which version of libdb? It is reported at amavisd startup,
Mark Martinec wrote:
> ...
> With mailman for example, one could do (in Mailman/mm_cfg.py):
> SMTPHOST = 'localhost'
> SMTPPORT = 10025
> ...
>
Excellent. That's the kind of simple answer I've been looking for.
Cheers.
Coops.
--
Coops,
> I successfully altered the Debian default settings to include scanning
> of relayed mail (by scanning all outgoing mail). However the problem
> which now occurs is that all mail sent to the public mailing lists is
> being checked, and causing a huge load on the server when ever a single
>
Since 2 or 3 weeks we have problem with amavisd-new on postfix. We got
several lines like this :
(!)_DIE: Suicide in child_init_hook: BDB no dbS: Lock table is out of
available locker entries, . at (eval 51) line 30.\n
And we must restart amavisd because our spools keep on growing and
growing i
Hi people I'm new to the list and to the linux servers world. I'm building a
mail relay server using Postfix, Amavisd-new, Spam Assassin, Razor and SophosAV
on a Slackware 9.
The postfix version is 2.4.6, the amavisd-new version is 2.5.3.
The problem is the following, when I call the "amavisd s
Hi,
I'm looking for some advice on bypassing spam checking for a mailman
mailing list.
I've started hosting the email for a public announcement mailing list of
~1300+ recipients. I had amavis running on Debian (stable) with postfix,
and successfully checking mail destined for the machine.
But I
13 matches
Mail list logo
