Relationship Graph

View IssueDependency GraphShow Summary
Relationship Graph
related to related to child of child of duplicate of duplicate of

View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004618SOGoActiveSyncpublic2018-12-05 12:532019-02-18 19:35
Reporterasepulveda Assigned Toludovic  
PriorityhighSeveritycrashReproducibilityalways
Status closedResolutionno change required 
Platformevery email clientsOSevery OS 
Product Version4.0.4 
Summary0004618: Active Sync is not working
Description

Hello

Today we updated SOGo 4.0.4 to the last nigthly update and now, the emails´s reception in ActiveSync configured accounts is not working because the new emails can´t been shown.

The log generated is:
<0x0x7faded2c0e70[NGImap4Client]> ERROR(-[NGImap4Client _processUnknownCommandParserException:]): catched non-IMAP4 parsing exception NGCouldNotOpenStreamException: could not open stream

This error does not appears in simple Imap accounts and SOGo Webmail, only appears in ActiveSync configuration.

Steps To Reproduce

Configure an acount with ActiveSync protocol

Additional Information

<0x0x7faded2c0e70[NGImap4Client]> ERROR(-[NGImap4Client _processUnknownCommandParserException:]): catched non-IMAP4 parsing exception NGCouldNotOpenStreamException: could not open stream

TagsNo tags attached.

Activities

ludovic

ludovic

2018-12-05 13:18

administrator   ~0013215

Your IMAP server is down.
asepulveda

asepulveda

2018-12-05 13:45

reporter   ~0013216

Hello

The IMAP server is working.

The issue only appears configuring the accounts using ActiveSync protocol. If we configure the same accounts using IMAP, the reception works fine.

Regards
asepulveda

asepulveda

2018-12-10 15:46

reporter   ~0013220

Hello

Could you see the problem?

Regards
tfu

tfu

2018-12-18 20:26

reporter   ~0013226

You could try to set ImapDebugEnabled = YES; in sogo.conf. With this parameter you will see more details about the imap-commands sent from sogo.
asepulveda

asepulveda

2018-12-19 09:52

reporter   ~0013227

Hello

We have updated the SOGo version and now the problem is fixed.

Thank you for the support
Regards

Issue History

Date Modified Username Field Change
2018-12-05 12:53 asepulveda New Issue
2018-12-05 13:18 ludovic Note Added: 0013215
2018-12-05 13:18 ludovic Status new => closed
2018-12-05 13:18 ludovic Assigned To => ludovic
2018-12-05 13:18 ludovic Resolution open => no change required
2018-12-05 13:45 asepulveda Note Added: 0013216
2018-12-05 13:45 asepulveda Status closed => feedback
2018-12-05 13:45 asepulveda Resolution no change required => reopened
2018-12-10 15:46 asepulveda Note Added: 0013220
2018-12-10 15:46 asepulveda Status feedback => assigned
2018-12-18 20:26 tfu Note Added: 0013226
2018-12-19 09:52 asepulveda Note Added: 0013227
2019-02-18 19:35 ludovic Status assigned => closed
2019-02-18 19:35 ludovic Resolution reopened => no change required