Version 1.10.0-379-dev - "work in progress", not in Google Play

[Kostya Vasilyev]

Re: I have a Moto G5 Plus, Android 7.0

Moto is pretty much same as Nexus - "pure" Android, and the Contacts app there isn't good with Groups.

Re: birthdays

Yes I see it now.

Must be a side effect of "time zones" and how I'm now storing events (birthdays, wedding anniversaries) in the UTC time zone (I thought this is what Android wanted... and this is how Exchange returns them).

I'll file a bug report.

[Kostya Vasilyev]

Re: If I add a birthday, something happens with the date on my Calendar App that shows the contact birthday for 2 days, instead of just one day.

I hope this is fixed in build 369 (in this topic header).

[hzamora]

Thanks. It is working!

Regards...

[Kostya Vasilyev]

Re: Thanks. It is working!

Good

[mauri_va]

Thanks for this dev builds!
I was redirected here following my request if Aqua-mail will support oauth authentication for yahoo account and the answer is yes!
Purchased pro key, I'm testing the 367 build.
Yahoo account seems to work, although sometimes it seems to "fall asleep": sincronization sometimes seems don't happen and in this 2 days I've got also an error in sincronization (I just saw a red exclamation point next to the last sync time). This morning, just turned on my cell phone, all my mail accounts synced, except for yahoo... But during this day it seemed to work properly.
A question: I see that the "push" option is not available for yahoo account. Yahoo does not allow this option or this will be implemented in future?

Thank you for all your great work!

[Kostya Vasilyev]

Yahoo account seems to work, although sometimes it seems to "fall asleep": sincronization sometimes seems don't happen and in this 2 days I've got also an error in sincronization (I just saw a red exclamation point next to the last sync time). This morning, just turned on my cell phone, all my mail accounts synced, except for yahoo...

That "red last sync time" mean -- that the app tried, but ran into network / connectivity errors. Could be some other thing not OAUTH (remember that OAUTH2 is just a particular way to log in, nothing else).

I'd say keep an eye on it and see how it behaves, write back if this remains.

Re: push

For push mail, for "Internet Mail" (IMAP) accounts, Aqua Mail uses the industry standard, well documented, widely supported "IDLE" extension.

It is supported / used by: Gmail, AOL, Hotmail, Yandex, GMX, Fastmail, Web.de services and others, and also servers like Dovecot, Courier, Cyrus and others.

Yahoo however chose to not implement it. I believe they have their own mechanism for push mail which they'd worked out with Apple and which is undocumented.

[FuFa]

Hi,

as I'm currently testing Exchange Online, I found that AquaMail is almost the only app that includes the contacts and calendar sync also for shared mailboxes! Thanks for that, great tool!! :-)

One issue I found with the 1.10 dev builds is the contact sync with a shared exchange mailbox account. It seams it is syncing the contacts from the main account, not from the shared mailbox entered in the account settings.

Is this a bug or did I understood this function wrong?

[Kostya Vasilyev]

One issue I found with the 1.10 dev builds is the contact sync with a shared exchange mailbox account. It seams it is syncing the contacts from the main account, not from the shared mailbox entered in the account settings.

Um, just something I forgot to keep in mind in the contacts code. I'll make a note to fix this.

[Kostya Vasilyev]

Re: contact sync with a shared exchange mailbox account

Should be fixed in build 372 (the link is above).

[FuFa]

Have you tested calendar invitations? Would you please tell me if it's working (accept, maybe, decline invitations, sent and received by AquaMail). Thank you

I made some tests between the main Exchange account and the shared mailbox calendar (two separate accounts in AM). As far as I can see everything works as expected.

I use Business Calendar 2 as calendar app, created an appointment on the shared calendar and invited the main account. Invitation was synced correctly to main account calendar and I can switch status there. Status was reflected correctly in the original appointment in shared calendar. Also canceling or declining the appointment/invitation removes it correctly from the calendar.

Not sure if the calendar app has an influence here, or the used mailbox account type. But in my setup it looks fine! 

[FuFa]

Re: contact sync with a shared exchange mailbox account

Should be fixed in build 372 (the link is above).

Tested and verified successfully 

Thanks alot!

[FuFa]

Have you tested calendar invitations? Would you please tell me if it's working (accept, maybe, decline invitations, sent and received by AquaMail). Thank you

I made some tests between the main Exchange account and the shared mailbox calendar (two separate accounts in AM). As far as I can see everything works as expected.

I use Business Calendar 2 as calendar app, created an appointment on the shared calendar and invited the main account. Invitation was synced correctly to main account calendar and I can switch status there. Status was reflected correctly in the original appointment in shared calendar. Also canceling or declining the appointment/invitation removes it correctly from the calendar.

Not sure if the calendar app has an influence here, or the used mailbox account type. But in my setup it looks fine! 

Thank you. Are you accepting /declining meeting invitations in AquaMail attachements? Or you're simply using calendar events in the calendar app to accept /decline them?

Hm, I did all the actions in the calendar app. I will try to repeat it from within AM directly.

[FuFa]

Have you tested calendar invitations? Would you please tell me if it's working (accept, maybe, decline invitations, sent and received by AquaMail). Thank you

I made some tests between the main Exchange account and the shared mailbox calendar (two separate accounts in AM). As far as I can see everything works as expected.

I use Business Calendar 2 as calendar app, created an appointment on the shared calendar and invited the main account. Invitation was synced correctly to main account calendar and I can switch status there. Status was reflected correctly in the original appointment in shared calendar. Also canceling or declining the appointment/invitation removes it correctly from the calendar.

Not sure if the calendar app has an influence here, or the used mailbox account type. But in my setup it looks fine! 

Thank you. Are you accepting /declining meeting invitations in AquaMail attachements? Or you're simply using calendar events in the calendar app to accept /decline them?

Hm, I did all the actions in the calendar app. I will try to repeat it from within AM directly.

I created a second account now in Exchange Online and did the test again with this account directly from OWA (without having it in AM or on my phone at all).

Send invitations to the account in AM then from the new account, in AM I opened the invitation mail and used the buttons there to respond. Accept, Decline and Maybe, all replies were shown in the original appointment correctly in the invitators account. In AM I can also see the sent response mails, Accepted:, Declined: and Tentative:.

Was this what you were asking for? It looks like it works correctly, at least between two Exchange accounts.

[FuFa]

One last thing that would make the Exchange integration perfect 

In this thread there was a discussion about allowing "identities" also for Exchange accounts:

https://www.aqua-mail.com/forum/index.php?topic=4940.msg28694#msg28694

I think the proposed solution would work, as the same way it is done in Outlook. Are there any plans to add this feature currently? I could easily test it as long as my Exchange Online test period is running :-)

[Kostya Vasilyev]

I think the proposed solution would work, as the same way it is done in Outlook. Are there any plans to add this feature currently? I could easily test it as long as my Exchange Online test period is running :-)

No we're not working on that right now, sorry.