• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Alternative ways to forward emails

Aslanj

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.65
We continue to run into issues when emails are forwarded (especially to Google/Yahoo addresses) using the mail forwarding settings in Plesk. There's already a lot of discussion on this with no complete resolution, it seems. We have correctly set up and can verify DKIM, SPF, DMARC authentications, so they're passing for the most part. However, when an email is forwarded in Plesk using the forwarding setting for a given email address, it appears that Plesk is either re-encoding the content or changing something, which causes the body hash to not verify, even though ARC sealing is functional.

I was wondering if anyone has successfully used an alternative way to forward emails. For instance, as an alternative method, (someone please correct me if I'm mistaken) the webmail filters (forward feature) treat the incoming message as a new message to send out, instead of ARC sealing and relaying the message directly. If that's the case, it would certainly help with authentication on Google's end. Unfortunately, we currently have Horde and the script error causes this filter to not activate. The only suggested solution I've found is not doable on our end.

Any other suggestions on making sure emails forward to Gmail/Yahoo accounts successfully would also be most welcome.

Thanks in advance!
 
I'm not sure if this will be suitable for you, but I use Cloudflare Email Routing.
I haven't looked into solutions with third-party services, to be honest, but I'm going to check out Cloudflare Email Routing, see how they process messages, cache contents, etc. Thanks!

Since my original post, we have installed Roundcube and the forwarding filter set up through webmail might help a bit. Unfortunately, that's a painful process to manage all forwarding setups, so I doubt we'll pursue that route.

We have additionally set up MTA-STS, TLS-RPT, and BIMI, got a score of 95% (A+) on PowerDMARC (and, yes, we have checked mail-tester and a bunch of other analyzers, all looking good), yet some emails continue to go into spam folders on Gmail/Yahoo. We had problems with our PTR records and we have multiple domains/IPs hosted on the same server. While we continue to look into those, I'm still quite interested in why body hash verification is failing despite ARC sealing on PLESK.
 
Back
Top