Search results

An extra Received: is normal. Are you sure that's everything that's changed? Any encoding issues, CR/LF conversions? Are you sure it doesn't replace the signature? Do the postfix logs say anything about DKIM? By the way, your plesk is ancient and it seems you don't have reverse DNS properly...

plesk does not change the way your linux distribution configures ip addresses, so you'd really need to look up your distribution's networking documentation.

What IP does google report, then? Does it belong to your vserver provider? Does your provider force smtp connections through a proxy?

Does the customer use a browser that has link prefetch enabled? (this is a big security risk when it prefetches links from 3rd party hosts)

Could you try to pick a mail from the exchange outgoing queue and compare to what it looks like after it went through postfix? Is plesk set up to use dkim for that domain?

That won't survive a reboot and therefore is just asking for trouble.

which view are you using? dynamic or active?

What do you click? "Open in web" or "Preview"?

It's just how it's designed (and it's bad that adding an email account also creates a plesk account unless you uncheck the box "Can be used to log in to Plesk")

# host -t MX deurenbergmedia.nl deurenbergmedia.nl mail is handled by 0 deurenbergmedia-nl.mail.protection.outlook.com. So yes, it is normal.

by the way, I very much dislike that "Can be used to log in to Plesk" is checked by default. Giving a user more rights should be a conscious decision, not a forgotten default.

Why, the same way it does when apache binds to the server's outside IP instead of loopback? That's what mod_remoteip is for. Like I wrote already, this is a misconfiguration of mod_remoteip. It must be told which servers set a trustworthy X-Forwarded-For:, otherwise anyone could make a request...

Must be a misconfiguration of mod_remoteip. At the end of /etc/apache2/plesk.conf.d/server.conf, there needs to be 127.0.0.1 added to the line RemoteIPInternalProxy. @Peter Debik is that enough to forward to dev or should I open a bug?

However in that case they wouldn't show up in the maillog. Something tries to send a mail but gets rightfully rejected. Thankfully they're stupid (if they used a local mail address for the From, it wouldn't get blocked as Relaying). As it gets rejected right at the start of the SMTP dialog...

Why? Everything you could alter in your SPF or DMARC configuration would only affect the ability to (elsewhere) forward mails originating from your domain, and wouldn't help at all with mails from other domains forwarded by yours.

Doesn't plesk connect to the local database via socket? Would make sense that's not compatible with TLS.

Please also read the last paragraph on that site: "The considerations in this blog post are for Linux systems that are dedicated for MySQL. For Windows systems or systems that run multiple applications along with MySQL, these observations can be inaccurate." Look into monitoring, check the...

Also, 100GB seem excessive, especially when it's 200x innodb_log_file_size

You could also just have run mysqltuner without the --host argument ...

As you can see in /etc/crontab, at 6:25 each script in /etc/cron.daily is started, which does updates, backup, and other plesk tasks. You seem to also have a task like update-slocate running at 0:00 which does some disk I/O and fills the cache. That is not a problem, it's supposed to use...