iphone (IOS) not able to send mails
-
I am facing a strange behavior. Z-push is working nicely on my server with 3 different device types connected. Outlook / android and IOS.
Strangely IOS is not able to send mails, Outlook and Android can. I have tried it with 3 different users. Every time IOS is not able to send mails -> "Cannot Send Mail | Check the settings for the outgoing servers in settings -> Mail -> Accounts.
It looks like the provisioning is not setting the outgoing servers up for the iphones.
Has someone experienced this already? I have checked the other not able to send mails threads but they seem to have sending not working at all… for me it is just the iphones.
Thanks for any hint ;-)
-
This issue (ZP-1588) is already known, but unfortunately nobody has found a solution yet.
For me it is working fine - no problem at all.One question I have for you is - are you using Device Provisioning in z-push/config.php ? That has never been discussed before…
( define(‘PROVISIONING’, true); ) -
Yes, i have also tried to change it to false with the same effect :-(
<?php /*********************************************** * File : config.php * Project : Z-Push * Descr : Main configuration file * * Created : 01.10.2007 * * Copyright 2007 - 2016 Zarafa Deutschland GmbH * * This program is free software: you can redistribute it and/or modify * it under the terms of the GNU Affero General Public License, version 3, * as published by the Free Software Foundation. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU Affero General Public License for more details. * * You should have received a copy of the GNU Affero General Public License * along with this program. If not, see <http://www.gnu.org/licenses/>. * * Consult LICENSE file for details ************************************************/ /********************************************************************************** * Default settings */ // Defines the default time zone, change e.g. to "Europe/London" if necessary define('TIMEZONE', 'Europe/Berlin'); // Defines the base path on the server define('BASE_PATH', dirname($_SERVER['SCRIPT_FILENAME']). '/'); // Try to set unlimited timeout define('SCRIPT_TIMEOUT', 0); // This should be solved on THE webserver level if there are proxies // between mobile client and Z-Push. // IMPORTANT: This setting will be deprecated in Z-Push 2.7.0. // Use a custom header to determinate the remote IP of a client. // By default, the server provided REMOTE_ADDR is used. If the header here set // is available, the provided value will be used, else REMOTE_ADDR is maintained. // set to false to disable this behaviour. // common values: 'HTTP_X_FORWARDED_FOR', 'HTTP_X_REAL_IP' (casing is ignored) define('USE_CUSTOM_REMOTE_IP_HEADER', false); // When using client certificates, we can check if the login sent matches the owner of the certificate. // This setting specifies the owner parameter in the certificate to look at. define("CERTIFICATE_OWNER_PARAMETER", "SSL_CLIENT_S_DN_CN"); /* * Whether to use the complete email address as a login name * (e.g. user@company.com) or the username only (user). * This is required for Z-Push to work properly after autodiscover. * Possible values: * false - use the username only. * true - string the mobile sends as username, e.g. full email address (default). */ define('USE_FULLEMAIL_FOR_LOGIN', false); /********************************************************************************** * StateMachine setting * * These StateMachines can be used: * FILE - FileStateMachine (default). Needs STATE_DIR set as well. * SQL - SqlStateMachine has own configuration file. STATE_DIR is ignored. * State migration script is available, more informations: https://wiki.z-hub.io/x/xIAa */ define('STATE_MACHINE', 'FILE'); define('STATE_DIR', '/var/lib/z-push/'); /********************************************************************************** * IPC - InterProcessCommunication * * Is either provided by using shared memory on a single host or * using the memcache provider for multi-host environments. * When another implementation should be used, the class can be set here explicitly. * If empty Z-Push will try to use available providers. * Possible values: * IpcSharedMemoryProvider - default. Requires z-push-ipc-sharedmemory package. * IpcMemcachedProvider - requires z-push-ipc-memcached package. It is necessary to set up * memcached server before (it won't be installed by z-push-ipc-memcached). * IpcWincacheProvider - for windows systems. */ define('IPC_PROVIDER', 'IpcSharedMemoryProvider'); /********************************************************************************** * Logging settings * * The LOGBACKEND specifies where the logs are sent to. * Either to file ("filelog") or to a "syslog" server or a custom log class in core/log/logclass. * filelog and syslog have several options that can be set below. * For more information about the syslog configuration, see https://wiki.z-hub.io/x/HIAT * Possible LOGLEVEL and LOGUSERLEVEL values are: * LOGLEVEL_OFF - no logging * LOGLEVEL_FATAL - log only critical errors * LOGLEVEL_ERROR - logs events which might require corrective actions * LOGLEVEL_WARN - might lead to an error or require corrective actions in the future * LOGLEVEL_INFO - usually completed actions * LOGLEVEL_DEBUG - debugging information, typically only meaningful to developers * LOGLEVEL_WBXML - also prints the WBXML sent to/from the device * LOGLEVEL_DEVICEID - also prints the device id for every log entry * LOGLEVEL_WBXMLSTACK - also prints the contents of WBXML stack * * The verbosity increases from top to bottom. More verbose levels include less verbose * ones, e.g. setting to LOGLEVEL_DEBUG will also output LOGLEVEL_FATAL, LOGLEVEL_ERROR, * LOGLEVEL_WARN and LOGLEVEL_INFO level entries. * * LOGAUTHFAIL is logged to the LOGBACKEND. */ define('LOGBACKEND', 'filelog'); define('LOGLEVEL', LOGLEVEL_WARN); define('LOGAUTHFAIL', true); // To save e.g. WBXML data only for selected users, add the usernames to the array // The data will be saved into a dedicated file per user in the LOGFILEDIR // Users have to be encapusulated in quotes, several users are comma separated, like: // $specialLogUsers = array('info@domain.com', 'myusername'); define('LOGUSERLEVEL', LOGLEVEL_DEVICEID); $specialLogUsers = array(); // Filelog settings define('LOGFILEDIR', '/var/log/z-push/'); define('LOGFILE', LOGFILEDIR . 'z-push.log'); define('LOGERRORFILE', LOGFILEDIR . 'z-push-error.log'); // Syslog settings // false will log to local syslog, otherwise put the remote syslog IP here define('LOG_SYSLOG_HOST', false); // Syslog port define('LOG_SYSLOG_PORT', 514); // Program showed in the syslog. Useful if you have more than one instance login to the same syslog define('LOG_SYSLOG_PROGRAM', 'z-push'); // Syslog facility - use LOG_USER when running on Windows define('LOG_SYSLOG_FACILITY', LOG_LOCAL0); // Location of the trusted CA, e.g. '/etc/ssl/certs/EmailCA.pem' // Uncomment and modify the following line if the validation of the certificates fails. // define('CAINFO', '/etc/ssl/certs/EmailCA.pem'); /********************************************************************************** * Mobile settings */ // Device Provisioning define('PROVISIONING', true); // This option allows the 'loose enforcement' of the provisioning policies for older // devices which don't support provisioning (like WM 5 and HTC Android Mail) - dw2412 contribution // false (default) - Enforce provisioning for all devices // true - allow older devices, but enforce policies on devices which support it define('LOOSE_PROVISIONING', false); // The file containing the policies' settings. // Set a full path or relative to the z-push main directory define('PROVISIONING_POLICYFILE', 'policies.ini'); // Default conflict preference // Some devices allow to set if the server or PIM (mobile) // should win in case of a synchronization conflict // SYNC_CONFLICT_OVERWRITE_SERVER - Server is overwritten, PIM wins // SYNC_CONFLICT_OVERWRITE_PIM - PIM is overwritten, Server wins (default) define('SYNC_CONFLICT_DEFAULT', SYNC_CONFLICT_OVERWRITE_PIM); // Global limitation of items to be synchronized // The mobile can define a sync back period for calendar and email items // For large stores with many items the time period could be limited to a max value // If the mobile transmits a wider time period, the defined max value is used // Applicable values: // SYNC_FILTERTYPE_ALL (default, no limitation) // SYNC_FILTERTYPE_1DAY, SYNC_FILTERTYPE_3DAYS, SYNC_FILTERTYPE_1WEEK, SYNC_FILTERTYPE_2WEEKS, // SYNC_FILTERTYPE_1MONTH, SYNC_FILTERTYPE_3MONTHS, SYNC_FILTERTYPE_6MONTHS define('SYNC_FILTERTIME_MAX', SYNC_FILTERTYPE_ALL); // Interval in seconds before checking if there are changes on the server when in Ping. // It means the highest time span before a change is pushed to a mobile. Set it to // a higher value if you have a high load on the server. define('PING_INTERVAL', 30); // Set the fileas (save as) order for contacts in the webaccess/webapp/outlook. // It will only affect new/modified contacts on the mobile which then are synced to the server. // Possible values are: // SYNC_FILEAS_FIRSTLAST - fileas will be "Firstname Middlename Lastname" // SYNC_FILEAS_LASTFIRST - fileas will be "Lastname, Firstname Middlename" // SYNC_FILEAS_COMPANYONLY - fileas will be "Company" // SYNC_FILEAS_COMPANYLAST - fileas will be "Company (Lastname, Firstname Middlename)" // SYNC_FILEAS_COMPANYFIRST - fileas will be "Company (Firstname Middlename Lastname)" // SYNC_FILEAS_LASTCOMPANY - fileas will be "Lastname, Firstname Middlename (Company)" // SYNC_FILEAS_FIRSTCOMPANY - fileas will be "Firstname Middlename Lastname (Company)" // The company-fileas will only be set if a contact has a company set. If one of // company-fileas is selected and a contact doesn't have a company set, it will default // to SYNC_FILEAS_FIRSTLAST or SYNC_FILEAS_LASTFIRST (depending on if last or first // option is selected for company). // If SYNC_FILEAS_COMPANYONLY is selected and company of the contact is not set // SYNC_FILEAS_LASTFIRST will be used define('FILEAS_ORDER', SYNC_FILEAS_LASTFIRST); // Maximum amount of items to be synchronized per request. // Normally this value is requested by the mobile. Common values are 5, 25, 50 or 100. // Exporting too much items can cause mobile timeout on busy systems. // Z-Push will use the lowest provided value, either set here or by the mobile. // MS Outlook 2013+ request up to 512 items to accelerate the sync process. // If you detect high load (also on subsystems) you could try a lower setting. // max: 512 - value used if mobile does not limit amount of items define('SYNC_MAX_ITEMS', 512); // The devices usually send a list of supported properties for calendar and contact // items. If a device does not includes such a supported property in Sync request, // it means the property's value will be deleted on the server. // However some devices do not send a list of supported properties. It is then impossible // to tell if a property was deleted or it was not set at all if it does not appear in Sync. // This parameter defines Z-Push behaviour during Sync if a device does not issue a list with // supported properties. // See also https://jira.z-hub.io/browse/ZP-302. // Possible values: // false - do not unset properties which are not sent during Sync (default) // true - unset properties which are not sent during Sync define('UNSET_UNDEFINED_PROPERTIES', false); // ActiveSync specifies that a contact photo may not exceed 48 KB. This value is checked // in the semantic sanity checks and contacts with larger photos are not synchronized. // This limitation is not being followed by the ActiveSync clients which set much bigger // contact photos. You can override the default value of the max photo size. // default: 5242880 - 5 MB default max photo size in bytes define('SYNC_CONTACTS_MAXPICTURESIZE', 5242880); // Over the WebserviceUsers command it is possible to retrieve a list of all // known devices and users on this Z-Push system. The authenticated user needs to have // admin rights and a public folder must exist. // In multicompany environments this enable an admin user of any company to retrieve // this full list, so this feature is disabled by default. Enable with care. define('ALLOW_WEBSERVICE_USERS_ACCESS', false); // Users with many folders can use the 'partial foldersync' feature, where the server // actively stops processing the folder list if it takes too long. Other requests are // then redirected to the FolderSync to synchronize the remaining items. // Device compatibility for this procedure is not fully understood. // NOTE: THIS IS AN EXPERIMENTAL FEATURE WHICH COULD PREVENT YOUR MOBILES FROM SYNCHRONIZING. define('USE_PARTIAL_FOLDERSYNC', false); // The minimum accepted time in second that a ping command should last. // It is strongly advised to keep this config to false. Some device // might not be able to send a higher value than the one specificied here and thus // unable to start a push connection. // If set to false, there will be no lower bound to the ping lifetime. // The minimum accepted value is 1 second. The maximum accepted value is 3540 seconds (59 minutes). define('PING_LOWER_BOUND_LIFETIME', false); // The maximum accepted time in second that a ping command should last. // If set to false, there will be no higher bound to the ping lifetime. // The minimum accepted value is 1 second. The maximum accepted value is 3540 seconds (59 minutes). define('PING_HIGHER_BOUND_LIFETIME', false); // Maximum response time // Mobiles implement different timeouts to their TCP/IP connections. Android devices for example // have a hard timeout of 30 seconds. If the server is not able to answer a request within this timeframe, // the answer will not be recieved and the device will send a new one overloading the server. // There are three categories // - Short timeout - server has up within 30 seconds - is automatically applied for not categorized types // - Medium timeout - server has up to 90 seconds to respond // - Long timeout - server has up to 4 minutes to respond // If a timeout is almost reached the server will break and sent the results it has until this // point. You can add DeviceType strings to the categories. // In general longer timeouts are better, because more data can be streamed at once. define('SYNC_TIMEOUT_MEDIUM_DEVICETYPES', "SAMSUNGGTI"); define('SYNC_TIMEOUT_LONG_DEVICETYPES', "iPod, iPad, iPhone, WP, WindowsOutlook, WindowsMail"); // Time in seconds the device should wait whenever the service is unavailable, // e.g. when a backend service is unavailable. // Z-Push sends a "Retry-After" header in the response with the here defined value. // It is up to the device to respect or not this directive so even if this option is set, // the device might not wait requested time frame. // Number of seconds before retry, to disable set to: false define('RETRY_AFTER_DELAY', 300); /********************************************************************************** * Backend settings */ // The backend data provider. // Leave this value empty and Z-Push will autoload a backend. The sequence of autoload is: // BackendKopano, BackendCombined, BackendIMAP, BackendVCardDir, BackendMaildir. // If BackendKopano is not installed, Z-Push will load BackendCombined. If BackendCombined // also is not installed, Z-Push will load BackendIMAP and so on. // If you prefer explicitly configure a backend provider, currently possible values are: // BackendKopano - to use with the Kopano groupware. Syncs emails, calendar items, // contacts, tasks and notes or any combination of the listed items. // BackendCombined - combine multiple backends for different items, e.g. // BackendIMAP for emails, BackendCalDAV for calendar items, // BackendCardDAV for contacts etc. You can configure what backend // syncs which items in /etc/combined.conf.php. // BackendIMAP - to sync emails with an IMAP server. // BackendCalDAV - to sync calendar items and / or tasks with a CalDAV server. // BackendCardDAV - to sync contacts with a CardDAV server. // BackendMaildir - to sync emails from a Maildir. // BackendStickyNote - to sync notes with a Postgres server. // BackendVCardDir - to sync contacts with vcard folder. define('BACKEND_PROVIDER', 'BackendCombined'); //define('BACKEND_PROVIDER', 'BackendIMAP'); /********************************************************************************** * Search provider settings * * Alternative backend to perform SEARCH requests (GAL search) * By default the main Backend defines the preferred search functionality. * If set, the Search Provider will always be preferred. * Use 'BackendSearchLDAP' to search in a LDAP directory (see backend/searchldap/config.php) */ define('SEARCH_PROVIDER', ''); // Time in seconds for the server search. Setting it too high might result in timeout. // Setting it too low might not return all results. Default is 10. define('SEARCH_WAIT', 10); // The maximum number of results to send to the client. Setting it too high // might result in timeout. Default is 10. define('SEARCH_MAXRESULTS', 10); /********************************************************************************** * Kopano Outlook Extension - Settings * * The Kopano Outlook Extension (KOE) provides MS Outlook 2013 and newer with * functionality not provided by ActiveSync or not implemented by Outlook. * For more information, see: https://wiki.z-hub.io/x/z4Aa */ // Global Address Book functionality define('KOE_CAPABILITY_GAB', true); // Synchronize mail flags from the server to Outlook/KOE define('KOE_CAPABILITY_RECEIVEFLAGS', true); // Encode flags when sending from Outlook/KOE define('KOE_CAPABILITY_SENDFLAGS', true); // Out-of-office support define('KOE_CAPABILITY_OOF', true); // Out-of-office support with start & end times (superseeds KOE_CAPABILITY_OOF) define('KOE_CAPABILITY_OOFTIMES', true); // Notes support define('KOE_CAPABILITY_NOTES', true); // Shared folder support define('KOE_CAPABILITY_SHAREDFOLDER', true); // Send-As support for Outlook/KOE and mobiles define('KOE_CAPABILITY_SENDAS', true); // Secondary Contact folders (own and shared) define('KOE_CAPABILITY_SECONDARYCONTACTS', true); // Copy WebApp signature into KOE define('KOE_CAPABILITY_SIGNATURES', true); // Delivery receipt requests define('KOE_CAPABILITY_RECEIPTS', true); // Impersonate other users define('KOE_CAPABILITY_IMPERSONATE', true); // To synchronize the GAB KOE, the GAB store and folderid need to be specified. // Use the gab-sync script to generate this data. The name needs to // match the config of the gab-sync script. // More information here: https://wiki.z-hub.io/x/z4Aa (GAB Sync Script) define('KOE_GAB_STORE', 'SYSTEM'); define('KOE_GAB_FOLDERID', ''); define('KOE_GAB_NAME', 'Z-Push-KOE-GAB'); /********************************************************************************** * Synchronize additional folders to all mobiles * * With this feature, special folders can be synchronized to all mobiles. * This is useful for e.g. global company contacts. * * This feature is supported only by certain devices, like iPhones. * Check the compatibility list for supported devices: * http://z-push.org/compatibility * * To synchronize a folder, add a section setting all parameters as below: * store: the ressource where the folder is located. * Kopano users use 'SYSTEM' for the 'Public Folder' * folderid: folder id of the folder to be synchronized * name: name to be displayed on the mobile device * type: supported types are: * SYNC_FOLDER_TYPE_USER_CONTACT * SYNC_FOLDER_TYPE_USER_APPOINTMENT * SYNC_FOLDER_TYPE_USER_TASK * SYNC_FOLDER_TYPE_USER_MAIL * SYNC_FOLDER_TYPE_USER_NOTE * flags: sets additional options on the shared folder. Supported are: * DeviceManager::FLD_FLAGS_NONE * No flags configured, default flag to be set * DeviceManager::FLD_FLAGS_SENDASOWNER * When replying in this folder, automatically do Send-As * DeviceManager::FLD_FLAGS_CALENDARREMINDERS * If set, Outlook shows reminders for these shares with KOE * DeviceManager::FLD_FLAGS_NOREADONLYNOTIFY * If set, Z-Push won't send notification emails for changes * if the folder is read-only * * Additional notes: * - on Kopano systems use backend/kopano/listfolders.php script to get a list * of available folders * * - all Z-Push users must have at least reading permissions so the configured * folders can be synchronized to the mobile. Else they are ignored. * * - this feature is only partly suitable for multi-tenancy environments, * as ALL users from ALL tenents need access to the configured store & folder. * When configuring a public folder, this will cause problems, as each user has * a different public folder in his tenant, so the folder are not available. * - changing this configuration could cause HIGH LOAD on the system, as all * connected devices will be updated and load the data contained in the * added/modified folders. */ $additionalFolders = array( // demo entry for the synchronization of contacts from the public folder. // uncomment (remove '/*' '*/') and fill in the folderid /* array( 'store' => "SYSTEM", 'folderid' => "", 'name' => "Public Contacts", 'type' => SYNC_FOLDER_TYPE_USER_CONTACT, 'flags' => DeviceManager::FLD_FLAGS_NONE, ), */ ); -
Looks just fine, my differences are with the KOE settings.
(KOE is the Kopano Outlook extension.)
We do not use Kopano, so we cannot use all of those features.define('KOE_CAPABILITY_GAB', true); define('KOE_CAPABILITY_RECEIVEFLAGS', true); define('KOE_CAPABILITY_SENDFLAGS', true); define('KOE_CAPABILITY_OOF', false); define('KOE_CAPABILITY_OOFTIMES', false); define('KOE_CAPABILITY_NOTES', true); define('KOE_CAPABILITY_SHAREDFOLDER', true); define('KOE_CAPABILITY_SENDAS', false); define('KOE_CAPABILITY_SECONDARYCONTACTS', true); define('KOE_CAPABILITY_SIGNATURES', false); define('KOE_CAPABILITY_RECEIPTS', true); define('KOE_CAPABILITY_IMPERSONATE', false); define('KOE_GAB_STORE', 'SYSTEM'); define('KOE_GAB_FOLDERID', ''); define('KOE_GAB_NAME', 'Z-Push-KOE-GAB');``` -
@bob4os
I really appreciate your help on this sunny Sunday morning ;-)I disabled all of them, still I cant send.
I recall from my last solution (really long time ago) that apple hat some issues when a specific folder was not available. If you have a working active sync connection with z-push, can you check two things for me?
- Do you see here in the advanced settings something for sending mails?
- Which standard folders do you have in your ios mailbox?
-
You’re welcome :-)
Same options there, folders are similar (german language for me).
I have a lot of Apple iOS device connected to my Z-Push instance and no issue with any device.
Whether recently added with iOS 14 (it all started with iOS 14) nor updated iOS devices, where the account was migrated.Could you take a look at policies.ini and compare your settings with mine?
[default] devpwenabled = 1 alphanumpwreq = 0 devencenabled = 0 docbrowseenabled = attenabled = 1 mindevpwlenngth = 4 maxinacttimedevlock = 900 maxdevpwfailedattempts = 12 maxattsize = '' allowsimpledevpw = 1 devpwexpiration = 0 devpwhistory = 0 allowstoragecard = 1 allowcam = 1 reqdevenc = 0 allowunsignedapps = 1 mindevcomplexchars = 3 allowwifi = 1 allowtextmessaging = 1 allowpopimapemail = 1 allowbluetooth = 2 allowirda = 0 reqmansyncroam = 0 maxcalagefilter = 0 allowhtmlemail = 1 maxemailagefilter = 0 maxemailbodytruncsize = -1 maxemailhtmlbodytruncsize = -1 reqsignedsmimemessages = 0 reqencsmimemessages = 0 reqsignedsmimealgorithm = 0 reqencsmimealgorithm = 0 allowsmimeencalgneg = 2 allowsmimesoftcerts = 1 allowbrowser = 1 allowconsumeremail = 1 allowinternetsharing = 1 -
sure thing:
devpwenabled = 1 (0)
allowirda = 0 (1)
maxdevpwfailedattempts = 12 (8)I have changed everything to your settings except irda (i think this should really make no difference ;)) reenabled provisioning in the z-push.conf and retried.
Directly after resetup of the mail account i see this again in the log , still the same error in the iphone:13/06/2021 21:21:25 [110456] [FATAL] [maedball] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION commandHmm if this error occurred since IOS 14, maybe i can check tomorrow with my colleagues if they know any differences from my mobility team. (they are using o365 but still maybe they have an idea).
-
Could you remove the account, delete the device states with z-push-admin.php -a remove -d <deviceid> and recreate the whole account and try again?
Just want to rule out the “devpwenabled” option. -
@bob4os well:
13/06/2021 21:55:22 [ 1405] [ERROR] [maedball] LoopDetection->ProcessLoopDetectionPreviousConnectionFailed(): Command 'Provision' at 13/06/2021 21:54:58 with pid '104908' terminated unexpectedly or is still running. 13/06/2021 21:55:22 [ 1405] [ERROR] [maedball] Please check your logs for this PID and errors like PHP-Fatals or Apache segmentation faults and report your results to the Z-Push dev team. 13/06/2021 21:55:39 [110456] [WARN] [maedball] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict 1but it wait, there is more ;-)
2021/06/13 21:54:31 [error] 246432#246432: *6050 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Call to undefined method Utils::SafeGetContents() in /usr/share/z-push/lib/utils/utils.php:995 Stack trace: #0 /usr/share/z-push/lib/default/filestatemachine.php(221): Utils::SafePutContents() #1 /usr/share/z-push/lib/core/devicemanager.php(186): FileStateMachine->LinkUserDevice() #2 /usr/share/z-push/index.php(224): DeviceManager->Save() #3 {main} thrown in /usr/share/z-push/lib/utils/utils.php on line 995" while reading response header from upstream, client: 52.98.155.85, server: myserver.net, request: "POST /Microsoft-Server-ActiveSync?Cmd=Provision&User=maedball&DeviceId=83e1baa94125441c98006a91f60c6396&DeviceType=Outlook HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "myserver.net" 2021/06/13 21:54:59 [error] 246432#246432: *7012 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Call to undefined method Utils::SafeGetContents() in /usr/share/z-push/lib/utils/utils.php:995 Stack trace: #0 /usr/share/z-push/lib/default/filestatemachine.php(221): Utils::SafePutContents() #1 /usr/share/z-push/lib/core/devicemanager.php(186): FileStateMachine->LinkUserDevice() #2 /usr/share/z-push/index.php(224): DeviceManager->Save() #3 {main} thrown in /usr/share/z-push/lib/utils/utils.php on line 995" while reading response header from upstream, client: XXX.XXX.XXX.XXX, server: myserver.net, request: "POST /Microsoft-Server-ActiveSync?User=maedball&DeviceId=7USFM7UGBD1TB3TOKLQ5C8K3E8&DeviceType=iPhone&Cmd=Provision HTTP/2.0", upstream: "fastcgi://127.0.0.1:7777", host: "myserver.net" 2021/06/13 21:55:58 [error] 246432#246432: *7374 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Call to undefined method Utils::SafeGetContents() in /usr/share/z-push/lib/utils/utils.php:995 Stack trace: #0 /usr/share/z-push/lib/default/filestatemachine.php(221): Utils::SafePutContents() #1 /usr/share/z-push/lib/core/devicemanager.php(186): FileStateMachine->LinkUserDevice() #2 /usr/share/z-push/index.php(224): DeviceManager->Save() #3 {main} thrown in /usr/share/z-push/lib/utils/utils.php on line 995" while reading response header from upstream, client: XXX.XXX.XXX.XXX, server: myserver.net, request: "POST /Microsoft-Server-ActiveSync?Cmd=FolderSync&User=maedball&DeviceId=71F78D5910B041C4902532958DE4FE5A&DeviceType=WindowsOutlook15 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "myserver.net" -
Yeah, somebody changed the function SafeGetContents to SafeGetContentsUnserialized and did not bother to check for dependencies!
There are some leftover calls to the old function - sorry about this, this usually does not happen here. -
@bob4os
No need to excuse yourselves ;-)
I am happy so find such a fine software out there for free and even have people helping on a SUNDAY at 10PM… -
Copy the GetSafeContents function from GitHub https://github.com/Z-Hub/Z-Push/blob/5fc6ca6e680b36f6d80ad052fc7c2ed89cc77a36/src/lib/utils/utils.php line 1425 and following into your “lib/utils/utils.php”, this should work until it has been properly fixed.
-
@bob4os Thank you very much. The question is if it makes sense to open all the small warnings and issues I see in the Z-push log like:
13/06/2021 22:42:35 [ 1411] [WARN] [maedball] /usr/share/z-push/backend/caldav/caldav.php:841 A non-numeric value encountered (2) 13/06/2021 22:59:24 [110456] [WARN] [maedball] BackendIMAP->StatMessage('4278c508','23'): Failed to retrieve overview: 13/06/2021 23:00:49 [ 1411] [WARN] [maedball] /usr/share/z-push/include/mimeDecode.php:865 iconv(): Detected an illegal character in input string (8) 13/06/2021 23:00:45 [ 1414] [WARN] [maedball] SyncObject->Check(): object from type SyncMail: parameter 'from' contains an invalid email address 'Angelika Klein <>'. Address is removed 13/06/2021 23:01:36 [ 1404] [ERROR] [maedball] Ignored broken message (SyncMail). Reason: '2' Folderid: 'i/48a41822' message id '196' 13/06/2021 23:01:53 [108025] [ERROR] [maedball] TimezoneUtil::guessTZNameFromPHPName() no compatible timezone found for 'UTC+01:00'. Returning 'GMT Standard Time'. Please contact the Z-Push dev team. 13/06/2021 23:02:04 [ 1407] [ERROR] [maedball] BackendIMAP->delete_calendar_dav(): event not found, we will end with zombie events 1 13/06/2021 23:01:53 [108025] [ERROR] [maedball] TimezoneUtil::guessTZNameFromPHPName() no compatible timezone found for 'UTC+01:00'. Returning 'GMT Standard Time'. Please contact the Z- 13/06/2021 23:04:29 [ 1411] [WARN] [maedball] cleanupDate('Fri, 1 Aug 2014 20:14:12 UT'): strtotime() failed - message might be broken. 13/06/2021 23:04:32 [106660] [WARN] [maedball] /usr/share/z-push/lib/core/streamer.php:309 strlen() expects parameter 1 to be string, array given (2) 13/06/2021 23:04:32 [106660] [WARN] [maedball] /usr/share/z-push/include/z_RFC822.php:182 trim() expects parameter 1 to be string, array given (2) 13/06/2021 23:05:35 [104908] [ERROR] [maedball] z_RFC822 error: Validation failed for: -
Are you using PHP 8?
-
@bob4os
7.4 php-frm - > via Nginx.It is more or less a stock Ubuntu 20.04 lts with dovecot (imap) and Nextcloud (cal and card dav)
-
/usr/share/z-push/backend/caldav/caldav.php:841 - ZP-1571
/usr/share/z-push/include/mimeDecode.php:865 - ZP-1579
BackendIMAP->delete_calendar_dav(): event not found, we will end with zombie events - a mail with a cancelation of an event was found, the calendar entry has most likely never existed, so this is to be expected…These are new to me:
/usr/share/z-push/lib/core/streamer.php:309 strlen() expects parameter 1 to be string, array given (2)
/usr/share/z-push/include/z_RFC822.php:182 trim() expects parameter 1 to be string, array given (2) -
Just in case someone has the same issue.
I changed the imap settings to SSL and suddenly IOS was able to send mails.
Now i just need to find out why z-push is disconnecting once outlook is connected:
[WARN] [michael.klein] /usr/share/z-push/backend/imap/imap.php:127 imap_open(): Couldn't open stream {mailserver:993/imap/ssl} (2) [ERROR] [michael.klein] BackendIMAP->Logon(): can't connect as user 'michael.klein' on '{mailserver:993/imap/ssl}': Can not authenticate to IMAP server: [CLOSED] IMAP connection broken (authenticate) [FATAL] [michael.klein] Exception: (AuthenticationRequiredException) - Access denied. Username or password incorrect [michael.klein] IP: 10.20.0.4 failed to authenticate user 'michael.klein' [WARN] [michael.klein] Unknown:0 Unknown: Can not authenticate to IMAP server: [CLOSED] IMAP connection broken (authenticate) (errflg=2) (8) -
Hello,
does anyone have founf a solution for this behavior?
I have the same problem a described in the initial post. The connection to my IMAP Backend with all Android Client are still working. All IOS device are not be able to send mails. In this account the did not have a mail adress, and are notifing the user with "Cannot Send Mail | Check the settings for the outgoing servers in settings -> Mail -> Accounts.
I tried different task to solve the problem, in example:-
All connection to the IMAP and SMTP backend are based on ssl/tls
-
Changed the provisioning to false
-
I deleted the account setting after every change and resets the device on the Z-Push frontend
Kind regards Andreas
-
-
@andreasb I was never able to get it working with the native IOS app. Instead i switched to the outlook app on IOS… It is not ideal but at least it works
-
@maedball
I found a solution.
After a couple of days in investigation what is the root cause for the strange behavior, I tried to setup the native IOS Mail APP with my full mail address as login name and now I can send mails as expected.
Maybe the missing AD is the problem in the Active Sync with communication in with a native IMAP backend.
Can you check this in your setup?
