Hello!
Im new here, using amavis, happy with it, but have now the following
Problem.
I don't want to have my /tmp Directory with permissions 777. But when I
give /tmp a owning Group of the amavis user and permissions 775, I get:
Aug 7 15:00:19 hostname amavis[23970]: (23970-05) (!!) TROUBLE i
Stefan,
> Yes, but I've thought, that amavisd-new can set a recipient address
> as "user" (e.g. via a "User:" header I've read about). But you are
> right - when a message is scanned only once regardless of number of
> recipients, this does not make much sense.
If you let MTA do the splitting and
> >
>
> What version of amavisd-new? Requires 2.5.0 or newer.
>
> --
> Gary V
>
Still amavisd-new-2.4.4-4 and spamassassin-3.1.7-3
Need to upgrade uh... :)
Is there any changes in amavisd.conf and local.cf I need to be aware of
upgrading to amavisd-new-2.5.2-4 and spamassassin-3.2.2-1 (Ander
> With amavisd-new, the $daemon_user is what SpamAssassin sees. It sees
> no other users when called by amavisd-new. You won't find a howto.
Yes, but I've thought, that amavisd-new can set a recipient address
as "user" (e.g. via a "User:" header I've read about). But you are
right - when a messa
Just thought I would tell a little story that happened to me recently.
Virus scanning stopped working after my last config change. Unfortunately I
did not notice it until quite a while later all the while virus scanning was
not getting envoked. Nothing bad happened because I have virus scanning o
On 8/7/07, Stefan Palme wrote:
>
> Hi,
>
> I have a "classical" setup using postfix + amavisd-new + SA to
> check for spammy email. Amavisd is using an SQL database for storing
> individuall policies, white-/blacklists etc. per recipient (using the
> @lookup_sql_dsn feature for this).
>
> Now some
Hi,
I have a "classical" setup using postfix + amavisd-new + SA to
check for spammy email. Amavisd is using an SQL database for storing
individuall policies, white-/blacklists etc. per recipient (using the
@lookup_sql_dsn feature for this).
Now some users want to modify the scores for some of t
On 8/7/07, Leon Kolchinsky <[EMAIL PROTECTED]> wrote:
> > Hello All,
> >
> > I've installed on my mail server SaneSecurity and MSRBL signatures and
> > made
> > a little reference for my own use during this installation.
> >
>
> Following my own post:
>
> I've sent phish_sigtest and scam_sigtest fi
Hello list,
I'm running a server with postfix 2.4.3, amavis 2.5.2 and clamav 0.91.1.
Yesterday I send the testmessage sample-42-mail-bomb.txt from the amavisd-new
package through my mailsystem and got the following:
Aug 6 14:24:19 server amavis[22492]: (22492-03)
LMTP::10024 /var/amavis/tmp/am
Does anyone have any insight into this?
I also have some additional information. Postfix was recently upgraded
to 2.4.4 (from 2.2.x), are there relevant postfix configuration
variables that may have changed? I can provide complete amavis and
postfix configurations upon request. Thanks. -- Joel
> Hello All,
>
> I've installed on my mail server SaneSecurity and MSRBL signatures and
> made
> a little reference for my own use during this installation.
>
Following my own post:
I've sent phish_sigtest and scam_sigtest files as an attachements to one of
my mail accounts.
These mails detecte
Dear Mark,
The thing is, that we have a big farm of amavisd-new machines connected
by CARP in one AV/AS cluster (about 30 boxes, and growing), and it serves
for many, many smtp boxes. With this patch we found it very useful and
easy to manage what does amavisd-new do with the mail received from
Hello All,
I've installed on my mail server SaneSecurity and MSRBL signatures and made
a little reference for my own use during this installation.
Please comment or suggest fixes of the following:
-
Steps to install SaneSecurity and MSRBL signature
13 matches
Mail list logo
