Improving antispam

[wooby]

Hello ALl
CAn anybody tell me if you have done according to Improving Anti-spam system - Zimbra :: Wiki
to block a particluar email address ?

Can you tell me if editing the salocal.cf.in can cause any issues?

I really waiting for valuable replies.
Thanks in anticiaption

[GWilliams]

Hi Wooby,

We have implemented postgrey according to Improving Anti-spam system - Zimbra :: Wiki and it has made a dramatic improvement...

Unfortunately, I can't comment on editing salocal.cf.in, as I have not done so myself on Zimbra, but I would try a greylisting solution first.

All the best.

[wooby]

CAn anybody help on implications n editing salocal.cf.in

[uxbod]

No problem in modifying salocal.cf.in as long as you keep a record of the changes; as the file can be overwritten on a upgrade.

[wooby]

Was not sure if any issues wud come up.Thanks for the help here.

[uxbod]

I guess that depends on what you are planning to change

[wooby]

user receving spam mail from a particluar ID with various contents. user moved it to JUNK still it is coming to his Inbox. So wanted to block that email ID by trying according to the wiki by adding entry:

blacklist_from sales@traveloforange.com to salocal.cf.in

Thanks

[ewilen]

Note: if you upgrade to ZCS 6, there's a user-configurable blacklist under preferences in ZWC.

That said, when I was asked to blacklist mail from a particular address under ZCS 5, I did the following (modified per your example):

As root:

cd /opt/zimbra/conf
cp amavisd.conf.in amavisd.conf.in.bak
vi amavisd.conf.in

Now in the section following the line # soft-blacklisting (positive score) I add this:

'sales@traveloforange.com' => 15.0,

This should be enough to cause anything from that address to be dropped altogether if it's at all spammy (assuming kill percent is set to 75). If other characteristics of the mail generate a negative total, then the message will go into Junk.

Then, as zimbra, do zmamavisdctl stop && zmamavisdctl start . Note, the && means "do the second command if the first command exits successfully".

Finally, look in amavisd.conf and confirm that the change has gone into it.

Not sure why I did it that way, but it worked. The modification to salocal.conf.in is simpler of course and it might also work; you'll just have to restart some part of Zimbra when you make a change to one of the *.conf.in files. For salocal.conf.in zmmtactl restart should be sufficient but you might need to do zmamavisdctl restart if the *.conf file isn't updated.

[wooby]

That was Great help. Let me do accordingly and will update soon.