[imp] EAS, Android client: incoming mail sent 4x to client?

[Robin Bankhead]

Thanks for the replies, Michael and Simon.

My partner's phone is out of action and will probably get a factory  
reset soon, so I might look at this again then.

Meanwhile I brought horde up to date (webmail-5.2.1 -> 5.2.6) and  
decided to wipe and try it with my SIII.  (Nice to see wipe works,  
never tried it before!)  The mux'ed message issue didn't crop up, sure  
enough; but unfortunately that was because the phone refused to sync  
anything in my inbox that was *newer* than the end of April, and  
nothing new showed up after that either.

I do have a couple of hundred messages in my inbox, plus a lot more in  
subfolders, so this might well be part of the problem.  Generally I  
think I'm best to chalk it up to Flaky Android Client Syndrome and  
move on, making do with a plain old IMAP server for the email side of  
things.

Thanks,
Robin Bankhead

Quoting Michael J Rubinsky <mrubinsk at horde.org>:

> Also, make sure you have updated to the latest packages. There have  
> been a bunch of recent bug fixes to ActiveSync support,  including a  
> fix for duplicate emails on Outlook - maybe this fixes your issue as  
> well.
>
> -mike
> Sent from mobile. 
>
> From: Simon B <simon.buongiorno at gmail.com>
> Sent: Jun 2, 2015 7:06 AM
> To: horde at headbank.co.uk
> Cc: imp
> Subject: Re: [imp] EAS, Android client: incoming mail sent 4x to client?
>
>> On 2 Jun 2015 12:42, "Robin Bankhead" <horde at headbank.co.uk> wrote:
>>>
>>> Hi,
>>>
>>> I was setting up ActiveSync on my partner's Galaxy SII, having used it
>> for some time now on my SIII (except email sync, as support for this was
>> considered alpha at the time I set it up).  I thought I'd enable email sync
>> for her, which seemed fine initially, syncing all existing messages as
>> expected.
>>>
>>> However I then sent a test message to her account, and four copies of the
>> message appeared in the client!
>>>
>>> I won't have much time to debug this for the next while (and the client
>> works fine when the same account's configured as standard IMAP), but
>> wondered if anyone else has seen behaviour like this before and knows
>> something about the cause?
>>
>> Works fine on my S3.  Never tried it on an S2.
>>
>> Enable a debugging log for the device and do a clean sync.
>>
>> Simon
>> --
>> imp mailing list
>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>>
>
>
> -- 
> imp mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org