The newest nightly fixed it all. Also, iOS calendar notifications seem to work 
(I did not see them work before).

Adrian

> Am 09.03.2016 um 15:34 schrieb Peter B <[email protected]>:
> 
> I guess this will be in the nightlies - I´m hoping so! Got a user that needs 
> it.
> 
> I´ve been living on nightlies since 3.0.1 and they´re great, had to roll back 
> once but as it´s packaged that´s pretty painless.
> 
> The folks working on SOGo are fantastic, can´t remember I saw such responsive 
> turn-around on an application like this. (thanks guys)
> 
> Peter.
> 
> On 09/03/2016 14:25, [email protected] wrote:
>> I can see in BTS that it's been fixed and slated for v3.0.3. is there any 
>> way to patch 3.0.2 now with this fix?
>> 
>> - Fabe
>> 
>> 
>> On 2016-03-09 03:28, Peter B wrote:
>>> I only have one iOS mobile user at the moment, so hadn't considered
>>> this serious in case it was just me (sample of one and all that). This
>>> has come up on the list a couple of times now, seems it's happening
>>> for all mobile iOS users.
>>> 
>>> So, I've just submitted a bug, http://sogo.nu/bugs/view.php?id=3571
>>> 
>>> Peter.
>>> 
>>> On 08/03/2016 23:25, Fabian Santiago wrote:
>>> 
>>>> Yes that's exactly it + some other emails, while showing me a
>>>> preview correctly, when I open them show me "message body empty /
>>>> not downloaded".
>>>> 
>>>> I can't submit the bug report myself so that would be awesome if you
>>>> or someone else did. Thanks.
>>>> 
>>>> Sincerely,
>>>> 
>>>> Fabian Santiago
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>> On Mar 8, 2016, at 4:32 PM, André Peters <[email protected]>
>>>> wrote:
>>>> 
>>>> Do mails look like this for you? ->
>>>> 
>>>> This is a cryptographically signed message in MIME format.
>>>> 
>>>> --------------ms090502040201080706050302
>>>> Content-Type: text/plain; charset=windows-1252; format=flowed
>>>> Content-Transfer-Encoding: quoted-printable
>>>> 
>>>> Okay, hat sich jetzt gerade schon etwas ver=E4ndert? Also am iPhone,
>>>> mein=
>>>> e=20
>>>> ich?
>>>> 
>>>> I have a customer reporting this and need to make sure this is the
>>>> correct problem before creating a bug report.
>>>> inverse.ca [1] changed some mime handling stuff, maybe that broke
>>>> it?
>>>> 
>>>> I don't know if he reads it, but: Ludovic Marcotte, do you need a
>>>> report/issue on Git for this?
>>>> 
>>>> Am 08.03.2016 um 19:15 schrieb Fabian Santiago:
>>>> 
>>>> Not officially on the bug tracking system no I haven't.
>>>> 
>>>> Sincerely,
>>>> 
>>>> Fabian Santiago
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>> On Mar 8, 2016, at 1:09 PM, André Peters <[email protected]>
>>>> wrote:
>>>> 
>>>> Same here... did you report it already?
>>>> 
>>>> Am 08.03.2016 um 18:28 schrieb [email protected]:
>>>> Certain email with certain encodings / mime types are being
>>>> mis-displayed on my IOS mobile device via activesync but looks fine
>>>> via IMAP. Sogo is doing something to it which did not occur in
>>>> v2.3.8; only since my v3.0.2 upgrade. any thoughts?
>>>> 
>>>> - Fabe
>>> 
>>> -- 
>>> [email protected]
>>> https://inverse.ca/sogo/lists
>>> 
>>> -- 
>>> [email protected]
>>> https://inverse.ca/sogo/lists
>>> 
>>> Links:
>>> ------
>>> [1] http://inverse.ca
> 
> -- 
> [email protected]
> https://inverse.ca/sogo/lists

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to