Search results

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...

Ah - http addresses work with Curl, but https addresses do not. Googling is spinning up some references to needing urandom in the chrooted environment but I'm not finding much about how to add that... --add urandom doesn't work.

7 months later, I'm finally looking into this again. Combining John's advice above and How to add programs to a chrooted shell environment template in Plesk , the below code seems to have gotten me half way there. sudo mkdir /var/www/vhosts/chroot/usr/lib64 sudo cp -a /usr/lib64/mysql...

I take it the new server is running a recent enough Plesk version? Looking at our servers, /usr/lib64/plesk-9.0/maildir-migrate-dovecot (which I believe is the script that was at fault for us), was last updated April 27th so presumably if your Plesk was updated after that date, you'll have the...

Hi Dave. Our migrations have been working since my above reply on June 22nd 2020. Just a couple of days ago actually, we finished migrating the last account from our oldest server and this one had a 10gb mail inbox associated to it. No problems at all with the migration. The servers we're...

Thanks @Ehud that's exactly what I was hoping for. Is there a limit to the number of IPs you can add in one go with the comma separators? And what do those initial LIST lines do?

Thankfully science gave us coffee!

Unfortunately we don't have a development server that this is an issue on so that's not an option for me...

OK, thanks. I'm too tired to dare action this on a production server right now, but this sounds promising! I'll let you know how I get on.

Interesting... So, this should do it then? sudo cp -a /usr/lib64/*.so* /var/www/vhosts/chroot/usr/lib64/