Recent content by TorbHo

@Sebahat.hadzhi the ">" is missing in your script. Correct script would be: echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;\nproxy_ssl_session_reuse off;" > /etc/nginx/conf.d/fixssl.conf && service nginx restart For systemctl use systemctl restart nginx instead to restart nginx

As already described: There is something missing in the code, the “>” is missing: echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;\nproxy_ssl_session_reuse off;" > /etc/nginx/conf.d/fixssl.conf && service nginx restart

Keep in mind that if you use the Plesk watchdog extension, nginx will be restarted soon. So first disable nginx monitoring in watchdog.

How many email addresses are set up? We are using Postfix with thousands of mail addresses with excessive use without any problem.

For Ubuntu < 22 try disabling NGINX Reverse Proxy with Tools and Settings -> Services Management -> Reverse Proxy Server (nginx) -> Disable until fix is ready.

@Sebahat.hadzhi Thank you for this information, good to hear they are working on this now. I understand these things take time, but I quietly hope for a quicker resolution, as we have several server migrations coming up soon due to aging software.

To return to the original topic: When will the DKIM migration issue finally be addressed? This problem has been known for years, and it's still affecting anyone who relies on external DNS and expects consistent DKIM functionality after migrating between Plesk servers. In the meantime, is there...

Thank you for your input. However, in our case the situation is a bit more nuanced. We’re operating a system with around 200 customers on a single server, and many of them have auto-forwarding from their business address to private GMX or Web.de mailboxes. That means we’re not sending mass...

@Bitpalast Thank you. I’ve checked this on my server using postcat -vq <queue_id> and can confirm that there is no DKIM-Signature header present in the queued messages. This confirms that Postfix indeed seems to sign the message at the time of actual SMTP delivery, not at the time of queuing...

Since yesterday, GMX and Web.de – two of the largest email providers in Germany – have started strictly enforcing DKIM verification for incoming mail. This has led to major delivery issues after the migration, as emails without valid DKIM signatures are now being rejected. This raises the...

We recently migrated many domains from one Plesk server to another using the official Plesk Migrator. After the migration, we noticed that the existing DKIM keys were not transferred. Instead, Plesk automatically generates new DKIM private keys for each domain on the destination server. This...

Thank you very much for your help. We were able to narrow down the issue further. It appears to be related to the fact that we have a spam filter server in front of the mail server in place that relays the emails to the destination server. We added the spam filter’s IP address to the local SPF...

@Sebahat.hadzhi Thank you for your response. Here is the output: Apr 8 14:31:56 servername postfix/smtpd[2745145]: B82806B21F8B: client=mx.mailserver.de[9x.9x.2x.1xx] Apr 8 14:31:56 servername psa-pc-remote[1680301]: B82806B21F8B: from=<[email protected]> to=<[email protected]>...

We are currently receiving a large number of DKIM/DMARC errors. All emails with a DMARC policy of "reject" are being rejected. There doesn’t seem to be any reasonable cause for this, so we wanted to disable DMARC until the issue can be narrowed down. However, disabling the DMARC check for...

Since I unfortunately haven't received a response yet, here's at least my script that searches for and outputs the affected entries. It could be extended to modify the entries via the Plesk CLI, but in my case, I handled it manually. for domain in $(plesk bin domain --list); do echo "Domain...