Search results

Why not (dist) upgrading to Debian 11? You still get PHP 7.4 there from Plesk. Or does your software run with the bundled PHP version that the Panel itself runs with?

A current Plesk server does use/support the exact same settings/configuration as 99.999% of all mail servers on this planet. Well, OK, quite a lot do not support the MD5 stuff anymore, but AUTH PLAIN/LOGIN works literally everywhere and so that is what should be used. (Apple Mail can/does not...

Authentication Method should be set to "Password" in Apple speak (translates to AUTH PLAIN in technical terms) for both incoming and outgoing mail server. "MD5 Challenge-Response" and "MD5 Digest" may work with most servers as well, but I recommend to not use that. The "SSL" option/toggle...

The only (negative) effect that the OCSP stapling option has and ever can have, is a warning message when reloading or restarting the nginx webserver. So yes, it may not be nice, but it will never break your system. Btw. for self-signed certificates you'll get the same warning, as these...

I've seen this error once on a server of ours as well... (but so far did not investigate it any further)

latest ionCube release for PHP 7.4 is v14.4.0

Username: TITLE Enabling mail service on domain as Reseller/Customer bugged PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian, Version 18.0.69 Update #2 Debian 12.10 PROBLEM DESCRIPTION The Mail service of a subscription/domain cannot be enabled (properly) by a...

caveats? long delivery delays for inbound messages and you'll need to closely monitor the mail flow and manage the ever increasing whitelist for your Postgrey daemon. the practical benefit of greylisting is also pretty much non-existing nowadays... IMHO you're better off implementing...

For only one vHost, you should be able to put that config snippet into the "Additional Apache directives" option on the "Apache & nginx Settings" page in Plesk. For only a specific script...well, never done that, no clue if something with <FilesMatch> or <Location> around that config snippet...

The flushpackets option should help here, i.e. you can place the following option somewhere in the Apache2 configuration. # disable output buffering for php-fpm/proxy_fcgi <IfModule proxy_fcgi_module> <Proxy fcgi://127.0.0.1:9000 enablereuse=off flushpackets=on> </Proxy> </IfModule>

Nobody and nothing does and should ever prioritize email routing based on MX over local authority! That would break all rules and regulation regarding email delivery. "split" domain scenarios can be achieved with manual re-routing rules for unknown addresses (i.e. "catchall" box) or the use of...

Current workaround (courtesy of Plesk support) seems to be to add the following to the panel.ini (just as an info to other affected people, looking for a quick-fix til hotfix is out) [dynamicList] enableTakeTour = 0

Just a warning/heads-up for you guys. After upgrading to 18.0.68, some of our customers can no longer login to the panel, as it throws an error message. (also happens when we try the "Log in as Customer") So far we have no clue, what circumstance triggers that problem, as most customers are just...

I do recommend Official imapsync migration tool ( release 2.290 ) And then use it like this (your desired options may vary): ./imapsync --host1 old.server.name --user1 xyz@domain.com --password1 'P4sSw0rd' --host2 new.server.name --user2 xyz@domain.com --password2 'P4sSw0rd' --automap...

The Performance Booster does disable open_basedir (i.e. set an empty value) as open_basedir can significantly hamper the performance of a website. That being said, even without the Performance Booster extension, Plesk nowadays seems to disable open_basedir for newly created websites per...

For Debian12 you can follow the instructions in the old post of mine: - Question - How to install PHP 5.6.40 on Plesk 18.0.58 and Debian 12.4? For Ubuntu you would need to adapt part one (adding repositiory) according to: ***** The main PPA for supported PHP versions with many PECL ext... ...

if it runs on PHP 5.4 it will also run on PHP 5.6 - trust me on this and for PHP 5.6 there are plenty of easy methods to get it running on a Plesk server (at least for Debian and Ubuntu)

The DKIM signature of this email was wrong (according to your screenshot), so what do you expect your server should be doing with this message? What I don't really get, is what DMARC has to do here, as neither googlemail.com nor gmail.com have a DMARC record published. Your own DMARC settings...

E_STRICT got deprecated with PHP 8.4 (see PHP 8.4: `E_STRICT` constant deprecated) If you still use it in your configuration, it will throw an error/warning message.

@ciB Your first email got whitelisted and so correctly not flagged as spam. (despite the score being 11.21 and thus way above the limit of 5 that is needed to mark it as spam) So you need to check WHY it got whitelisted.... I assume that either the enevelope-from/return-path or the from...