• 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.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Resolved Messages with a different timestamp after importing

Denis Gomes Franco

Regular Pleskian
Hey,

Just stumbled upon another bug. After importing mails correctly (see my previous thread: Resolved - Error when importing mails to a different mailbox location) the customer complained that all mails were being displayed with the date/time of the import operation (eg. 02/01/2019 at 15:33) instead of the actual message date/time (eg. 25/07/2018 at 09:33)

Lots of research (including Plesk forums and support docs) and I just found out that this is a recurring issue with importing mails. When displaying messages to the user, the mail server uses the message file's actual date and time instead of the date and time present in the message's headers. This causes problems even with messages restored from a backup, if the restore operation does not preserve the original files' timestamps.

Of course this is not an issue with *new* messages because they'll be written to the server the moment they arrive, and thus their dates will all be correct.

So I created this thread to warn others about this situation. I fixed this after finding a shell command that GREPs all mail files, extract their dates and TOUCH the files so they have correct dates and times.

It is also possible to simply direct your customer to configure Roundcube to show actual receive dates of the e-mails. If your customer uses IMAP, the app may or may not show the correct dates, looks like there is inconsistent behavior about this.

Also, here's some feedback to the Plesk team: the Mail Import function should already do that (write files with the correct dates and times) when importing messages. It would be unbelievably easy for them to implement that.
 
@EmilioO just reacted to this very old post and now it seems interesting to post an update: I am no loger using the MAIL IMPORT function in Plesk (so I don't know if they fixed it since this thread was written up). There is a very cool plugin for Cpanel for migrating mailboxes which I later found out that it is simply a GUI for IMAPSYNC - Official imapsync migration tool ( release 1.977 ). IMAPSYNC not only moves over messages quite fast, it also syncs mailboxes, eg., you can run it multiple times until all messages are moved over in case the process stops for some reason. I've moved several gigabyte-sized mailboxes using it and it is really dependable. But it is a command-line tool.

Maybe someone can create a wrapper for IMAPSYNC for Plesk, or the Plesk team could simply abandon its current module and just implement IMAPSYNC for the MAIL IMPORT function...
 
Back
Top