[SOLVED] No SPAM check when mail is "transported"

[uxbod]

I believe $mydomain should be set to ''. And then the code should say it is local

my($is_local) = lookup2(0,$recip, ca('local_domains_maps'));
      $is_local ? $cnt_local++ : $cnt_remote++;

[moren]

Ops, i missed this forum entry (busy typing).

The $mydomain is set to 'molud2.hh.se' and this is the hostname of the test-gateway-machine.
I noticed that this entry is empty on the production machine...

[uxbod]

Set that entry to blank in /opt/zimbra/conf/amavisd.conf.in and then restart.

[moren]

I just did this and *YES*, it works. Now the headers is added. Very good indeed!!!

I do not remember (quite sure) that we have modified this in our production server...

I noticed that this entry (in amavisd.conf.in) is set by @@av_notify_domain@@ and this can be found in zmlocalconfig, ie

$ zmlocalconfig | grep av_notify_domain
av_notify_domain = molud2.hh.se

Can I set this in the admin-GUI someware ?
or modify it with zmlocalconfig ?
Can this give other side-effects?

Any thoughts?

I prefer to do this because then it is more likely that this survives future updates.

[uxbod]

You can change it with

su - zimbra
zmlocalconfig -e av_notify_domain=''

or to remove it complete

su - zimbra
zmlocalconfig -u av_notify_domain

It would appear that on install it is set to the initial domain; and on a upgrade it pulls it from the current running config. Looking at another ZCS6 install it is not actually set which surprises me.

[uxbod]

Has the test mail gateway that you upgraded ever been a mailstore as-well ?

[moren]

Yes, we have the mail-store rpm installed at this machine also. I think the reason was to get av/as graphs at this machine OR to get the spam.* and ham.* accounts created. I do not remember the exact reason.

We also forwards spam/ham from users to the gateway machine to train SA.

[uxbod]

The mail-store rpm is not required on a front-end gateway. As you are not running a true multi-server setup then you could look at moving the SA Bayes from file based to either MySQL or PostgresSQL. That way whether the server is Zimbra or ANother you can make use of the shared Bayes.

[moren]

That is another way to get the same behavior I suppose. I will look into that in future setup. Thank you for the suggestion.

... and thank you for your excellent help and suggestions. It was really helpful.


Best regards

[moren]

FYI: We have now successfully updated our production server to 6.0.6 (from 5.0.9).

Prior to the update the av_notify_domain was not defined.

After the update it was set to the default domain (==fqdn of host) and we had to apply the fix above, ie: zmlocalconfig -e av_notify_domain=''