Bulk Import of Email Files - Revision history

Ltalaschus: /* Preparing Python */

2024-04-10T15:35:15Z

Preparing Python

Ltalaschus: /* Preparing Python */

2024-04-10T08:58:37Z

Preparing Python

Ltalaschus at 14:56, 21 September 2023

2023-09-21T14:56:07Z

Ltalaschus at 06:27, 25 August 2023

2023-08-25T06:27:27Z

Ltalaschus: /* Migrating local Exchange Archive Mailboxes into MailStore */

2023-04-26T16:15:03Z

Migrating local Exchange Archive Mailboxes into MailStore

Rrommelrath: /* Migrating Exchange Archive Mailboxes into MailStore */

2023-04-24T06:39:25Z

Migrating Exchange Archive Mailboxes into MailStore

Ltalaschus at 12:47, 20 April 2017

2017-04-20T12:47:44Z

Bmeyn at 08:06, 29 March 2017

2017-03-29T08:06:20Z

Ltalaschus at 16:43, 28 March 2017

2017-03-28T16:43:13Z

Ltalaschus at 08:48, 16 February 2017

2017-02-16T08:48:42Z

@@ Line 8: / Line 8: @@
 == Preparing Python ==
-The provided scripts are written in Python. Python 3.4 or newer is required as well as the [[Media:scripts.zip|Python scripting package]].
+The provided scripts are written in Python. Python 3.6 or newer is required as well as the [[Media:scripts.zip|Python scripting package]].
 The [[Python API Wrapper Tutorial|Python API-Wrapper]] has to be installed.

@@ Line 8: / Line 8: @@
 == Preparing Python ==
-The provided scripts are written in Python. Python 3.2 or newer is required as well as the [[Media:scripts.zip|Python scripting package]].
+The provided scripts are written in Python. Python 3.4 or newer is required as well as the [[Media:scripts.zip|Python scripting package]].
 The [[Python API Wrapper Tutorial|Python API-Wrapper]] has to be installed.

@@ Line 58: / Line 58: @@
 The table ''Recent Results'' in MailStore Client gives you an overview of all run archiving profiles. Failed runs can by easily identified by their start time as the file names of the log files begin with the same value.
 [[de:Massenimport von E-Mail-Dateien]]
 [[en:Bulk Import of Email Files]]

@@ Line 12: / Line 12: @@
 == Preparing the Folder Structure ==
-The scripting package contains the <code>createUserFolders.py</code> script which prepares the folders by fetching a list of existing MailStore Server users and creating folders with the same names in the filesystem. The actual bulk archiving script uses these folder names to assign the enclosed files to the corresponding users in MailStore.
+The scripting package contains the <code>create_user_folders_server/spe.py</code> script which prepares the folders by fetching a list of existing MailStore Server users and creating folders with the same names in the filesystem. The actual bulk archiving script uses these folder names to assign the enclosed files to the corresponding users in MailStore.
 The MailStore Server Administration API must be enabled in the [[MailStore Server Service Configuration]].
@@ Line 37: / Line 37: @@
 == Archiving ==
-Archiving is done by the <code>bulkImport.py</code> script. Before running it must be adapted to your MailStore installation by using ''IDLE''. Since this script uses the MailStore Client to connect to the server, rather than connecting to the  MailStore Server Administration API you have to use slightly other values.
+Archiving is done by the <code>bulk_import.py</code> script. Before running it must be adapted to your MailStore installation by using ''IDLE''. Since this script uses the MailStore Client to connect to the server, rather than connecting to the  MailStore Server Administration API you have to use slightly other values.
 The path to <code>MailStoreCmdSilent.exe</code>, the host name, credentials of an administrator and the <code>rootpath</code> have to be adjusted.
@@ Line 43: / Line 43: @@
 When importing into MailStore Server the <code>HOST</code> has to be in the format <code>computer:port</code>. When importing into a MailStore SPE instance the format has to be <code><nowiki>https://computer:port/instanceid</nowiki></code>.
-Similar to the <code>createUserFolders.py</code> script, <code>rootpath</code> points to the folder that contains the actual user folders.
+Similar to the <code>create_user_folders_server/spe.py</code> script, <code>rootpath</code> points to the folder that contains the actual user folders.
 The <code>filetype</code> variable can have one of the following values according to the file type to archive: <code>pst</code>, <code>mbox</code> or <code>emlmsg</code>.

