Mailparse helps PHP software inspect MIME email messages and attachments. A helpdesk, mail importer or custom application may require it even when ordinary website mail sending already works. It does not create a mailbox, configure SMTP or repair DNS authentication records.
IN THIS ARTICLE
Check access and requirements
Check the application's current dependency list and identify the runtime used by its mail-import process. A browser request, cron job and background worker may use different PHP executables. Keep a sample message that contains no confidential customer information for testing.
01 Change the setting
- In Plesk, select the correct subscription and open PHP Selector from the available sidebar or additional tools. This guide applies to Linux subscriptions where the CloudLinux integration is installed. Windows Plesk uses its own PHP configuration.
- Check the active PHP version and which websites the selector change will affect. Plesk also has a native PHP Settings page for each domain. A CloudLinux setting will not automatically override a different Plesk PHP handler. Confirm which handler serves the website first.
- Open Extensions for the active PHP version and locate mailparse.
- Enable it and save if required. Mailparse requires
mbstringto be loaded before it, so confirm that dependency is enabled in the same runtime. Ask support to correct a package or load-order problem; the selector only offers extensions installed by the server administrator. - Run the application's dependency check and import a small test message with a harmless attachment. Verify the scheduled importer separately if it runs through cron.
Confirm the expected result
Confirm that the application reports the extension available and correctly separates the message sender, subject, body and attachment. Check character encoding with a representative multilingual message if your helpdesk handles multiple languages.
What should I check if the application still reports Mailparse as missing?
If the browser reports success but cron still fails, compare the cron PHP path and loaded extensions. If an extension is unavailable for the selected version, ask support for the supported combination. Do not paste real customer messages or mailbox credentials into a public diagnostic page.