• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Mailparse extension

Nicola

Basic Pleskian
Hi,
I need to install extension Mailparse, is there any particular procedure with plesk or I can install the extension via ssh without problems?
 
Hi Nicola,

nothing special here. Just keep in mind, that the PHP extension "mailparse" can be installed very easily with pecl and when you use several PHP versions on your server, you should consider to install the extension for each PHP version ( including your OS - vendor version! ).

If you don't include the "version", when you install the PHP extension "mailparse", "pecl" will always use the latest STABLE ( currently: 3.0.1 ) version ( which is ONLY compatible with PHP 7.0+ (!) ). Earlier PHP versions are only compatible with "mailparse version 2.1.6".
For the Plesk-PHP-5.4 - version for example, you would use the command: "/opt/plesk/php/5.4/bin/pecl install mailparse-2.1.6".
Consider to read as well => https://devblog.plesk.com/2015/08/adding-custom-php-modules-in-plesk/ for further instructions of the pecl - usage on servers which use Plesk.
 
Also note that mailparse should load after mbstring. Because .ini-files are loaded alphabetically, this means that you might want to name the .ini-file where you refer to mailparse.so with a different name (e.g. instead of mailparse.ini, you can try z_mailparse.ini). At least that was our experience.
 
Back
Top