As part of our offboarding process, we need to back up the user's mailbox, including the folder structure, which also includes SQL. This should be part of the administration interface.
Please be so kind as to provide the following question:
Should hMailserver offer a possibility to backup and restore only single accounts?
a) Yes, absolutely
b) No, I do not need
c) I use other solutions
Thank you!
Build-In Functions to export(backup)/import(restore) single account
Re: Build-In Functions to export(backup)/import(restore) single account
Why does this require sql?
Folder structure and messages can be copied from one server to another using tolls like IMAPcopy, and even some mail clients allow this (Outlook for all of it's faults does this really well - copying entire folders and sub-folders and their contents).
Folder structure and messages can be copied from one server to another using tolls like IMAPcopy, and even some mail clients allow this (Outlook for all of it's faults does this really well - copying entire folders and sub-folders and their contents).
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation
https://www.hmailserver.com/documentation
Re: Build-In Functions to export(backup)/import(restore) single account
Simply said: Folders, Rules, Flags and Tagsmattg wrote: ↑2019-12-16 23:46Why does this require sql?
Folder structure and messages can be copied from one server to another using tolls like IMAPcopy, and even some mail clients allow this (Outlook for all of it's faults does this really well - copying entire folders and sub-folders and their contents).
Yes, some mua allow you to export the whole structure, but not all. Regardless of mua, hms does not allow to export server-side rules to the mua, because sive is not supported. However, we must be able to restore the mailbox completely, including the personal rules.
And finally, it occasionally happens that mua is no longer available because the client was reset before the backup.
And by the way, I'm not talking about moving postboxes (which cannot move rules either). I'm really talking about a real backup of only one account!
- jimimaseye
- Moderator
- Posts: 10053
- Joined: 2011-09-08 17:48
Re: Build-In Functions to export(backup)/import(restore) single account
I'm sure there might be a use to isolate one single account and restore it back to hms in it's entirety like the current internal backup does for all accounts. (Emploee leaves the business and an archive is held under data retention policy). But i would only expect this to be a hms compatible backup and not an 'export' (for migration).
It may also be problematic using existing code in that uid's used for that account at time of backup (written in the database) might be changed and replaced if the restore is sometime after the original backup. (Ie, uid 123 backed up as user A might have some been replaced with a new user Z and therefore restore would have a conflict). Or perhaps maybe not if uid's are genuinely uids that only ever increment and never regenerate.
[Entered by mobile. Excuse my spelling.]
It may also be problematic using existing code in that uid's used for that account at time of backup (written in the database) might be changed and replaced if the restore is sometime after the original backup. (Ie, uid 123 backed up as user A might have some been replaced with a new user Z and therefore restore would have a conflict). Or perhaps maybe not if uid's are genuinely uids that only ever increment and never regenerate.
[Entered by mobile. Excuse my spelling.]
5.7 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829
Re: Build-In Functions to export(backup)/import(restore) single account
I know! That was exactly the reason, I opened this FR. A built-in function would ensure, that an export or an import will be made in a proper way.jimimaseye wrote: ↑2019-12-22 11:50...
It may also be problematic using existing code in that uid's used for that account at time of backup (written in the database) might be changed and replaced if the restore is sometime after the original backup. (Ie, uid 123 backed up as user A might have some been replaced with a new user Z and therefore restore would have a conflict). Or perhaps maybe not if uid's are genuinely uids that only ever increment and never regenerate.
[Entered by mobile. Excuse my spelling.]