User unable to send email using Zimbra Connector for Outlook
User unable to send email using Zimbra Connector for Outlook
- This article is a Work in Progress, and may be unfinished or missing sections.
Purpose
Resolve an error that occurs when sending an email from the ZCO connector. User receives a bounce-back message immediately. The log file shows the next content:
2015-03-03 09:38:16,697 INFO [qtp1303093998-1651091:https://192.25.25.25:443/service/soap/SendMsgRequest] [name=user1@domain.com;mid=722;ip=192.25.25.22;ua=ZimbraConnectorForOutlook/8.0.8.1167;] smtp - Sending message to MTA at mail.domain.com: Message-ID=<9718771c.000010a4.0000000d@domain.local>, replyType=r, uploads=[Upload: { accountId=974bb8b3-29d3-4ebc-90c5-54db5d8f6082, time=Tue Mar 03 09:38:16 EST 2015, size=11171, uploadId=997abf2d-5d0b-4127-9fd8-dc2910874469:7190a6bf-954b-4b44-920a-619ea3d4170b, name=lslib32.bin, path=null }]
2015-03-03 09:38:16,708 WARN [Index-3] [name=user@domain.com;mid=286;] index - Failed to open Indexer
java.io.IOException: read past EOF
at org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:223)
at org.apache.lucene.store.BufferedIndexInput.readByte(BufferedIndexInput.java:39)
at org.apache.lucene.store.DataInput.readInt(DataInput.java:84)
at org.apache.lucene.store.BufferedIndexInput.readInt(BufferedIndexInput.java:169)
at org.apache.lucene.index.FieldsReader.detectCodeVersion(FieldsReader.java:91)
at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:303)
at org.apache.lucene.index.SegmentInfos$1.doBody(SegmentInfos.java:363)
at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:754)
at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:593)
at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:359)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1148)
at com.zimbra.cs.index.LuceneIndex$4.<init>(LuceneIndex.java:318)
at com.zimbra.cs.index.LuceneIndex.openIndexWriter(LuceneIndex.java:318)
at com.zimbra.cs.index.LuceneIndex.openWriter(LuceneIndex.java:485)
at com.zimbra.cs.index.LuceneIndex.openIndexer(LuceneIndex.java:470)
at com.zimbra.cs.mailbox.MailboxIndex.add(MailboxIndex.java:880)
at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailbox.java:8555)
at com.zimbra.cs.mailbox.MailboxIndex.indexItemList(MailboxIndex.java:763)
at com.zimbra.cs.mailbox.MailboxIndex.indexDeferredItems(MailboxIndex.java:373)
at com.zimbra.cs.mailbox.MailboxIndex.access$600(MailboxIndex.java:83)
at com.zimbra.cs.mailbox.MailboxIndex$BatchIndexTask.exec(MailboxIndex.java:1404)
at com.zimbra.cs.mailbox.MailboxIndex$IndexTask.run(MailboxIndex.java:1383)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Resolution
The issue is caused by a corrupted index for the user. To verify the issue, run the following command using the zimbra user:
zmprov verifyIndex user@example.com
You should receive an error similar to the following:
index does not exist or no segments file found: /opt/zimbra/index/~/index/~
To recreate the index, run:
zimbra@zm-nodeD:~$ zmprov rim user@example.com start status: started
- Also insufficient disk space can cause this issue. Please ensure that the index partition contains enough space.
Additional Content
- No additional content.
