salocal.cf vs. local.cf

[olecoot]

Please don't flame ...

Can someone explain to me when I would adjust /opt/zimbra/conf/salocal.cf.in as opposed to /opt/zimbra/conf/spamassassin/local.cf? I've placed blacklisted domains in the salocal.cf.in and all seems to be working fine. But in researching some future spam control I have seen where it has been advised to configure local.cf, then in other posts the salocal.cf.in. I am thoroughly confused.

Is there documentation that explains the function of the two files?

Thank you.

[uxbod]

An alternative is to create you own .cf eg. company.cf under /opt/zimbra/conf/spamassassin. You will then retain your changes across upgrades. Spamassassin will automagically source in your own .cf.

[olecoot]

Originally Posted by uxbod

An alternative is to create you own .cf eg. company.cf under /opt/zimbra/conf/spamassassin. You will then retain your changes across upgrades. Spamassassin will automagically source in your own .cf.

Thank you for your quick reply. I read your suggestion in another post. Would this work if I were using the server to host multiple domains? Would I use a "domain.cf" for each domain on the server or is that where the salocal and local files come into play?

[uxbod]

Changes would apply to all domains as SpamAssassin is not domain specific within Zimbra.

[olecoot]

Originally Posted by uxbod

Changes would apply to all domains as SpamAssassin is not domain specific within Zimbra.

I will give it a try. Thank you.