Search results

OK, well at least I know this is expected behaviour then. Bit of a pain but I suppose manageable.

I'm part way through migrating websites from a CentOS 7.9 server running Plesk 18.0.59 Update #2 to Alma 9 running Plesk 18.0.60, and I've just noticed that if I click through to the mail settings of a transferred website, and then the "How to configure external DNS" link, the DKIM record that...

I ended up editing /etc/yum.repos.d/almalinux-crb.repo and changing its baseurl line to the same as in the /etc/yum.repos.d/rackspace-almalinux-crb.repo variant, and Plesk is now installing. baseurl=https://mirror.rackspace.com/almalinux/$releasever/CRB/$basearch/os/

After my efforts to spin up a Rocky 9 server were swatted by Plesk not actually supporting Rocky 9, I've now spun up an Alma 9 server and worked my way back to being ready to install Plesk. This time I got the following error: So I enabled and tried again: And got the following: I then...

I'm not on the Rocky / Alma / CentOS / RHEL dev teams so can't guarantee anything, granted. But Rocky was founded by Gregory Kurtzer, one of the original CentOS founders, so I'd expect it to be as close, if not closer, to a binary compatible RHEL than Alma, given both distributions make that...

Fair point on upgrading in steps, but our servers are all cloud instances so unfortunately the CentOS to Alma upgrade script isn't an option, which is a shame as that does sound like a brilliant solution. It seems the sensible approach is going to be for me to start again with the server build...

We have 3 CentOS 7.9 servers to migrate for separate clients, and as we're already running a Rocky 8 server for another client with Plesk installed to that just fine, I perhaps ignorantly just assumed Plesk would also run on Rocky 9 without problems. Having spent 2 days building the first...

Voted. For anybody else stumbling on to this, until it's properly resolved we just adopted a DMARC policy of p=quarantine;sp=none; which seems to work well enough. It offers basically zero protection against mail spoofing but means your legitimate emails with DKIM signatures at least make it...

I didn't try that, admittedly. Worth remembering though - thanks.

Done: Issue DKIM signatures not applied when incoming mail disabled

Username: TITLE Issue DKIM signatures not applied when incoming mail disabled PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.52 Update #3 CentOS Linux 7.9.2009 PROBLEM DESCRIPTION When a domain's mail settings are set to "Disabled for incoming mail", emails...

I noticed Plesk now has 3 options for the per-domain mail service. Instead of just enabled and disabled, there's now a "Disabled for incoming mail" option which I presume means we can finally have the mail service running for generating emails through, without the server erroneously trying to...

We recently added DKIM to main domain, to combat some spam issues and get our sender reputation back up, but our server hostname is a subdomain of this domain and it looks like this is resulting in mailer daemon bounce emails being rejected because they're not sent with the appropriate DKIM...

We're having issues with our IP reputation on one of our servers causing some remote mail servers to now reject, or spam, emails sent from any domain that this server hosts and I think I've discovered the cause. Looking in the mail logs, it seems we're receiving a lot of mail sent to random...

Oh wow, that looks like a lot of hackery just to make sendmail work! PHPMailer in SMTP mode does work, and for in-house scripts that's a totally fine approach. My worry though is that if something like a Magento Cron tries to trigger an email it's entirely possible that this is going to rely on...

It does appear we have one remaining issue, actually. PHPs mail functions aren't working - even if using PHPMailer the cron tasks just throw an "/usr/sbin/sendmail: No such file or directory" error. Following the various symlinks that /usr/sbin/sendmail passes through, I thought this would...

I think I'm done and now all of the domains I'd previously had to keep as /bin/bash shells because of complex cron scripts now seem to be working under "/bin/bash (chrooted)" on CentOS 7. I've collated everything into a new Bash script in the hopes this is useful to others...

Ahhh! Turns out the lib64 copy John had suggested previously was needed since the NSS libraries are in that tree. I'd tried it when tinkering with the MySQL isses but reverted when I realised only the mysql folder was needed. Seems this does fix the Curl issues though: sudo cp -a...

Seems to be an NSS issue: sudo mkdir /var/www/vhosts/chroot/etc/ssl sudo cp -a /etc/pki /var/www/vhosts/chroot/etc/ sudo cp -a /etc/ssl/certs /var/www/vhosts/chroot/etc/ssl/ sudo chroot /var/www/vhosts/chroot curl -v https://www.google.com * About to connect() to www.google.com port 443 (#0)...

Not convinced urandom is the problem... If I chroot in and attempt to fire a curl request for a https url, I'm getting "Problem with the SSL" outputs. I've found the CA parts in /etc/ssl/certs but this directory is missing from the chroot template... Am I supposed to just copy the whole...