Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-23-2007, 07:20 PM
Loyal Member
 
Posts: 96
Default Can't receive mail

I'm new to Zimbra and was attached to the quality of the product. I've been using Postfix in the past with Squirrelmail. I've installed the latest version of Zimbra and I have everything setup including the masquerading (@domain.com instead of @mail.domain.com) on sending but I can't seem to receive mail. If I send a test mail from yahoo to @mail.domain.com, no mail comes through but I don't get an error on the yahoo side for a failure. If I send to the masquerade address (@domain.com), I get a failure error on the on the yahoo side immediately. Either way, no mail is received on my server. I'm sure it's something very simple I'm missing.

Any help would be appreciate. Thanks in advance.
Reply With Quote
  #2 (permalink)  
Old 02-23-2007, 09:50 PM
Former Zimbran
 
Posts: 5,606
Default

Hello, and welcome to the forums!
Could you please post your postfix log located in /var/log/zimbra.log so that we can see what's going on?

Thanks
john
Reply With Quote
  #3 (permalink)  
Old 02-24-2007, 03:37 AM
Loyal Member
 
Posts: 96
Default

I already did a little troubleshooting and it looked like it was nothing showing me an answer there. I obviously edited this copy and paste not to reflect my true domain name.

Feb 24 06:32:01 mail CRON[6572]: (pam_unix) session opened for user zimbra by (uid=0)
Feb 24 06:32:04 mail zmtomcatmgr[6688]: status requested
Feb 24 06:32:04 mail zmtomcatmgr[6688]: status OK
Feb 24 06:32:04 mail zimbramon[6573]: 6573:info: 2007-02-24 06:32:02, STATUS: mail.DOMAIN.COM: antispam: Running
Feb 24 06:32:04 mail zimbramon[6573]: 6573:info: 2007-02-24 06:32:02, STATUS: mail.DOMAIN.COM: antivirus: Running
Feb 24 06:32:04 mail zimbramon[6573]: 6573:info: 2007-02-24 06:32:02, STATUS: mail.DOMAIN.COM: ldap: Running
Feb 24 06:32:04 mail zimbramon[6573]: 6573:info: 2007-02-24 06:32:02, STATUS: mail.DOMAIN.COM: logger: Running
Feb 24 06:32:04 mail zimbramon[6573]: 6573:info: 2007-02-24 06:32:02, STATUS: mail.DOMAIN.COM: mailbox: Running
Feb 24 06:32:04 mail zimbramon[6573]: 6573:info: 2007-02-24 06:32:02, STATUS: mail.DOMAIN.COM: mta: Running
Feb 24 06:32:04 mail zimbramon[6573]: 6573:info: 2007-02-24 06:32:02, STATUS: mail.DOMAIN.COM: snmp: Running
Feb 24 06:32:04 mail zimbramon[6573]: 6573:info: 2007-02-24 06:32:02, STATUS: mail.DOMAIN.COM: spell: Running
Feb 24 06:32:04 mail CRON[6572]: (pam_unix) session closed for user zimbra

When I use mxtoolbox.com to check to see what's going on, I get a reverse DNS lookup failure. I followed the instructions per

I got Ubuntu and Zimbra working

But I have a feeling that I didn't do something right in BIND that's causing this issue.
Reply With Quote
  #4 (permalink)  
Old 02-24-2007, 08:27 AM
Loyal Member
 
Posts: 96
Default

I'm getting reverse DNS lookup failures when I test using mxtoolbox.com. I used the setup from the Ubuntu post and I think I messed up BIND somehow. When I run the log file you suggested, I get no errors and everything seems to running as normal.
Reply With Quote
  #5 (permalink)  
Old 02-24-2007, 08:58 AM
Former Zimbran
 
Posts: 5,606
Default

Hi Reckless,
Thanks for letting me know. We have a new spam moderation system, and sometimes, newer users posts' get moderated. Sorry bout that, but thanks for letting me know

Let's try
dig mx mail.DOMAIN.com

and see what output you get.

-john
Reply With Quote
  #6 (permalink)  
Old 02-24-2007, 10:00 AM
Loyal Member
 
Posts: 96
Default

dig mx mail.MYDOMAIN.COM

; <<>> DiG 9.3.2 <<>> mx mail.MYDOMAIN.COM
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49276
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;mail.MYDOMAIN.COM IN MX

;; ANSWER SECTION:
mail.MYDOMAIN.COM 60 IN MX 10 MYDOMAIN.COM
mail.MYDOMAIN.COM 60 IN MX 5 mail.MYDOMAIN.COM

