you using ipad mail app? because I’m loading multiple mail account from 3 devices (I use Spark mail on all my apple devices) and I don’t have any more issues after.
It only happens to the mail account which I use to load /admin /cloud and /mail (sometimes)
I deleted my account again on MS Outlook on the ipad. I stopped dovecot and the logging was quiet. I added my MIAB account to the iOS mail app, and bingo, started getting the rapid & relatively continuous logins from dovecot on imap.
So the point is it’s not limited to MS Outlook on the ipad.
I just tried ios mail app + exchange and withnessed the problem.
Your solution would be not to use Microsoft Exchange set up, and to use IMAP set setup, then you can set up CardDav and CalDav separately if you are using them. I tried it and it works fine.
warning reflected in your mail set up instructions in /admin page
The problem with this approach is that iOS mail clients, including the default Mail app, don’t seem to support Push when using IMAP. At least I haven’t found any that reliably do support Push for IMAP accounts. I think it’s precisely this Push support that causes Z-Push to log in to the internal IMAP server so often. Personally, I don’t really see a problem as long as it works.
I’m not sure whther it’s about PUSH (it works fine when we set up as IMAP account), or got to do with the following logs, where Exchange (When we set it up as MS Exchange account) is trying to authenticate with both LOGIN (via smtp) and PLAIN method. This may be the cause?
Mar 17 22:18:56 imap-login: Info: Login: user=<me@mydomain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=25588, TLS, session=<nhHSKby9wol/AAAB>
Mar 17 22:18:56 imap-login: Info: Login: user=<me@mydomain.com>, method=LOGIN, rip=127.0.0.1, lip=127.0.0.1, mpid=25590, secured, session=<Ds/TKby9OIh/AAAB>
Mar 17 22:18:56 imap(me@mydomain.com): Info: Logged out in=28 out=800
If we were to use normal imap connection, then it will only be PLAIN method.
UPDATE: Then in the z-push at the same time.
17/03/2021 22:17:20 [23805] [WARN] [me@mydomain.com] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
17/03/2021 22:17:21 [24024] [WARN] [me@mydomain.com] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
17/03/2021 22:17:22 [23805] [WARN] [me@mydomain.com] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
17/03/2021 22:17:23 [24024] [WARN] [me@mydomain.com] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
17/03/2021 22:17:24 [23805] [WARN] [me@mydomain.com] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
17/03/2021 22:17:24 [24024] [WARN] [me@mydomain.com] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
17/03/2021 22:17:25 [23805] [WARN] [me@mydomain.com] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
17/03/2021 22:17:27 [24024] [WARN] [me@mydomain.com] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
17/03/2021 22:17:27 [23805] [WARN] [me@mydomain.com] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict