Zimbra generates large mailbox.log files

[phoenix]

Do you have a firewall and/or SElinux (AppArmor) active on the zimbra server? On the Zimbra server can you do the following:

telnet localhost 53
telnet localhost 25

Do you get a response from either of those?

su - zimbra 
zmcontrol status

Is everything running OK?

Please post the output of the following commands (run on the Zimbra server):

cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname`

[Peperzaken]

Originally Posted by phoenix

Do you have a firewall and/or SElinux (AppArmor) active on the zimbra server? On the Zimbra server can you do the following:

telnet localhost 53
telnet localhost 25

Do you get a response from either of those?

root@zimbra:/opt/zimbra/log# telnet localhost 53
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
root@zimbra:/opt/zimbra/log# telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 zimbra.peperzaken.nl ESMTP Postfix

su - zimbra 
zmcontrol status

Is everything running OK?

Yes, everything is running OK.

Please post the output of the following commands (run on the Zimbra server):

cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname`

/etc/hosts:

root@zimbra:/# cat /etc/hosts
127.0.0.1	localhost
10.0.0.175	zimbra.peperzaken.nl	zimbra
# 10.0.0.175	mail.peperzaken.nl	mail

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

/etc/resolv.conf:

root@zimbra:/# cat /etc/resolv.conf
nameserver 10.0.0.175
search zimbra.peperzaken.nl
// nameserver 193.74.208.65
// nameserver 213.51.129.37
// nameserver 213.51.144.37

dig zimbra.peperzaken.nl:

root@zimbra:/# dig zimbra.peperzaken.nl mx

; <<>> DiG 9.3.2 <<>> zimbra.peperzaken.nl mx
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig zimbra.peperzaken.nl any:

root@zimbra:/# dig zimbra.peperzaken.nl any

; <<>> DiG 9.3.2 <<>> zimbra.peperzaken.nl any
;; global options:  printcmd
;; connection timed out; no servers could be reached

host `hostname`:

root@zimbra:/# host `hostname`

;; connection timed out; no servers could be reached

[phoenix]

Sorry, my mistake. Your hosts file should also have the localhost formatted like this:

127.0.0.1 localhost.localdomain localhost

The dig command should be for the domain and not the FQDN of the server as per the following:

dig peperzaken.nl mx

[Peperzaken]

First of all, sorry for the late reply.

Originally Posted by phoenix

Sorry, my mistake. Your hosts file should also have the localhost formatted like this:

127.0.0.1 localhost.localdomain localhost

Fixed.

The dig command should be for the domain and not the FQDN of the server as per the following:

dig peperzaken.nl mx

dig peperzaken.nl mx:

root@zimbra:/etc/bind# dig peperzaken.nl mx

; <<>> DiG 9.3.2 <<>> peperzaken.nl mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 22904
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;peperzaken.nl.                 IN      MX

;; Query time: 1 msec
;; SERVER: 10.0.0.175#53(10.0.0.175)
;; WHEN: Wed Dec  3 16:59:03 2008
;; MSG SIZE  rcvd: 31

This is the output of the dig command with 10.0.0.1 (the IP of the router) as forwarder in the bind setup and 10.0.0.175 as the only nameserver defined in /etc/resolv.conf. With this configuration the output of the host command is the following:

root@zimbra:/etc/bind# host `hostname`
Host zimbra.peperzaken.nl not found: 2(SERVFAIL)

When I define the IP 10.0.0.1 as nameserver in /etc/resolv.conf the dig command gives the status "NOERROR" and the host command gives the external IP.

What can I do now to fix all this?

[Peperzaken]

OK, I think I fixed the problem with the DNS:

root@zimbra:/etc/bind# host `hostname`
zimbra.peperzaken.nl has address 10.0.0.175

dig peperzaken.nl mx:

root@zimbra:/etc/bind# dig peperzaken.nl mx

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

;; QUESTION SECTION:
;peperzaken.nl.                 IN      MX

;; ANSWER SECTION:
peperzaken.nl.          604800  IN      MX      10 zimbra.peperzaken.nl.

;; AUTHORITY SECTION:
peperzaken.nl.          604800  IN      NS      10.0.0.175.peperzaken.nl.

;; ADDITIONAL SECTION:
zimbra.peperzaken.nl.   604800  IN      A       10.0.0.175

;; Query time: 1 msec
;; SERVER: 10.0.0.175#53(10.0.0.175)
;; WHEN: Wed Dec  3 19:05:46 2008
;; MSG SIZE  rcvd: 95

dig peperzaken.nl any:

root@zimbra:/etc/bind# dig peperzaken.nl any

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

;; QUESTION SECTION:
;peperzaken.nl.                 IN      ANY

;; ANSWER SECTION:
peperzaken.nl.          604800  IN      SOA     zimbra.peperzaken.nl. admin.peperzaken.nl. 70725 604800 86400 2419200 604800
peperzaken.nl.          604800  IN      NS      10.0.0.175.peperzaken.nl.
peperzaken.nl.          604800  IN      A       10.0.0.175
peperzaken.nl.          604800  IN      MX      10 zimbra.peperzaken.nl.

;; ADDITIONAL SECTION:
zimbra.peperzaken.nl.   604800  IN      A       10.0.0.175

;; Query time: 1 msec
;; SERVER: 10.0.0.175#53(10.0.0.175)
;; WHEN: Wed Dec  3 19:07:31 2008
;; MSG SIZE  rcvd: 153

Does this looks correct? The solution was to fix the incorrect zone file defined in the bind configuration. Should this be the solution for the original problem?