[SOLVED] Problems receiving mail with Zimbra

[jsr]

Hello,

i really hope anyone can help me out with this (little) problem i experience after my zimbra installation

the installation went fine. After the installation i am able to login to both webmail and the ZimbraAdmin page (both using my domain).

Sending mail is no problem. mails are send fine (tested it at several mail addresses).

i am however unable to retrieve any mail at user made in zimbra.

i will post some details:

tail /var/log/zimbra

Jul 26 18:54:24 mail zimbramon[2364]: 2364:info: 2009-07-26 18:54:02, STATUS: mail.jsr-domain.nl: snmp: Running
Jul 26 18:54:24 mail zimbramon[2364]: 2364:info: 2009-07-26 18:54:02, STATUS: mail.jsr-domain.nl: spell: Running
Jul 26 18:54:24 mail zimbramon[2364]: 2364:info: 2009-07-26 18:54:02, STATUS: mail.jsr-domain.nl: stats: Running
Jul 26 18:54:37 mail postfix/qmgr[7656]: A36AACD054D: from=<forums@zimbra.com>, size=3190, nrcpt=1 (queue active)
Jul 26 18:54:37 mail postfix/qmgr[7656]: B48CBCD0385: from=<zimbra@mail.jsr-domain.nl>, size=1110, nrcpt=1 (queue active)
Jul 26 18:54:37 mail postfix/qmgr[7656]: E59C2CD035E: from=<zimbra@mail.jsr-domain.nl>, size=1108, nrcpt=1 (queue active)
Jul 26 18:54:37 mail postfix/lmtp[2600]: A36AACD054D: to=<joeri@jsr-domain.nl>, relay=none, delay=2358, delays=2358/0.23/0.01/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=mail.jsr-domain.nl type=A: Host not found, try again)
Jul 26 18:54:37 mail postfix/lmtp[2601]: B48CBCD0385: to=<admin@mail.jsr-domain.nl>, relay=none, delay=11080, delays=11080/0.13/0/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=mail.jsr-domain.nl type=A: Host not found, try again)
Jul 26 18:54:37 mail postfix/lmtp[2600]: E59C2CD035E: to=<admin@mail.jsr-domain.nl>, relay=none, delay=11079, delays=11079/0.27/0/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=mail.jsr-domain.nl type=A: Host not found, try again)
Jul 26 18:55:07 mail clamd[6712]: SelfCheck: Database status OK.


zimbra@mail:/var/log$ more /etc/hosts
127.0.0.1 localhost.local localhost
127.0.1.1 mail.local mail
192.168.178.106 mail.jsr-domain.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


root@mail:/var/log# nslookup mail.jsr-domain.nl
;; connection timed out; no servers could be reached

root@mail:/var/log# hostname
mail.jsr-domain.nl

root@mail:/var/log# hostname -f
mail.jsr-domain.nl


DNS Information for 'jsr-domain.nl'

Zone Info: jsr-domain.nl
Info Type Message
Information jsr-domain.nl./80.101.39.114 is located in Netherlands (NL)
Information Zimbra Collaboration Suite Log In resolves to 80.101.39.114
Information 5 seconds to complete zone checks.

Parent Name Servers

This section lists the hierarchy of name servers that a DNS lookup needs to walk to find your zone's name servers. For brevity only one name server is listed per zone.
Zone Name Server IP Location Response Time (ms)
nl. nl1.dnsnode.net 194.146.106.42 Sweden 0
. a.root-servers.net 198.41.0.4 United States 0
jsr-domain.nl Name Servers
Zone Configuration Info
Info Type Message
Information Setting the master name server to 'ns1.netground.nl' per the SOA record on ns1.netground.nl
Zone Configuration (SOA Record)

The Statement of Authority Record describes the primary name server. It is usually used by secondary name servers as an aid to keep their information synchronized with the primary name server. And it is used by independent name servers as a guide for how long to cache DNS lookup results.

Primary Name Server ns1.netground.nl
DNS Host Master hostmaster.netground.nl
Secondary Refresh 4 hours
Secondary Retry 1 hour
Secondary Expire 1 week
Default Record Cache Time 1 day
Serial Number 2009072504

SOA Info

Heads-up SOA default TTL is set to 1 day. The recommended setting is between 1 and 3 hours (3600 seconds and 10800 seconds).

Heads-up SOA expire is set to 1 week. The recommended length is between 2 and 4 weeks (1209600 seconds and 2419200 seconds).
Information The serial number for this domain is 2009072504. This looks like format recommended by RFC1912 of YYYYMMDDnn where nn is the daily revision number.

Information SOA retry time is set to 1 hour. This is the time a nameserver will wait before trying to contact the master server after a failure. It should be more than 2 minutes, but not more than a few hours.
ns1.netground.nl Name Server

Name ns1.netground.nl
IP Address 87.250.129.129
Location Netherlands
Response Time 135ms

Name Server Info

Information The name server did not return any records after our AXFR request. This is quite normal.

Information This name server returns the following DNS records for

'jsr-domain.nl': '50 jsr-domain.nl. (MX)'
ns2.netground.nl Name Server
Name ns2.netground.nl
IP Address 87.233.146.129
Location Netherlands
Response Time 165ms

Name Server Info
Information The name server did not return any records after our AXFR request. This is quite normal.

