Search results

Please see this thread in the Plesk Extensions subforum: https://talk.plesk.com/threads/mail-handler-called-twice-why.339640/#post-810019

Sorry, it was a temporary error at download site. It should already be fixed now.

@Dree, check this out: [root@server ~] # cat /root/.plesk_banner # This script is indirectly called by Bash on login shell startup. # It outputs Plesk shell banner with login instructions. # If you don't need it, you may comment out the following line. /usr/lib64/plesk-9.0/ssh-banner || ...

Before switching, it is recommended to wait until all queued mail is delivered and stop the SMTP service to stop receiving emails. Other than that the process should be smooth. Please also note that by replacing sendmail (depending on the exact way you do it) you may inadvertently break some...

@Linulex, yes your script would work with Postfix as well. However I strongly advise against applying it as is since it's easy to affect security and behavior on package updates. A much better option would be to implement a custom mail handler as suggested by @UFHH01. Please also check out...

Thanks for your report, @Michael (UW Madison) ! We've reproduced and filed the issue under internal ID EXTRUBY-21. It will be fixed in one of the future updates.

@bonny3, please see this thread: https://talk.plesk.com/threads/exception-failed-to-solve-dependencies.340071/ Exception: Failed to solve dependencies: psa-mail-driver-common-17.0.17-cos6.build1700161110.19.x86_64 requires libopendkim.so.10()(64bit)

Yes, in before-local it's too late, since it is executed in the MDA (mail delivery agent) context. Handler needs to be executed in SMTP (or to lesser extent, sendmail) context for REPLY to have any effect. There's a SpamAssassin integration in Plesk. Doesn't it suit your needs?

_pre and _post scripts are for the case when user runs apt-get upgrade and apt-get dist-upgrade manually between them. The other script will automate the process completely, effectively running _pre, then dist-upgrade, then _post script. For dist-upgrading to Ubuntu 16.04 we usually recommend...

Everything looks good. Please try again or try using console interface instead (just run the plesk installer command).

This would not happen under normal circumstances. Probably some essential component is not fully installed. Please post the output of the following commands: # plesk installer list plesk 17.0.17 2>/dev/null # plesk version

Missing /opt/psa/bin/distupgrade.helper.ubt14-ubt16_post.x64.sh means plesk-core package was not upgraded during the dist-upgrade process. Check dist-upgrade logs for errors. The script should have told you the log path, if not, check /var/log/plesk/install/plesk-distupgrade.log.

@Oliver Marugg, no the bug is not fixed. For your reference, internal ID is PI-331. However, this issue happens only if corresponding locale is not configured properly in Linux. To check, run: # LC_ALL=de_DE.UTF-8 LANG=de_DE.UTF-8 bash -c echo bash: warning: setlocale: LC_ALL: cannot change...

You have some process (presumably not Apache) listening on port 7080 (and likely 7081 as well). I suppose it may be lightspeed. Find them out with netstat -tulnap | grep 708[01], then stop or kill them (if it's not httpd). It's possible that lightspeed was not properly uninstalled.

@upstar, most likely your Plesk license key does not allow other localizations. Check in Tools & Settings > License Management > Plesk License Key > Info > Available Languages.

It's really simple. Make sure your MySQL instance is available for "external" world. By default Plesk configures MySQL to listen only on loopback for security reasons. You may check which IPs your MySQL instance is bound to using the following command: netstat -tulnap | grep 3306 To...

@SeScDe, deploy container, set up static port mapping (e.g. to 32123). Then go to domain > Apache & nginx Settings and (assuming you're using nginx) do the following: Deselect "Proxy mode" and make sure no checkboxes in nginx settings block are selected. Click Apply. Then paste into "Additional...

@iceman333, I suppose you've upgraded your MySQL from system 5.5 to 5.7, but didn't adapt its configuration? Try removing the key_buffer=16M option(s) from /etc/mysql/my.cnf Please also read MySQL upgrade guide very carefully.

You may use DKIM as a reference implementation. For example: root@a10-52-38-93:~# plesk sbin mail_handlers_control --list .---.---.-------.--------------------------------------.-----------------.------------------.-----------------. | E | P | prior | address |...

@lippoliv, with a little bit of effort it's fairly easy to adapt the provided snippet in Python to any other language. What's important here is the attention to details. Here's an example how to add a Bash script as a custom mail handler to reject all mails received by a specific mail address...