Getting mail from another account

[dhull]

I tried to get mail from another IMAP account. Partway through the process I got the following error message.

A network service error has occurred. msg: system failure: Unable to store IMAP message data
code: service.FAILURE
method: ZmCsfeCommand.prototype.invoke
detail: soap:Receiver

What's going on here?

[jholder]

Can you take a look at the full stack trace in /opt/zimbra/log/zmmailboxd.out

[JpMaxMan]

Originally Posted by dhull

I tried to get mail from another IMAP account. Partway through the process I got the following error message.

A network service error has occurred. msg: system failure: Unable to store IMAP message data
code: service.FAILURE
method: ZmCsfeCommand.prototype.invoke
detail: soap:Receiver

What's going on here?

I am getting this same problem - is there any info on a solution?

[phoenix]

Originally Posted by JpMaxMan

I am getting this same problem - is there any info on a solution?

How about answering the question that was asked by jholder in the post above yours?

[JpMaxMan]

Ok, I didn't see anything in there.. this is from the "view details" pop-up:

A network service error has occurred. msg: system failure: Unable to store IMAP message data
code: service.FAILURE
method: ImportDataRequest
detail: soap:Receiver
trace: com.zimbra.common.service.ServiceException: system failure: Unable to store IMAP message data Code:service.FAILURE at com.zimbra.common.service.Ser...

Doing a tail on the zmmailboxd.out while I did a check mail did not show any activity. Looking in that file, there are the last two exceptions listed:

Caused by: javax.naming.CommunicationException: zimbra.tipit.net:389 [Root exception is java.net.ConnectException: Connection refused]
at com.sun.jndi.ldap.Connection.(Connection.java:197)
at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)
at com.sun.jndi.ldap.LdapClientFactory.createPooledCo nnection(LdapClientFactory.java:46)
at com.sun.jndi.ldap.pool.Connections.(Connections.java:97)
at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Po ol.java:114)
at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(Ld apPoolManager.java:310)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1572)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:261 6)
at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:287)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapC txFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(Ldap CtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstanc e(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext (LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(N amingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(Init ialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.ja va:223)
at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134)
at com.zimbra.cs.account.ldap.LdapUtil.getDirContext( LdapUtil.java:214)
... 32 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(PlainSoc ketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
at java.net.Socket.connect(Socket.java:519)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:336)
at com.sun.jndi.ldap.Connection.(Connection.java:184)
... 49 more

But, I don' think this has anything to do with it?

I'm happy to post any further info, please let me know what would be helpful.

[phoenix]

Originally Posted by JpMaxMan

Caused by: javax.naming.CommunicationException: zimbra.tipit.net:389 [Root exception is java.net.ConnectException: Connection refused]

The problem would appear to be your inability to contact LDAP, is it running?

[JpMaxMan]

Originally Posted by phoenix

The problem would appear to be your inability to contact LDAP, is it running?

According to zmcontrol status, yes:

ldap Running

That's what I was saying, I think that error is not related. Maybe I'm wrong. But, I think it was already there. Doing a:

tail -f zmmailboxd.out

while I create the IMAP account and then have it check external mail does not generate any logging activity in this file.

[bjagg]

Try tailing /opt/zimbra/log/mailbox.log for the stack traces.

I had a similar problem with one account. The account had a 'spam' and a 'SPAM' folder. The mail server had no problems with the two since they are difference case. Zimbra did. Once I merged the folders to one, it sync'd just fine!!

[dwmtractor]

I have seen a similar error when your system tries to download a message that exceeds either the maximum message size, or would put your mailbox over its quota. You might have a look-see at those two things and make sure they aren't slapping you down. . .the error messages aren't too instructive at that point.