• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Email dates changing after Backup Restore

paolotrombini25

New Pleskian
Server operating system version
CentOS Linux 7
Plesk version and microupdate number
18.0.54
Hello everyone,

using Plesk Obsidian Version 18.0.54 on Linux, we performed a restore of a backup via the Backup & Restore page accessible from Domains > Domain Name > Backup & Restore, selecting "Sites" as the type.

However, after completing the restore, we noticed that the date of receipt in many old emails had been changed to the date of the restore. This can be seen both in the webmail and in the Apple Mail client.

To resolve this, we tried this guide: Upon restoring Plesk backup email messages show backup restoration time as the time they were received on the Apple mail client - Support Cases from Plesk Knowledge Base

However, this did not completely resolve the issue, as upon investigation, we realized that some emails are missing the "Date" header field, which the script uses to determine the original date of the email. The date field is present in:

Received: from XX by XXX (Postfix) with ESMTPS id C0A81286BD for <XXX>; Sat, 15 Feb 2020 16:48:32 +0100 (CET)

Is there a valid alternative to that script or a way to solve the problem?

Thanks in advance.
 
Back
Top