;; ADDITIONAL SECTION:
mail.MYDOMAIN.COM 60 IN A 68.XX.XX.XX < these 2 addresses matched
MYDOMAIN.COM 60 IN A 68.XX.XX.XX

;; Query time: 60 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sat Feb 24 12:46:47 2007
;; MSG SIZE rcvd: 99

When I test on mxtoolbox.com site I get this error:

HELO mxtoolbox.com - DIAGNOSTIC TEST - See http://www.mxtoolbox.com/Policy.aspx
250 mail.MYDOMAIN.COM [62 ms]
HELO mxtoolbox.com
250 mail.MYDOMAIN.COM [47 ms]
MAIL FROM:
250 Ok [62 ms]
RCPT TO:
554 : Relay access denied [62 ms]
QUIT
221 Bye [47 ms]

I'm sure it has something to do with the BIND setup unless port 25 issue.
Reply With Quote
  #7 (permalink)  
Old 02-24-2007, 10:02 AM
Loyal Member
 
Posts: 96
Default

netstat -ant

tcp 0 0 127.0.0.1:2208 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.100:389 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10024 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:7306 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:7307 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3310 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:50423 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.100:42109 192.168.0.100:389 ESTABLISHED
tcp 0 0 192.168.0.100:389 192.168.0.100:42109 ESTABLISHED
tcp 0 0 127.0.0.1:7306 127.0.0.1:42185 ESTABLISHED
tcp 0 0 127.0.0.1:7306 127.0.0.1:36331 ESTABLISHED
tcp 0 0 192.168.0.100:40583 66.102.1.104:80 TIME_WAIT
tcp6 0 0 :::993 :::* LISTEN
tcp6 0 0 :::995 :::* LISTEN
tcp6 0 0 :::7780 :::* LISTEN
tcp6 0 0 :::110 :::* LISTEN
tcp6 0 0 :::143 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 :::7025 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::7035 :::* LISTEN
tcp6 0 0 :::7071 :::* LISTEN
tcp6 0 0 ::ffff:127.0.0.1:36331 ::ffff:127.0.0.1:7306 ESTABLISHED
tcp6 0 0 ::ffff:127.0.0.1:42185 ::ffff:127.0.0.1:7306 ESTABLISHED
tcp6 0 0 ::ffff:192.168.0.:50754 ::ffff:192.168.0.10:389 TIME_WAIT
tcp6 0 0 ::ffff:192.168.0.:50755 ::ffff:192.168.0.10:389 TIME_WAIT
tcp6 0 0 ::ffff:192.168.0.:50752 ::ffff:192.168.0.10:389 TIME_WAIT
tcp6 0 0 ::ffff:192.168.0.:50753 ::ffff:192.168.0.10:389 TIME_WAIT
tcp6 0 0 ::1:42139 ::1:46329 TIME_WAIT
tcp6 0 0 ::1:36240 ::1:57863 TIME_WAIT
tcp6 0 0 ::1:51412 ::1:34409 TIME_WAIT
Reply With Quote
  #8 (permalink)  
Old 02-24-2007, 10:50 AM
Loyal Member
 
Posts: 96
Default

I remove bind9 from my box and reinstalled Zimbra. I ignored the hostname error on setup and now I can send and receive without an issue using @mail.MYDOMAIN.com.

I setup masquerading per

http://wiki.zimbra.com/index.php?tit...n_Masquerading

so now my sent mail is received as @MYDOMAIN.COM but I can only reply to @mail.MYDOMAIN.COM. If I try to reply to @MYDOMAIN.COM I get an immediate error. Should I be setting up RELAYING/DOMAIN FORWARDING per that page as well for @MYDOMAIN to find it's way to @mail.MYDOMAIN.COM?

My MX records point all back to me.
Reply With Quote
  #9 (permalink)  
Old 02-24-2007, 11:02 AM
Former Zimbran
 
Posts: 5,606
Default

Do you have the appropriate domains set up in your adminui?
Reply With Quote
  #10 (permalink)  
Old 02-24-2007, 11:22 AM
Loyal Member
 
Posts: 96
Default

I was one step ahead. I created a domain alias per that wiki and now everything is fine. This is a fantastic product. I was using postfix with Squirrelmail before but Zimbra is amazing.

Thanks for all the help. I'm sure I will be back on here asking about calendar and contact sharing.

Thanks.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.