I found this messages when have the mistake. All services are running but i see that in /var/log/messages
Code:
Oct 30 09:00:57 mail saslauthd[28351]: zmauth: authenticating against elected url 'https://mail.mydomain.com:7071/service/admin/soap/' ...
Oct 30 09:00:57 mail saslauthd[28351]: zmpost: url='https://mail.mydomain.com:7071/service/admin/soap/' returned buffer->data='<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"/></soap:Header><soap:Body><soap:Fault><soap:Code><soap:Value>soap:Receiver</soap:Value></soap:Code><soap:Reason><soap:Text>system failure: getDirectContext</soap:Text></soap:Reason><soap:Detail><Error xmlns="urn:zimbra"><Code>service.FAILURE</Code><Trace>btpool0-51:1256889657720:2fa0d5deaf1cbbdf</Trace></Error></soap:Detail></soap:Fault></soap:Body></soap:Envelope>', hti->error=''
Oct 30 09:00:57 mail saslauthd[28351]: auth_zimbra: user auth failed: system failure: getDirectContext
When this was hapenning can't login on Zimbra's server. Our clients insert the correct username and password and Zimbra ask this fields again. We can't send mails.
I have the same warn on /opt/zimbra/log/mailbox.log
Code:
2009-10-30 08:54:24,612 INFO [MailboxPurge] [name=user@mydomain.com;mid=126;] purge - Purging messages.
2009-10-30 08:54:25,152 WARN [MailboxPurge] [name=user@mydomain.com;mid=126;] purge - Unable to purge mailbox 126
com.zimbra.common.service.ServiceException: system failure: getDirectContext
ExceptionId:MailboxPurge:1256889265141:2fa0d5deaf1cbbdf
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:253)
at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:238)
at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrsInternal(LdapProvisioning.java:279)
at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:263)
at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:244)
at com.zimbra.cs.account.Provisioning.modifyAttrs(Provisioning.java:1543)
at com.zimbra.cs.mailbox.PurgeThread.saveLastPurgedId(PurgeThread.java:204)
at com.zimbra.cs.mailbox.PurgeThread.run(PurgeThread.java:135)
Caused by: javax.naming.CommunicationException: mail.mydomain.com:389 [Root exception is java.net.ConnectException: Connection refused]
at com.sun.jndi.ldap.Connection.<init>(Connection.java:197)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2616)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:246)
... 7 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jndi.ldap.Connection.createSocket(Connection.java:336)
at com.sun.jndi.ldap.Connection.<init>(Connection.java:184)
... 20 more Can be a bug??
SMTP authentication failed