[Solved] Autoconfiguration not working for iOS / Z-Push Support

Please tell me the path to the sendmail config. What permissions do I need?
chown to what and chmod 755?

That is out of my realms of expertise :sweat_smile: The default mailinabox settings work.

Edit: Looking on google for this error message for sendmail it could actually be anything. A couple of things that stand out is.

  • Run out of disk space (could have happened with all the Z-Push debug logs)

  • permissions on sendmail configuration

  • other error that may be in the mail logs.

Can anyone confirm, these are the right permissions:
root@box:/usr/local/lib/z-push# ls -ls /usr/sbin/sendmail
28 -rwxr-xr-x 1 root root 26848 Jan 29 09:02 /usr/sbin/sendmail

root@box:/usr/local/lib/z-push# ls -ls /usr/lib/sendmail
0 lrwxrwxrwx 1 root root 16 Jan 29 09:02 /usr/lib/sendmail → …/sbin/sendmail

Disk space is not a problem.

root@mail:~# cd /usr/local/lib/z-push
root@mail:/usr/local/lib/z-push# ls -ls /usr/sbin/sendmail
32 -rwxr-xr-x 1 root root 31184 Jan 29 03:02 /usr/sbin/sendmail
root@mail:/usr/local/lib/z-push#

I get a lot of these:

13/05/2024 07:53:19 [1180019] [FATAL] [emailaccount@domain.tld] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
13/05/2024 10:44:06 [1180017] [FATAL] [emailaccount@domain.tld] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
13/05/2024 16:43:25 [1180015] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:27 [1180023] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:30 [1180025] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:31 [1180026] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:32 [1180018] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:33 [1180021] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:34 [1180020] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:35 [1180022] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:36 [1180015] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:37 [1180024] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:38 [1180023] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:39 [1180017] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:40 [1180016] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:41 [1180019] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:41 [1180025] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:43 [1180026] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:44 [1180018] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:45 [1180021] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:46 [1180020] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:47 [1180022] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:48 [1180015] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:50 [1180024] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:51 [1180023] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:52 [1180017] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:43:53 [1180016] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:45:19 [1180026] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:45:24 [1180023] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:45:25 [1180015] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:45:27 [1180019] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:45:28 [1180020] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:45:30 [1180016] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:45:31 [1180018] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
13/05/2024 16:45:33 [1180022] [WARN] [emailaccount@domain.tld] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict

It would almost seem like php isn’t powerful enough to process large mailboxes.

These messages should settle down after a while. I think it was overnight when we were doing a lot of testing last year.

I wouldn’t just blame PHP, I think it is a combination of a few things. If this is a sticking point, would appreciate it if you or someone else would lodge an issue on Github. I’m trying to be user reported issues focused so I don’t hobby horse my own personal use cases over others.

Edit: also sorry @zoof for hijacking your thread.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.