upgrade 4.5.7 > 5.0.2 problem

[owl700]

Hi, i have upgrade from 4.5.7 to 5.0.2 and all is ok but if i try enable dns control and protocol control in mta global setting from admin panel when i exit and enter again in admin panel the checks are blank. I have click save, why i can't enable protocol and dns control?
I have installed zimbra on ubuntu server 6.0.6.
Thanks

[phoenix]

What, exactly, are you trying to do? Are you able to send & receive mail or do you have any errors in the logs? Does your server have valid A & MX DNS records? Run the following on your zimbra server:

host `hostname`  <-- type 'as-is' & use backticks not single quotes
dig yourdomain.com mx
dig yourdomain.com any

and post the results.

[owl700]

Hi, my server is running well from 2007, 1 month ago i have upgraded to 5.0.2 and always all running well.

hostname
> mail.mydomain.com
hostname -f
> mail.mydomain.com
hostname mail.mydomain.com
> mail.mydomain.com has address myserverip

----

dig mydomain.com mx

; <<>> DiG 9.3.2 <<>> mydomain.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58643
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;mydomain.com. IN MX
;; ANSWER SECTION:
mydomain.com. 604800 IN MX 10 mail.mydomain.com.
;; AUTHORITY SECTION:
mydomain.com. 604800 IN NS mail.mydomain.com.
;; ADDITIONAL SECTION:
mail.mydomain.com. 604800 IN A myserverip
;; Query time: 2 msec
;; SERVER: myserverip#53(myserverip)
;; WHEN: Sat Mar 22 14:12:24 2008
;; MSG SIZE rcvd: 81

----

dig mydomain.com any

; <<>> DiG 9.3.2 <<>> mydomain.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58545
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;mydomain.com. IN ANY
;; ANSWER SECTION:
mydomain.com. 604800 IN SOA mail.mydomain.com. me.mydomain.com. 200801011 604800 86400 2419200 604800
mydomain.com. 604800 IN NS mail.mydomain.com.
mydomain.com. 604800 IN MX 10 mail.mydomain.com.
mydomain.com. 604800 IN A myserverip
;; ADDITIONAL SECTION:
mail.mydomain.com. 604800 IN A myserverip
;; Query time: 4 msec
;; SERVER: myserverip#53(myserverip)
;; WHEN: Sat Mar 22 14:15:47 2008
;; MSG SIZE rcvd: 139

i want check the checkboxes in the admin MTA reject_invalid_hostname, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_unknown_client, reject_unknown_hostname and reject_unknown_sender_domain

if i check these checkboxes i logout and i login again the checks are again blanks.
I want enable these controls for reduce spam.

[Bill Brock]

I have the same issue. I check the six boxes in the global settings but the next time I login they are unchecked. It does appear, however, that the parameters are active as the server will reject any mail from a PC not adhereing to the rules.

[owl700]

Can you say me where can i show the active parameters?
Thanks

[phoenix]

Originally Posted by owl700

Can you say me where can i show the active parameters?
Thanks

You can list the restrictions by running the following command as the zimbra user:

zmprov gacf | grep zimbraMtaRestriction

Run that command then make a change to one of the settings in the Admin UI and see if it gets changed by running that command again. You should then logout/login and see if the settings are still in the admin ui and also check the setting by running the above command again. If you still have the problem of the option not 'sticking; in the admin ui then pleae check bugzilla for any outstanding reports and file a new bug if you don't find one.

[phoenix]

BTW, I have to ask the obvious question - you did hit the save button when you checked those options didn't you? I'm not seeing this behaviour on my own 5.0.3 server, marking any of those options then doing a logout/login still leaves them enabled.

[owl700]

Originally Posted by phoenix

BTW, I have to ask the obvious question - you did hit the save button when you checked those options didn't you? I'm not seeing this behaviour on my own 5.0.3 server, marking any of those options then doing a logout/login still leaves them enabled.

Sure always i pressed save

[owl700]

Originally Posted by phoenix

You can list the restrictions by running the following command as the zimbra user:

zmprov gacf | grep zimbraMtaRestriction

Run that command then make a change to one of the settings in the Admin UI and see if it gets changed by running that command again. You should then logout/login and see if the settings are still in the admin ui and also check the setting by running the above command again. If you still have the problem of the option not 'sticking; in the admin ui then pleae check bugzilla for any outstanding reports and file a new bug if you don't find one.

I have try to change values (and press save) and when i send via console zmprov gacf | grep zimbraMtaRestriction i receive always:

zimbra@mail:/root$ zmprov gacf | grep zimbraMtaRestriction
zimbraMtaRestriction: reject_invalid_hostname
zimbraMtaRestriction: reject_non_fqdn_sender

there is no way to enable the others controls ord disable reject_invalid_hostname and reject_non_fqdn_sender, can i enable the DNS and MTA controls in some manner?

[mmorse]

Originally Posted by owl700

there is no way to enable the others controls ord disable reject_invalid_hostname and reject_non_fqdn_sender, can i enable the DNS and MTA controls in some manner?

Enable:
zmprov mcf +zimbraMtaRestriction [value]
Disable:
zmzmprov mcf -zimbraMtaRestriction [value]

You can also run just the one's you want all on one line:

so to set all something like:
zmprov mcf zimbraMtaRestriction reject_invalid_hostname zimbraMtaRestriction reject_non-fqdn_hostname zimbraMtaRestriction reject_non_fqdn_sender zimbraMtaRestriction “reject_rbl_client dnsbl.njabl.org” zimbraMtaRestriction “reject_rbl_client cbl.abuseat.org” zimbraMtaRestriction “reject_rbl_client bl.spamcop.net” zimbraMtaRestriction “reject_rbl_client dnsbl.sorbs.net” zimbraMtaRestriction “reject_rbl_client zen.spamhaus.org”

Protocol checks:
reject_invalid_hostname
reject_non_fqdn_hostname
reject_non_fqdn_sender

DNS checks:
reject_unknown_client
reject_unknown_hostname
reject_unknown_sender_domain