Automagic Forum

When I tried using the AquaMail Tasker plugin I noticed that it has a significant shortcoming: the plugin only returns one email per mail check cycle, even if multiple messages fulfill the criteria specified in the plugin. For example, if one mail check returns 5 messages and all of them would fulfill the plugin conditions, Automagic sees only one. That's different from the K-9 Mail integration, where Automagic gets a trigger for each new email that fulfills the selection criteria.
I discussed this with the AquaMail developer, and obviously it is a limitation of the Tasker plugin architecture.

However, AquaMail has additional API functionality that allows to work around this limitation. Among other items it implements a content provider that returns all unread emails for an account. Together with the plugin as trigger (or a separate notification) it is possible to process all new mails from AquaMail.
The API functions themselves can already be utilized from Automagic without further enhancements.
But they require three additional permissions to use them without root.

It would be great if you would add the AquaMail permissions to Automagic. They are:
org.kman.AquaMail.datax.GET_ACCOUNTS
org.kman.AquaMail.datax.READ_MESSAGES
org.kman.AquaMail.datax.MESSAGE_ACTIONS
As far as I understand, they are only relevant if an Automagic user also has AquaMail installed, otherwise they would just be ignored.

A document with the API description is attached to this post, and you can find the discussion with the AquaMail developer here: http://www.aqua-mail.com/forum/index.php?topic=4476

Thanks!

I think it should not be a problem to include the permissions. I'll do so in the next EAP. Would be great if you could test if it works with aquamail when the EAP of 1.31 becomes available (will probably take a few weeks).
Such permissions have the drawback that they are usually only granted when aquamail is installed first so it's not the perfect solution but it's probably not a big problem. I'm not yet sure if there could be a problem with the Android 6 runtime permission model but testing in the EAP will show.

Thank you!!

I am happy to test when the next EAP becomes available. I subscribed to the EAP forum to get alerted when the next version becomes available.