Enabling SpamAssassin

[ekmeek]

When we initially installed ZCS we did not enable the spam or virus features as we had an external device doing this. We've recently thought about spamassassin only in Zimbra, so I thought I'd try it out in our test environment.

Like our production environment, our test environment is a multi-server setup.

Via the admin web interface, I enabled the spamassassin service for both mta's. I then had to run zmspamctl start on each of the mta's.

When I attempt to send an email from one internal account to another internal account it's being deferred and I'm finding this in the logs:

Jun 22 12:29:20 mta1 amavis[1931]: (!)DENIED ACCESS from IP 192.168.1.234, policy bank ''

Any idea what could be causing this?

[ekmeek]

Solution:

On our mta's we have postfix bound to their internal ip's:

smtp_bind_address = 192.168.1.234

In amavisd.conf.in we had to add the bolded line below:

$policy_bank{'MYNETS'} = {
originating => 1,
allow_disclaimers => %%binary VAR:zimbraDomainMandatoryMailSignatureEnabled%%,
log_level => 1,
@inet_acl = qw( 127.0.0.1 192.168.1.0/24 ),
};

[ekmeek]

And how does one mark posts solved? I swear I did it once but can't see where.

[Jose12]

Do you need to create an account for it.

[ekmeek]

To enable spamassassin?

In the web admin interface, I went to Configuration-->Services. Selected my mta's and under the Services tab selected Anti-Spam.

[phoenix]

Originally Posted by ekmeek

And how does one mark posts solved? I swear I did it once but can't see where.

It's a minor hiccup with a recent forum software upgrade, it will magically reappear.