Tickets :: Comment on [#14323] Active Sync / Jolla + SailfishOS 2.0.1.7: Attachments arrive with 0 Byte file size

* Your Email Address
* Spam protection	Enter the letters below: . .. ..__.\ /. . \ /\|__\|\| \| >< \| \| \/ \| \|\|__\/ \\|__\|
Comment	>> Hi, >> >> I have been using Horde's ActiveSync backend with a Jolla Smartphone >> for quite a while now. >> >> The only thing that is bugging me (and it may well be related to the >> Active Sync client implementation on the Jolla phone): >> >> Attachments in mails are shown and can be queued for downloading. The >> download then takes place and it seems that the download time is >> somewhat proportional to the attachment size. (Thus, it seems as if >> an actual download is happening). >> >> But then, downloaded files end up on the Jolla's file system with 0 >> Byte of size, thus, I only get empty files. >> >> Any idea how to track this in Horde? Unfortunately, I do not have >> another Active Sync client-capable device at hand. Any recommendation >> for a non-commercial client that I can easily use for testing and as >> a reference? > > After years of developing the ActiveSync library, I have settled on > using "Nine" as the main testing platform for Android - it is, by > far, the most complete and best implementation I have found. I also > periodically test native Android and Samsung's clients as well. Nine > is not "non-commercial", but does offer a free trial that should be > long enough for you to see that attachments work. > > I have no experience with Jolla OS and have never tested our > ActiveSync code against it. If I can easily get an emulator running I > can look to see if I can reproduce the issue. > > To further debug this issue on your end, we need details of the Horde > -> Device connection. It may also be beneficial to obtain a network > capture. > > To enable debugging, see instructions contained in the ActiveSync > section of Horde's configuration. Also, see > http://wiki.horde.org/ActiveSync for more details. > > Debugging should not be enabled on a production server, Attach/post > only the portion of the log that directly deals with the problem > reported (it may be simplest to clear the log file and then perform > the event that causes the error).
Attachment
Watch this ticket

Saved Queries