Zimbra Send OR recieve, not both

[japerry]

Hello, I've been looking through these forums, along with google trying to find answers to the problems I've been having with getting zimbra to work. Basically these are my problems:

Enable DNS lookups--SMTP works fine, mail is sent. Great. However, when looking at the logs, I see Oct 16 02:10:34 atcdirect postfix/smtp[1499]: 24EAD2D1900: to=<username@www.atcdirect.com>, relay=none, delay=30, status=deferred (connect to www.atcdirect.com[66.15.163.221]: Connection timed out)
*note, this was just atcdirect.com, but I added a hostname www to the front. shouldn't change anything.

When I remove DNS lookups, mail gets recieved just fine, but nothing will send. Either pingouts (to gmail.com because it doesn't resolve to google servers) or a 553 'this host is not allowed' error.

The last thing that doesn't seem to work is remote STMP authentication. It keeps prompting for a password in thunderbird and the logs return:
warning: SASL authentication failure: Password verification failed
Oct 16 02:09:10 atcdirect postfix/smtpd[30256]: warning: c-24-18-79-68.hsd1.wa.comcast.net[24.18.79.68]: SASL PLAIN authentication failed
Oct 16 02:09:10 atcdirect postfix/smtpd[30256]: warning: c-24-18-79-68.hsd1.wa.comcast.net[24.18.79.68]: SASL LOGIN authentication failed

In webmail, it seems like sending/recieving works just fine. Recieving mail in thunderbird works fine now that I've forwarded port 110 to 995 (the firewall on this network is really limiting towards ports.)

Hopefully someone can help. The 'disable_dns' page was helpful at first when I noticed I could recieve mail. but now that I can't send it, it hasn't really helped much.

Thank you!
Jakob

[KevinH]

Try this thread to fix your sasl issues:

SMTP SASL authentication failure

This may also fix your sending problems since postfix by default requires smtp auth to send from a remote network.

[japerry]

FIXED the SASL authd issue, I should have made it a little more clear what I've been doing.. I moved tomcat to :7070 (removed port 80 redirection).. I went in and edited ~/cyrus-sasl/etc/saslauthd.conf to say
http://hostname/service/soap -> http://hostname:7070/service/soap

But, I'm still having mucho problems Sending or recieving. This is the MAJOR problem I seek an answer for. Currently DNS lookups is OFF, which allows me to recieve all mail, but I cannot send any mail out. Its probably a simple fix, I just can't find it.

Thanks!... btw do you guys sit on IRC anywhere?

[KevinH]

Originally Posted by japerry

But, I'm still having mucho problems Sending or recieving. This is the MAJOR problem I seek an answer for. Currently DNS lookups is OFF, which allows me to recieve all mail, but I cannot send any mail out. Its probably a simple fix, I just can't find it.

We don't sit on IRC.

Are the logs still reporting errors like your first post? Do you have a valid DNS setup on your host?

What does "nslookup `hostname`" return?

[japerry]

There is no DNS setup currently on this host, the /etc/hostfile is showing:

127.0.0.1 localhost.localdomain localhost
192.168.111.2 atcdirect.com mail mail.atcdirect.com

nslookup atcdirect.com prints out
66.15.163.221

The mail server is located behind a firewall, but ports 25,143,110,80,7070,7071,22 are all open and being redirected to this machine. For SSL pop, 110 is redirected to 995 internally.

Do you think we need a DNS server on this system to get it to operate correctly? Do you think the local ip is causing an issue with resolving atcdirect.com at 66.15.163.221??

Thanks
~Jakob

[KevinH]

Originally Posted by japerry

There is no DNS setup currently on this host, the /etc/hostfile is showing:

127.0.0.1 localhost.localdomain localhost
192.168.111.2 atcdirect.com mail mail.atcdirect.com

This line:

192.168.111.2 atcdirect.com mail mail.atcdirect.com

Seems a little non-standard and I wonder if that tripped up the installer.

192.168.111.2 mail.atcdirect.com mail

Is what I'd expect and then `hostname` should return mail.atcdirect.com

What does hostname return now?

[Ed Wagner]

I've had a similar problem receiving email when DNS is enabled in the MTA settings. My Zimbra server is behind a firewall and I'm only forwarding a couple of ports through. Since the timeout was occurring when trying to connect to the external IP, it seemed like I might not be forwarding all of the correct ports. After some trial and error, it seems that opening up port 7025 (not port 7075 as you might expect from reading other posts and the bin/zmiptables mapping) in addition to port 25 solved the problem.