[SOLVED] Incoming msgs not being delivered

Hi.
Running FC5, 4.5.6_GA_1044.FC5_20070706162711 FC5 FOSS edition
and finding a problem I can't run down by searching here.
I can mail out as a user fine, and remote recipient gets message.
But sending IN a new message, or replying to Zimbra user results in msgs being put in deferred queue.
I have turned off AV/AS server, and done severa; zmcontrol stop/starts...
No other service answering when i turn off Zimbra, and telnet 25...nothing answers.

Any help, or point me to appropriate thread?
Thanks very much,
rick
[Follow up]
entry in log:
Sep 2 11:36:59 smtp postfix/lmtp[12634]: 69AF1C10776: to=<"user"@creativexxxname.com>, relay=none, delay=3579, status=deferred (connect to smtp.creativexxxxname.com[69.2.241.230]: Connection timed out)

What does the following show (run on your server):

Code:

---

host `hostname`  <-- backticks not single quotes
dig yourdomain.com MX
dig yourdomain.com any

---

I'm leaning toward DNS issue, too, but not sure how to fix it.
(inside IP address is 10.0.0.1)
(thanks)

[root@smtp tuser]# host `hostname`
smtp.creativelights.com has address 69.2.241.230
-------------------------------------------------
dig `creativelights.com` MX

; <<>> DiG 9.3.2 <<>> MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35814
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13

;; QUESTION SECTION:
;. IN NS

;; ANSWER SECTION:
. 15540 IN NS j.root-servers.net.
. 15540 IN NS k.root-servers.net.
. 15540 IN NS l.root-servers.net.
. 15540 IN NS m.root-servers.net.
. 15540 IN NS a.root-servers.net.
. 15540 IN NS b.root-servers.net.
. 15540 IN NS c.root-servers.net.
. 15540 IN NS d.root-servers.net.
. 15540 IN NS e.root-servers.net.
. 15540 IN NS f.root-servers.net.
. 15540 IN NS g.root-servers.net.
. 15540 IN NS h.root-servers.net.
. 15540 IN NS i.root-servers.net.

;; ADDITIONAL SECTION:
j.root-servers.net. 15540 IN A 192.58.128.30
k.root-servers.net. 15540 IN A 193.0.14.129
l.root-servers.net. 15540 IN A 198.32.64.12
m.root-servers.net. 15540 IN A 202.12.27.33
a.root-servers.net. 15540 IN A 198.41.0.4
b.root-servers.net. 15540 IN A 192.228.79.201
c.root-servers.net. 15540 IN A 192.33.4.12
d.root-servers.net. 15540 IN A 128.8.10.90
e.root-servers.net. 15540 IN A 192.203.230.10
f.root-servers.net. 15540 IN A 192.5.5.241
g.root-servers.net. 15540 IN A 192.112.36.4
h.root-servers.net. 15540 IN A 128.63.2.53
i.root-servers.net. 15540 IN A 192.36.148.17

;; Query time: 6 msec
;; SERVER: 192.168.150.11#53(192.168.150.11)
;; WHEN: Sun Sep 2 12:06:18 2007
;; MSG SIZE rcvd: 449
-------------------------------------------

[root@smtp tuser]# dig `creativelights.com` any
bash: creativelights.com: command not found

; <<>> DiG 9.3.2 <<>> any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43068
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13

;; QUESTION SECTION:
;. IN NS

;; ANSWER SECTION:
. 86210 IN NS l.root-servers.net.
. 86210 IN NS j.root-servers.net.
. 86210 IN NS i.root-servers.net.
. 86210 IN NS f.root-servers.net.
. 86210 IN NS m.root-servers.net.
. 86210 IN NS k.root-servers.net.
. 86210 IN NS g.root-servers.net.
. 86210 IN NS c.root-servers.net.
. 86210 IN NS d.root-servers.net.
. 86210 IN NS e.root-servers.net.
. 86210 IN NS b.root-servers.net.
. 86210 IN NS a.root-servers.net.
. 86210 IN NS h.root-servers.net.

;; ADDITIONAL SECTION:
l.root-servers.net. 12658 IN A 198.32.64.12
j.root-servers.net. 12658 IN A 192.58.128.30
i.root-servers.net. 86210 IN A 192.36.148.17
f.root-servers.net. 86210 IN A 192.5.5.241
m.root-servers.net. 86210 IN A 202.12.27.33
k.root-servers.net. 86210 IN A 193.0.14.129
g.root-servers.net. 86210 IN A 192.112.36.4
c.root-servers.net. 86210 IN A 192.33.4.12
d.root-servers.net. 86210 IN A 128.8.10.90
e.root-servers.net. 86210 IN A 192.203.230.10
b.root-servers.net. 86210 IN A 192.228.79.201
a.root-servers.net. 86210 IN A 198.41.0.4
h.root-servers.net. 86210 IN A 128.63.2.53

;; Query time: 2 msec
;; SERVER: 192.168.150.12#53(192.168.150.12)
;; WHEN: Sun Sep 2 12:09:27 2007
;; MSG SIZE rcvd: 449

Yes, it's a DNS problem. I guess this is a new install? As you're behind a NAT device (or firewall) you will need to install a local DNS server so that Zimbra (postfix) can resolve the local IP address of your server. Check the Split DNS setup in the wiki (or search the forums for 'DNS in a Nutshell'), it's fairly straightforward and you should be up and running in no time.

Thanks...yes, new install. Plus external DNS just got resolved this morning.
Yecch. this one is messy.
I've got a WinServer doing DNS over on that 192.168.150.xx address, so I'll look at setting that up properly.
(My Windows admin is out of town, so this might be Tuesday, now.)

Thanks Bill -
have a good week,
rick
PS. I looked at that splitDNS a week ago, and was hoping that I wouldn't have to do it. ;)

Yup, you definitely want to use split dns

The only other way would be to uncheck enable DNS lookups-but then you need to have a 'relay for external delivery'.
Or the uglier messing with zimbraMailTransport...
-but you have a DNS box internally so just don't.

Thanks, gents.
the nutshell article wasn't quite as useful as the wiki entry.
But I followed the directions, and after restarting named and bind, my deferred msgs all flowed. Perfect.

Demonstration for the customer begins Tuesday. wish us luck.
rick

Ah, I take it you decided to forgo waiting for your dns admin to come back.
Even though you've already done it-there's also this: /blog/archives/2007/06/making_zimbra_bind_work_together_1.html

Thanks mmorse - I did figure that I could just get the linux box to take care of itself. And it worked out fine. I have a second/virtual domain to add when we go live.
I should be able to add another zone like this, for the second domain, right?

Nutshell article had few typos, and the wiki article just seemed more streamlined.
thanks,
rick

(now I need to find an answer on the clamav component being weird).

Quote:

---

Originally Posted by rickvv

(now I need to find an answer on the clamav component being weird).

---

The release of ClamAV in 4.5.6 is just plan bad. We're going to update it in 4.5.7 which is expected soon.