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-02-2008, 04:17 AM
Senior Member
 
Posts: 59
Default Mail not getting to the mailboxes

After installing Zimbra on Debian 4 I log on to the admin console and creating a couple of accounts. Checking that all services are running (monitoring -> serverstatus). Only thing installer complained about was the fact that none of the MX records pointed to the servers IP (due to the fact that I havent changed the DNS yet..). Now, since all services are running and I can successfully log on to webmail I now change the dns settings for my domain so that mail.mydomain.com points to my IP.. I can see via Tools -> mail queue that mails are ticking in, but ending up in the "deferred" tab and none of em ends up in my mailbox. Any pointers to what I can have done wrong?
Reply With Quote
  #2 (permalink)  
Old 02-02-2008, 05:06 AM
Zimbra Consultant & Moderator
 
Posts: 20,316
Default

Quote:
Originally Posted by osiris View Post
Any pointers to what I can have done wrong?
You've already answered your own question, it's the fact you have no DNS A or MX records pointing to your server. If you are behind a NAT router then you'll need a Split DNS set-up.
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 02-02-2008, 05:27 AM
Senior Member
 
Posts: 59
Default

"Now, since all services are running and I can successfully log on to webmail I now change the dns settings for my domain so that mail.mydomain.com points to my IP". And mails are ticking so obviously the MX record where set, but figured out the error, yes I am behind NAT so I had to open up port 7075 I think it was, then everything worked fine, saw from logs lots of connection refused for that port..

Anyhow, things works but no stats shows up in stats monitor, and doesnt seem like the antispam works either as mails where I repeatly mention "******" etc goes straight trough, any way to really test each functionality of the server? Specifically antivirus and antispam solution, just to make 100% sure its running ok and all is good..

Feb 2 14:14:18 mail amavis[6714]: No $dspam, not using it
Feb 2 14:16:03 mail zimbramon[7501]: 7501:info: 2008-02-02 14:16:01, STATUS: mail.itechies.info: antispam: Running

Things like that makes me worried
Reply With Quote
  #4 (permalink)  
Old 02-02-2008, 05:33 AM
Zimbra Consultant & Moderator
 
Posts: 20,316
Default

It will take about 24hrs for the statistics to populate. DSPAM isn't enabled in current versions of Zimbra but Spamassassin etc. is and that's what does the anti-spam filtering.
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 02-02-2008, 05:52 AM
Senior Member
 
Posts: 59
Default Just to ignore?

Says in the end its done, but I guess the mailbox for spam user was supposed to grow with the added e-mails? or are they learned and then directly deleted?

zimbra@mail:~$ zmtrainsa
20080202144939 Starting spam/ham extraction from system accounts.
[] ERROR: java.security.cert.CertificateNotYetValidException : NotBefore: Sun Feb 03 01:02:53 CET 2008
Exception in thread "main" com.zimbra.common.service.ServiceException: system failure: admin auth failed url=https://mail.itechies.info:7071/service/admin/soap/
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:183)
at com.zimbra.cs.util.SpamExtract.getAdminAuthToken(S pamExtract.java:434)
at com.zimbra.cs.util.SpamExtract.main(SpamExtract.ja va:187)
Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Untrusted Server Certificate Chain
at com.sun.net.ssl.internal.ssl.Alerts.getSSLExceptio n(Alerts.java:174)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(S SLSocketImpl.java:1591)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Ha ndshaker.java:187)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Ha ndshaker.java:181)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serv erCertificate(ClientHandshaker.java:975)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.proc essMessage(ClientHandshaker.java:123)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoo p(Handshaker.java:516)
at com.sun.net.ssl.internal.ssl.Handshaker.process_re cord(Handshaker.java:454)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:884)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1096)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRe cord(SSLSocketImpl.java:623)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write (AppOutputStream.java:59)
at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
at org.apache.commons.httpclient.methods.StringReques tEntity.writeRequest(StringRequestEntity.java:150)
at org.apache.commons.httpclient.methods.EntityEnclos ingMethod.writeRequestBody(EntityEnclosingMethod.j ava:495)
at org.apache.commons.httpclient.HttpMethodBase.write Request(HttpMethodBase.java:1973)
at org.apache.commons.httpclient.HttpMethodBase.execu te(HttpMethodBase.java:993)
at org.apache.commons.httpclient.HttpMethodDirector.e xecuteWithRetry(HttpMethodDirector.java:397)
at org.apache.commons.httpclient.HttpMethodDirector.e xecuteMethod(HttpMethodDirector.java:170)
at org.apache.commons.httpclient.HttpClient.executeMe thod(HttpClient.java:396)
at org.apache.commons.httpclient.HttpClient.executeMe thod(HttpClient.java:324)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:234)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:295)
at com.zimbra.common.soap.SoapTransport.invokeWithout Session(SoapTransport.java:282)
at com.zimbra.cs.util.SpamExtract.getAdminAuthToken(S pamExtract.java:429)
... 1 more
Caused by: java.security.cert.CertificateException: Untrusted Server Certificate Chain
at com.sun.net.ssl.X509TrustManagerJavaxWrapper.check ServerTrusted(SSLSecurity.java:600)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serv erCertificate(ClientHandshaker.java:967)
... 22 more

-----

20080202144942 Finished extracting spam/ham from system accounts.
20080202144942 Starting spamassassin training.
netset: cannot include 127.0.0.0/8 as it has already been included
Learned tokens from 0 message(s) (0 message(s) examined)
netset: cannot include 127.0.0.0/8 as it has already been included
Learned tokens from 0 message(s) (0 message(s) examined)
netset: cannot include 127.0.0.0/8 as it has already been included
20080202144945 Finished spamassassin training.

Last edited by osiris; 02-02-2008 at 06:04 AM..
Reply With Quote
  #6 (permalink)  
Old 02-02-2008, 06:36 AM
Moderator
 
Posts: 6,237
Default

The error pretty much says that you should check your certificates...
Is this a commercial cert? "CertificateNotYetValidException : NotBefore: Sun Feb 03 01:02:53 CET 2008"
Reply With Quote
  #7 (permalink)  
Old 02-02-2008, 08:29 AM
Senior Member
 
Posts: 59
Default

Its the ones generated by the installer
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.