@@ Line 59: / Line 59: @@
 The table ''Recent Results'' in MailStore Client gives you an overview of all run archiving profiles. Failed runs can by easily identified by their start time as the file names of the log files begin with the same value.
-== Migrating local Exchange Archive Mailboxes into MailStore ==
+== Migrating on-premises Exchange Archive Mailboxes into MailStore ==
-MailStore is not able to access local Exchange archive mailboxes directly. To archive messages contained therein they have to be copied to a location that MailStore is able to read from. The messages could either be moved back to the original mailbox by the end user through Outlook and then be archived with MailStore using Exchange or Outlook archiving profiles. Alternatively, an Exchange administrator exports the archive mailboxes into PST files. The latter can be done in one central location and fully automated. Afterwards the PST files can be archived by using the procedure described above.
+MailStore is not able to access on-premises Exchange archive mailboxes directly. To archive messages contained therein, they have to be copied to a location that MailStore is able to read from. The messages could either be moved back to the original mailbox by the end user through Outlook and then be archived with MailStore using Exchange or Outlook archiving profiles. Alternatively, an Exchange administrator exports the archive mailboxes into PST files. The latter can be done in one central location and fully automated. Afterward, the PST files can be archived by using the procedure described above.
 To create PST files from archive mailboxes, follow these steps:

@@ Line 3: / Line 3: @@
 The following describes how to archive all PST-, MBOX-, EML- or MSG-files of all users in a few steps, using a bulk import script written in Python.