Information This name server returns the same DNS records for 'jsr-domain.nl' as the 'ns1.netground.nl/87.250.129.129' name server.
ns3.netground.nl Name Server
Name ns3.netground.nl
IP Address 213.222.24.129
Location Netherlands
Response Time 139ms

Name Server Info

Information The name server did not return any records after our AXFR request. This is quite normal.

Information This name server returns the same DNS records for 'jsr-domain.nl' as the 'ns1.netground.nl/87.250.129.129' name server.

Mail Servers
Mail Server Info
Info Type Message
Information You have 2 mail servers listed for your 'jsr-domain.nl' domain.

Mail Server: mail.jsr-domain.nl

Server Name mail.jsr-domain.nl
IP 80.101.39.114

Location Netherlands
Mail Server For *@jsr-domain.nl
MX Priority 10
Connect Response Time 1323ms

Server 'Hello' Line 220 mail.jsr-domain.nl ESMTP Postfix
Open Relay? No Problems Found
RDNS Entry a80-101-39-114.adsl.xs4all.nl.

Mail Server Info

Heads-up The mail server rejected the email address 'abuse@jsr-domain.nl' (550 5.1.1 <abuse@jsr-domain.nl>: Recipient address rejected: jsr-domain.nl). It should have accepted the address.

Information The mail server correctly rejected email to 'email_validation_service@domaincheckingservice.pi ngability.com' (554 5.7.1 <email_validation_service@domaincheckingservice.pi ngability.com>: Relay access denied)



root@mail:/var/log# vi /etc/bind/named.conf
// This is the primary configuration file for the BIND DNS server named.


options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
forwarders { 87.250.129.129 ; };
};
include "/etc/rndc.key";
// We are the master server for server.example.com
zone "mail.jsr-domain.nl" {
type master;
file "db.mail.jsr-domain.nl";
};


// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
type master;
file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";


if more information is wanted i will post it.
Im really on the edge off dispair (so close but still not there)

thnaks for any help

Joeri

[phoenix]

This problem has been covered many times in the forums. The first this is your hosts file is incorrect, it should only contain the following:

127.0.0.1 localhost.localdomain localhost
192.168.178.106 mail.jsr-domain.nl mail

Make that change then post the output of the following commands (run on the Zimbra server):

cat /etc/hosts
cat /etc/resolv.conf
dig jsr-domain.nl mx
dig jsr-domain.nl any
host `hostname`  <-- use that exact command with backticks not single quotes

[jsr]

root@mail:/var/log# cat /etc/hosts
127.0.0.1 localhost.local localhost
192.168.178.106 mail.jsr-domain.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


root@mail:/var/log# cat /etc/resolv.conf
nameserver 192.168.178.106


root@mail:/var/log# dig jsr-domain.nl mx

; <<>> DiG 9.4.2-P2 <<>> jsr-domain.nl mx
;; global options: printcmd
;; connection timed out; no servers could be reached


root@mail:/var/log# dig jsr-domain.nl any

; <<>> DiG 9.4.2-P2 <<>> jsr-domain.nl any
;; global options: printcmd
;; connection timed out; no servers could be reached


root@mail:/var/log# host `hostname`
;; connection timed out; no servers could be reached

[phoenix]

That would indicate that your DNS server isn't running or you have a firewall and/or SElinux (AppArmor) problem. If you have SElinux or AppArmor and a firewall installed then disable them, start your DNS server and try the commands again.

[jsr]

there is no firewall running at this moment (even not yet installed)

Bind9 is not willing to restart / start

root@mail:/etc/bind# /etc/init.d/bind9 restart
* Stopping domain name service... bind rndc: connect failed: 127.0.0.1#953: connection refused
[fail]
* Starting domain name service... bind [fail]


im really a DNS newbe so this will be a problem for me to solve, i hope anyone can help me furher dispite of my silly questions

[phoenix]

You'll have to do some reading about DNS, which operating system is this and did you install bind or bind-chroot?

[jsr]

OS is Ubuntu 8.04 LTS Bind is the default bind9 (installed using aptitude)

[phoenix]

Try the following: Ubuntu 9.04 rndc Fix on Bind9 | BeginLinux if that doesn't work there's a 'how-to' for setting up BIND here: DNS server Setup using bind in Ubuntu|Ubuntu Geek

[jsr]

unfortunaly it did not do the trick for me.

thanks for the help.

it is a testing environment so i will just start over and first create a fully working DNS server and afterwards install zimbra on it.

[jdp459]

As I look at this reported issue, I wonder **why** Zimbra can't use normal host files like every other server out there?
We keep 2 hosts files around - 1 for installing and upgrading Zimbra and the other to allow the server to behave inside our network. Seems a trivial 1 line of perl to pull only the hostname.domainname.tld line from the file for whatever Zimbra really requires. Grabbing just the first 2 or 3 fields and ignoring the extras is trivial too.

BTW, we found that an internal DNS isn't required. In our experience, the calls for "split DNS" are not necessary to get Zimbra working in a small enterprise (single server, no proxy). You just need the internal servers to access the internal IP (via /etc/hosts), the external users/servers to use the public MX DNS record for access, and the appropriate ports forwarded from your firewall to the server. DNS is a big hassle if you don't need it for any other purpose than Zimbra and should be avoided, if at all possible.