[SOLVED] Disclaimer problem after upgrade to zcs 5.0.13

[rajeshkodali]

smtp inet n - n - - smtpd
### KASPERSKY ANTI-SPAM BEGIN ###
-o content_filter=kas3scan:127.0.0.1:9026
### KASPERSKY ANTI-SPAM END ###
-o content_filter=dfilt:
dfilt unix - n n - - pipe
flags=Rq user=zimbra argv=/opt/zimbra/postfix/conf/disclaimer -f ${sender} -- ${recipient}


Now from zimbra 5.0.13 edition I think this file is generated from zmmta.cf so should I back up my original file as master.cf.in so that the disclaimer works ???

[uxbod]

All changes should be made to master.cf.in, which is the base file, once you restart ZCS it will re-write master.cf. So if you made changes directly to master.cf on restart they would be over-written.

[russgalleywood]

Hi Guys,

help,

have just overwritten the master.cf.in file as instructed with my disclaimer version and now I get Server errors!

We were on 5.0.9 for a long time and on this I would simply overwrite the master.cf with our one when updating Zimbra.

Please could someone quickly run me through the basic permission son these files and tell me what I am doing wrong!

When I run zmmtactl restart after alterations I get;

Rewriting configuration files...done.
Stopping zmmtaconfig...done.
Starting zmmtaconfig...done.
postfix/postfix-script: fatal: the Postfix mail system is not running
Stopping saslauthd...done.
Starting saslauthd...done.

Help please!!

Thanks Russ

[uxbod]

master.cf.in could change between versions of ZCS! so you should never keep a old one and just overwrite it ... easiest way is to keep the code required in a seperate block that you can just merge in to the latest file. What errors are being shown in /var/log/zimbra.log on startup ?

[russgalleywood]

Hi Uxbod,

it's OK, I backed up the old version first before replacing so I have just switched back but would still like to get our Disclaimer up and running.

So it may have been that there has been significant changes to the master.cf.in in recent version you mean?

Previously, over about 5 updates I have simply replaced the master.cf with my altered version and away we go.

Whilst running with the altered version the mail would be held and in the Admin Console if I hovered over a held mail it would tell me that permission was denied to the dfilt: in my altered code.

There is no faults in my var/log/zimbra file.

When making the alterations I would simply stop and start the zmmtactl service.

I'll make the alteration to the master.cf.in manually and carefully but am just wondering if I have inadvertently changed permission on something I shouldn't have?!

Lastly,

have tried the Admin Disclaimer zimlet on CentOS 5 but have always found this to appear corrupted on screen, sorry, I know this isn't the Zimlet thread but has anyone else had trouble with this?

CentOS5, Zimbra 5.0.14.

Thanks
Russ

[uxbod]

You can always run, as root, /opt/zimbra/libexec/zmfixperms to make sure all the permissions are okay.

[russgalleywood]

Ah yes, of course!

You must get really sick of telling people about that one!

Apologies.

One other thing then that you have probably also heard many times!
Is there any way to stop Zimbra overwriting my disclaimer version on each upgrade?

I was hoping that was the purpose of the master.cf.in file, is this not the case?

Thanks Uxbod, helpful as always.

[uxbod]

Unfortunately no as these files are distributed with the upgrade, which in effect is a complete new install package. I tend to create a .diff with my changes in so that when I need to apply again I can just run it through patch. That way if it does change the patch will not apply and I can check the new version.

[russgalleywood]

Thanks Uxbod,

I'll do this.