-The bulk import script expects the email files in folders that are named after  the corresponding MailStore users. Such a folder structure can easily be created by another script included in the [https://ftp.mailstore.com/pub/Scripts/Python/v9/scripts.zip Python scripting package].
+The bulk import script expects the email files in folders that are named after  the corresponding MailStore users. Such a folder structure can easily be created by another script included in the [[Media:Scripts.zip|Python scripting package]].
-If you want to archive PST- or MBOX-files of one user only, you can use the bulk import scripts from  the [https://ftp.mailstore.com/pub/Scripts/Batch/v9/scripts.zip batch scripting package]; the installation of Python is not required in that case.
+If you want to archive PST- or MBOX-files of one user only, you can use the bulk import scripts from  the [[Media:Batchscripts.zip|batch scripting package]]; the installation of Python is not required in that case.
 == Preparing Python ==
-The provided scripts are written in Python. Python 3.2 or newer is required as well as the [https://ftp.mailstore.com/pub/Scripts/Python/v9/scripts.zip Python scripting package].
+The provided scripts are written in Python. Python 3.2 or newer is required as well as the [[Media:scripts.zip|Python scripting package]].
 The [[Python API Wrapper Tutorial|Python API-Wrapper]] has to be installed.

@@ Line 3: / Line 3: @@
 The following describes how to archive all PST-, MBOX-, EML- or MSG-files of all users in a few steps, using a bulk import script written in Python.
-The bulk import script expects the email files in folders that are named after  the corresponding MailStore users. Such a folder structure can easily be created by another script included in the [ftp://ftp.mailstore.com/pub/Scripts/Python/v9/scripts.zip Python scripting package].
+The bulk import script expects the email files in folders that are named after  the corresponding MailStore users. Such a folder structure can easily be created by another script included in the [https://ftp.mailstore.com/pub/Scripts/Python/v9/scripts.zip Python scripting package].
-If you want to archive PST- or MBOX-files of one user only, you can use the buk import scripts from  the [https://ftp.mailstore.com/pub/Scripts/Batch/v9/scripts.zip batch scripting package]; the installation of Python is not required in that case.
+If you want to archive PST- or MBOX-files of one user only, you can use the bulk import scripts from  the [https://ftp.mailstore.com/pub/Scripts/Batch/v9/scripts.zip batch scripting package]; the installation of Python is not required in that case.
 == Preparing Python ==
@@ Line 12: / Line 12: @@
 == Preparing the Folder Structure ==
-The scripting package contains the <tt>createUserFolders.py</tt> script which prepares the folders by fetching a list of existing MailStore Server users and creating folders with the same names in the filesystem. The actual bulk archiving script uses these folder names to assign the enclosed files to the corresponding users in MailStore.
+The scripting package contains the <code>createUserFolders.py</code> script which prepares the folders by fetching a list of existing MailStore Server users and creating folders with the same names in the filesystem. The actual bulk archiving script uses these folder names to assign the enclosed files to the corresponding users in MailStore.
 The MailStore Server Administration API must be enabled in the [[MailStore Server Service Configuration]].
-After installing Python, the script can be modified by right-clicking on it, then selecting ''IDLE'', the supplied Python editor. Adapt the values of <tt>USER</tt>, <tt>PASS</tt>, <tt>HOST</tt> and <tt>PORT</tt> to your installation.
+After installing Python, the script can be modified by right-clicking on it, then selecting ''IDLE'', the supplied Python editor. Adapt the values of <code>USER</code>, <code>PASS</code>, <code>HOST</code> and <code>PORT</code> to your installation.
-The <tt>rootpath</tt> variable contains the path where the folders will be created.
+The <code>rootpath</code> variable contains the path where the folders will be created.
 Press F5 to run the script. A security question follows.
@@ Line 31: / Line 31: @@
 <p class="msnote">'''Important Notice:''' If you want to archive PST files, Microsoft Outlook must be installed on the machine where the archiving profile is run.</p>
-Depending on the file type to be archived, the created profiles must be named <tt>templateBulkImportEMLMSG</tt>, <tt>templateBulkImportPST</tt> or <tt>templateBulkImportMBOX</tt>.
+Depending on the file type to be archived, the created profiles must be named <code>templateBulkImportEMLMSG</code>, <code>templateBulkImportPST</code> or <code>templateBulkImportMBOX</code>.
 == Filling the Folders ==
-For each user, put the email files to be archived into the corresponding folders under the <tt>rootpath</tt>. When archiving PST files, these can be located in subfolders. A simultaneous import of different file types is not supported. If you want to archive PST and MBOX files, a separate run is necessary for each.
+For each user, put the email files to be archived into the corresponding folders under the <code>rootpath</code>. When archiving PST files, these can be located in subfolders. A simultaneous import of different file types is not supported. If you want to archive PST and MBOX files, a separate run is necessary for each.
 == Archiving ==
-Archiving is done by the <tt>bulkImport.py</tt> script. Before running it must be adapted to your MailStore installation by using ''IDLE''. Since this script uses the MailStore Client to connect to the server, rather than connecting to the  MailStore Server Administration API you have to use slightly other values.
+Archiving is done by the <code>bulkImport.py</code> script. Before running it must be adapted to your MailStore installation by using ''IDLE''. Since this script uses the MailStore Client to connect to the server, rather than connecting to the  MailStore Server Administration API you have to use slightly other values.
-The path to <tt>MailStoreCmdSilent.exe</tt>, the hostname, credentials of an administrator and the <tt>rootpath</tt> have to be adjusted
+The path to <code>MailStoreCmdSilent.exe</code>, the host name, credentials of an administrator and the <code>rootpath</code> have to be adjusted.
-When importing into MailStore Server the <tt>HOST</tt> has to be in the format <tt>computer:port</tt>. When importing into a MailStore SPE instance the format has to be <tt><nowiki>https://computer:port/instanceid</nowiki></tt>.
+When importing into MailStore Server the <code>HOST</code> has to be in the format <code>computer:port</code>. When importing into a MailStore SPE instance the format has to be <code><nowiki>https://computer:port/instanceid</nowiki></code>.
-Similar to the <tt>createUserFolders.py</tt> script, <tt>rootpath</tt> points to the folder that contains the actual user folders.
+Similar to the <code>createUserFolders.py</code> script, <code>rootpath</code> points to the folder that contains the actual user folders.
-The <tt>filetype</tt> variable can have one of the following values according to the file type to archive: <tt>pst</tt>, <tt>mbox</tt> or <tt>emlmsg</tt>.
+The <code>filetype</code> variable can have one of the following values according to the file type to archive: <code>pst</code>, <code>mbox</code> or <code>emlmsg</code>.
 In ''IDLE'', press the F5 key to run the script.
 == Logging ==
-While the archiving process runs, its progress can be monitored in the status window. The message ''exitcode: 0'' means that the file or folder has been archived successfully. A different output would show the error. The task logs of the procedures are stored in the <tt>rootpath</tt> folder and are named as follows:
+While the archiving process runs, its progress can be monitored in the status window. The message ''exitcode: 0'' means that the file or folder has been archived successfully. A different output would show the error. The task logs of the procedures are stored in the <code>rootpath</code> folder and are named as follows:
    Date-Time-User-File.log (PST,MBOX)
@@ Line 109: / Line 109: @@
 </div>
 * Once the export is finished, the PST files can be archived with the procedure described above.
 [[de:Massenimport von E-Mail-Dateien]]
 [[en:Bulk Import of Email Files]]