[SOLVED] Mail Transport Unavailable - Ubuntu 8.04

[Mccreations]

Hey,

Thanks for reading this, I need a little help.

I have one main server and a firewall/modem. My firewall has always been setup to assign the server the public IP address and redirect all traffic to the server. For security reasons I wanted to change that, so I re-configured my firewall to assign the server a private IP address and block all traffic. I then created a rule for all zimbra ports, so all of the mail ports are open.

But after the change to a private IP address I can no longer receive any mail. It all appears in the mail queue under deferred. The error is "mail transport unavailable"

I can send mail no problem but cannot receive mail.
Any help would be greatly appreciated!!

My server is the latest zimbra open source on Ubuntu server 8.04.

[iway]

Have you set the corresponding IP entry in the admin console?

[Mccreations]

Originally Posted by interways

Have you set the corresponding IP entry in the admin console?

Are you talking about the "MTA Trusted Networks"?

I believe I have this setup correctly, here's what I have now:
127.0.0.0/8 192.168.1.14/32

192.168.1.14 is my server's private IP address.

[santini]

I think I'm getting the same error on a similar setup. Smoothwall firewall, with port forwarding setup, to a zimbra server running on ubuntu 8.04.

I don't know much about how Zimbra/mail works. What it looks like is happening is mail comes into the MTA, and then the local delivery agent is trying to deliver the mail to the local users mail queue/account via the global IP address.

whatever ports that happens on are most likely blocked and causing the error/non-delivery.

[santini]

not sure what the negative side effects of this will be, but I got it working.

Servers > MTA
- uncheck 'enable DNS lookup'

then reboot.

[Mccreations]

Originally Posted by santini

not sure what the negative side effects of this will be, but I got it working.

Servers > MTA
- uncheck 'enable DNS lookup'

then reboot.

Thanks! That worked, and now I'm receiving mail again.

I wonder too about negative side effects. If someone could fill us in please...

[phoenix]

The answer for both of you would be a Split DNS set-up.

[Mccreations]

Originally Posted by phoenix

The answer for both of you would be a Split DNS set-up.

Thanks for responding!
Would you recommend setting up a Split DNS, or should I just leave DNS checks off?
And one more thing, if I also have a webserver on the same server would a Split DNS cause any troubles with it? Since they're both on the same machine there's no subdomain like mail.mydomain.tld just mydomain.tld, and since the A records are also changed to local IPs in the split DNS would that cause problems with the web server?

Sorry for the trouble.

[phoenix]

It shouldn't cause you any problems and mail.mydomain.tld isn't a subdomain it would be the FQDN of your mailserver and only show in the A and MX records. As far as the web server is concerned (if you have local DNS records) the a cname record pointing to the server should suffice.

[Mccreations]

Originally Posted by phoenix

It shouldn't cause you any problems and mail.mydomain.tld isn't a subdomain it would be the FQDN of your mailserver and only show in the A and MX records. As far as the web server is concerned (if you have local DNS records) the a cname record pointing to the server should suffice.

Alright, thanks for all the help!

You guys are the best!