[SOLVED] Issues w/ relaying for one domain

[pompeiisneaks]

I'm having issues relaying for only one domain, that happens to be local to the network the zimbra server is on, Sadly the postfix logs are completely useless as to why, the massive time I've spent googling only tell me it "could" be a dns lookup error, but all lookups succeed just fine. But, for completeness, here are my logs.

Feb 16 15:33:45 gamma postfix/smtpd[18833]: 297B345DBA: client=localhost[127.0.0.1]
Feb 16 15:33:45 gamma postfix/cleanup[18826]: 297B345DBA: message-id=<763308428.51.1266359620242.JavaMail.root@gamma .removed.tld>
Feb 16 15:33:45 gamma postfix/qmgr[6008]: 297B345DBA: from=<removed@removed>, size=1168, nrcpt=1 (queue active)
Feb 16 15:33:45 gamma postfix/error[18834]: 297B345DBA: to=<lookhere@somethingwronghere.bad>, relay=none, delay=0.19, delays=0.17/0.01/0/0.01, dsn=5.0.0, status=bounced (somethingwronghere.bad)
Feb 16 15:33:45 gamma postfix/bounce[18835]: 297B345DBA: sender non-delivery notification: 576CF45DBC
Feb 16 15:33:45 gamma postfix/qmgr[6008]: 297B345DBA: removed

I've obfuscated real server names, and made the domain taht is failing become:

somethingwronghere.bad

So what does this error mean? nothing to me. I've been a sendmail admin for a while, and do email support for a living. I can't for the life of me figure out why a

dig mx

and a

dig A

and dig NS PTR CNAME etc for that domain all work perfectly on the command line even as user zimbra or postfix, but the same error comes up every single time...

Ideas?

Why does it route to outside domains like say, hotmail, gmail, etc just fine, but this one a no go?

~Phil

[phoenix]

Let's start with the obvious questions, 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` <- use that exact command with backticks not single quotes

[pompeiisneaks]

Replacing all instances of my domain and my "other" domain w/ mydomain in fqdn's to hide the real domains but otherwise exact output from files:

cat /etc/hosts

[root@gamma ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
22.33.44.55 gamma.mydomain.com gamma www MyDomain | Domain Names, Web Hosting, and Free Domain Services

domain mydomain.com
search otherdomain.org
nameserver 192.168.13.1
nameserver 192.168.13.3

(those are my dns servers and work fine to resolve all hosts, as you'll see below:

[root@gamma ~]# dig mx otherdomain.org +short
10 kappa.otherdomain.org.
20 sigma.otherdomain.org.
30 kappa2.otherdomain.org.

[root@gamma ~]# dig mx mydomain.com +short
20 sigma.otherdomain.org.
30 kappa2.otherdomain.org.
40 gamma.mydomain.com.
10 kappa.otherdomain.org.

[root@gamma ~]# dig any otherdomain.org +short
"v=spf1 a mx ~all"
22.22.22.22 (faked IP)
alpha.otherdomain.org. hostmaster.otherdomain.org. 2009120201 10800 3600 1209600 43200
beta.otherdomain.org.
alpha.otherdomain.org.
sigma.otherdomain.org.
30 kappa2.otherdomain.org.
10 kappa.otherdomain.org.
20 sigma.otherdomain.org.

[root@gamma ~]# dig any mydomain.com +short
"v=spf1 a mx -all"
22.22.22.22 (faked IP again)
alpha.mydomain.com. hostmaster.mydomain.com. 2010010801 10800 3600 1209600 43200
alpha.mydomain.org.
delta.mydomain.org.
beta.mydomain.org.
10 kappa.otherdomain.org.
20 sigma.otherdomain.org.
30 kappa2.otherdomain.org.
40 gamma.mydomain.com.

[root@gamma ~]# host `gamma.mydomain.com`
-bash: gamma.mydomain.com: command not found

I was a bit confused by this last request as the backtick in bash is reserved as "run command in backticks and sent output here" like

for i in `cat /etc/hosts`; do echo $i; done

in a simple shell script...
but if I do a single tick:

[root@gamma ~]# host 'gamma.mydomain.com'
gamma.mydomain.com has address 22.33.44.55 (right address in lookup, but this isn't the host domain I can't find... the mx records for all mxes for that domain dig just fine. again, as I stated, this all works perfectly, I've been maintaining my own dns on Bind 9 for a long time now. I've done all the above tests and they all succeed just fine. The only other option I can think of that could be failing is that postfix may run in a chroot jail and the jail doesn't have something it needs... I just don't know if zimbra does that or not, and I really love the massively useless vague error that postfix throws. The email error I get as the sender is even more cryptic:

Here it is in its entirety:

This is the mail system at host gamma.mydomain.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<pdavis@otherdomain.org>: otherdomain.org


?????

~Phil

[pompeiisneaks]

WOW,

I'm silly, I just realized why, I was debating moving to the zimbra server for my otherdomain and had "set it up" in zimbra but put in no accounts. It wasn't trying to route to external servers, it was trying to deliver locally to a non existent account... Now I removed the domain in zimbra and it correctly uses the MX and routes the mail.

Thanks

~Phil

[phoenix]

Originally Posted by pompeiisneaks

WOW,

I'm silly, I just realized why, I was debating moving to the zimbra server for my otherdomain and had "set it up" in zimbra but put in no accounts. It wasn't trying to route to external servers, it was trying to deliver locally to a non existent account... Now I removed the domain in zimbra and it correctly uses the MX and routes the mail.

Glad you've resolved the problem.

Originally Posted by pompeiisneaks

[root@gamma ~]# host `gamma.mydomain.com`
-bash: gamma.mydomain.com: command not found

Ah, but you didn't run the command I asked.

Originally Posted by pompeiisneaks

I was a bit confused by this last request as the backtick in bash is reserved as "run command in backticks and sent output here"

You're quite right in that statement and that's why I asked you to run this command:

host `hostname`

Exactly that command without any changes and as you see it.

[pompeiisneaks]

Yeah thanks for that, sorry I didn't think before doing it. I'm used to expecting people to follow my directions and get annoyed when they don't and then I don't follow a simple one... anyway, sometimes when I get working on an issue like that I don't see the forest from the trees. The dns checks had already all been done and as you can see it was something non dns related. Cheers!