User unable to send email using Zimbra Connector for Outlook

User unable to send email using Zimbra Connector for Outlook

   KB 21737        Last updated on 2015-07-13  

(0 votes)


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:] [;mid=722;ip=;ua=ZimbraConnectorForOutlook/;] smtp - Sending message to MTA at 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] [;mid=286;] index - Failed to open Indexer read past EOF
                    at org.apache.lucene.index.FieldsReader.detectCodeVersion(
                    at org.apache.lucene.index.SegmentInfos$1.doBody(
                    at org.apache.lucene.index.SegmentInfos$
                    at org.apache.lucene.index.SegmentInfos$
                    at org.apache.lucene.index.IndexWriter.<init>(
                    at com.zimbra.cs.index.LuceneIndex$4.<init>(
                    at com.zimbra.cs.index.LuceneIndex.openIndexWriter(
                    at com.zimbra.cs.index.LuceneIndex.openWriter(
                    at com.zimbra.cs.index.LuceneIndex.openIndexer(
                    at com.zimbra.cs.mailbox.MailboxIndex.add(
                    at com.zimbra.cs.mailbox.Mailbox.endTransaction(
                    at com.zimbra.cs.mailbox.MailboxIndex.indexItemList(
                    at com.zimbra.cs.mailbox.MailboxIndex.indexDeferredItems(
                    at com.zimbra.cs.mailbox.MailboxIndex.access$600(
                    at com.zimbra.cs.mailbox.MailboxIndex$BatchIndexTask.exec(
                    at com.zimbra.cs.mailbox.MailboxIndex$
                    at java.util.concurrent.Executors$
                    at java.util.concurrent.ThreadPoolExecutor.runWorker(
                    at java.util.concurrent.ThreadPoolExecutor$


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

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 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.

Verified Against: Zimbra Collaboration 8.6, 8.5, 8.0 Date Created: 02/24/2015
Article ID: Date Modified: 2015-07-13

Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »

Wiki/KB reviewed by John Jorge Jenny Last edit by Jorge de la Cruz
Jump to: navigation, search