Hi,
I have just started playing around with sogo 2.2.3/activesync with
outlook 2013. Using the 'documented tric' I can connect, and it starts
syncing, however various issues show up:
* I see MANY (211482!! to be precise) files like
"/tmp/OGo7F7D534EF0071249.tmp"
* eventually WOWatchDogChild kills the pid after ten minutes ('safety belt')
* Errors in sogo.log like
2014-04-17 03:22:29.394 sogod[22920] _consume[1343]: error try to read
over buffer len self->dataIdx 55 _cnt 1 byteLen 55
Apr 17 03:22:29 sogod [22920]: <0x0x7fb4f8116bc0[NGMimeBodyPartParser]>
WARNING(-[NGMimePartParser parseHeader]:706): 2 an error occured during
body parsing (maybe end of stream)
* Errors in sogo.log like
Apr 17 03:21:17 sogod [22920]: [WARN] <0x0x7fb4eeb745a0[NSDataMalloc]>
-[NSData(MIMEContentTransferEncoding)
dataByApplyingMimeContentTransferEncoding:]: unknown
content-transfer-encoding: '8-bit'
Apr 17 03:21:17 sogod [22920]: <0x0x7fb4eeb71420[NGMimeMessageParser]>
WARNING(-[NGMimePartParser readBody]): encountered unknown
content-transfer-encoding: '8-bit'
* and errors in sogo.log like:
Apr 17 03:20:30 sogod [22920]: <0x0x7fb4e62afb40[GSCBufferString]> Got
invalid multibyte sequence. ToEncode: US-ASCII FromEncode: UCS-2LE.
To get this far, I had to add "ulimit -n 65536" to /etc/init.d/sogo.
The question really is: The level of development on ActiveSync seems
pretty high now, so should I just wait for 2.2.4 and find many of the
issues above fixed..?
Regards,
MJ
--
users@sogo.nu
https://inverse.ca/sogo/lists
