| Welcome to the Zimbra :: Forums! | |
Welcome, if you would like to post a comment please register.
We also encourage you to explore all things Zimbra with our team and members of the community.
|  | 
05-15-2007, 07:06 AM
| | | Import Wizard for Outlook - remove 10mb Size Limitation? Hi there,
We've setup a new Zimbra server and are in the process of testing migration to the server from Outlook.
We've come across the problem of migrating emails over 10mb in size. I've searched for hours and found many suggestions for adjusting variables, such as: Code: zmprov mcf zimbraMtaMaxMessageSize 51200000
zmprov mcf zimbraFileUploadMaxSize 51200000 (which is also adjustable in the Admin interface > Global Settings > MTA > Messages)
But the best one was in the Migration document: http://www.zimbra.com/docs/os/latest...llation_guide/ Quote:
By default, messages larger than 10 MB will not be imported. The message size includes the message and attachments. If the message is larger than 10 MB, a warning is logged to Migration Wizard log file, which can be reviewed from the Import Complete dialog when the migration is complete.
Note: You can modify the following registry key to change the default limit, "HKCU\Software\ZCSMigWiz\MaxAttachSizeMB". The registry key should be specified in megabytes (MB). A value of 0 means no limit to the size of the message with attachments.
|
However, there isn't a solution mentioned in the Outlook Migration document: http://www.zimbra.com/docs/os/latest...outlook_guide/ Quote: |
By default, messages larger than 10 MB will not be imported. The message size includes the message and attachments. If the message is larger than 10 MB, a warning is logged to Import Wizard log file.
| So please help me!
Is there a way to export emails larger than 10mb?!
Kind regards,
Chris
Last edited by fdsadmin; 05-15-2007 at 07:09 AM..
| 
05-15-2007, 07:12 AM
| | Zimbra Consultant & Moderator | |
Posts: 20,319
| | You don't actually say (unless I've just missed it) whether you tried the registry change in the Migration Document. If you have tried that did you restart your Windows machine after making the registry change? What errors are you getting, apart from the obvious one of no messages over 10mb being imported.
__________________
Regards
Bill
| 
05-16-2007, 04:57 AM
| | | Quote:
Originally Posted by phoenix You don't actually say (unless I've just missed it) whether you tried the registry change in the Migration Document. If you have tried that did you restart your Windows machine after making the registry change? What errors are you getting, apart from the obvious one of no messages over 10mb being imported. | Hi Bill,
Thanks for your reply. I'll try and clear things up a bit...
We're using Outlook (currently downloading emails using POP3) and wish to upload all the emails and calendars within our staff's PST files to the Zimbra server. Note: We do not use Exchange.
The Outlook and the Exchange migration tutorials differ slightly. The Outlook one does not refer to editing the registry. Also the registry entries for the Outlook PST migration tool are different to the Exchange migration tool (different folder name in registry). Also the registry key in the Exchange document does not exist in the Outlook document. Creating this key does not help the process.
The only errors I am receiving are here: Code: 16-05-2007 12:53:54 [4156]: (MI): **Warning** Message skipped, too large d(Mon, 27 Feb 2006 16:54:16 -0000) fid(272) size(13942049) max(10485760)
16-05-2007 12:53:56 [4156]: (MI): **Warning** Message skipped, MIME representation too large d(Tue, 25 Apr 2006 16:38:28 -0000) fid(005) size(14405434) max(10485760)
16-05-2007 12:53:57 [4156]: (MI): **Warning** Message skipped, too large d(Tue, 11 Jul 2006 16:26:02 -0000) fid(005) size(14209140) max(10485760)
16-05-2007 12:53:57 [4156]: (MI): **Warning** Message skipped, too large d(Wed, 12 Jul 2006 18:11:38 -0000) fid(005) size(13695608) max(10485760)
16-05-2007 12:53:58 [4156]: (MI): **Warning** Message skipped, MIME representation too large d(Tue, 1 Aug 2006 14:51:17 -0000) fid(005) size(12193086) max(10485760)
16-05-2007 12:53:58 [4156]: (MI): **Warning** Message skipped, too large d(Mon, 11 Sep 2006 15:07:46 -0000) fid(005) size(25696165) max(10485760)
16-05-2007 12:54:02 [4156]: (MI): **Warning** Message skipped, MIME representation too large d(Wed, 27 Sep 2006 15:14:49 -0000) fid(005) size(13088816) max(10485760)
16-05-2007 12:54:04 [4156]: (MI): **Warning** Message skipped, MIME representation too large d(Fri, 16 Mar 2007 16:39:57 -0000) fid(005) size(11584355) max(10485760)
16-05-2007 12:54:04 [4156]: (MI): **Warning** Message skipped, too large d(Mon, 19 Mar 2007 12:47:40 -0000) fid(287) size(11121632) max(10485760)
16-05-2007 12:54:06 [4156]: (MI): **Warning** Message skipped, MIME representation too large d(Tue, 27 Mar 2007 13:59:42 -0000) fid(005) size(11606034) max(10485760) Hope that this helps?
Chris | 
05-16-2007, 11:46 PM
| | Zimbra Employee | |
Posts: 33
| | Hi Chris,
The Migration Wizard for outlook uses the same DWORD registry key ("HKCU\Software\ZCSMigWiz\MaxAttachSizeMB") to filter the mails on the basis of Attachment size.
The documentation for this key in Migration wizard for Exchange holds true for Migration Wizard for outlook also.
From the logs the maximum size of your mail is 25696165, so have the registry key value set to 35 to migrate all your mails. This is because the MIME representation might increase the size of the original mail by 33%. Also accordingly set the maximum size settings on Zimbra server.
-Uday | 
05-17-2007, 08:23 AM
| | | Quote:
Originally Posted by Uday Hi Chris,
The Migration Wizard for outlook uses the same DWORD registry key ("HKCU\Software\ZCSMigWiz\MaxAttachSizeMB") to filter the mails on the basis of Attachment size.
The documentation for this key in Migration wizard for Exchange holds true for Migration Wizard for outlook also.
From the logs the maximum size of your mail is 25696165, so have the registry key value set to 35 to migrate all your mails. This is because the MIME representation might increase the size of the original mail by 33%. Also accordingly set the maximum size settings on Zimbra server.
-Uday | Hi Uday,
Great! It nearly worked perfectly! The daft thing is that the Outlook program lives under " HKCU\Software\zimbra\PSTMigration\", but still references the Exchange program's key (which doesn't exist and must be created) " HKCU\Software\ZSCMigWiz\".
The remaining errors are few (and sent items don't really matter), but it would be nice to get to the bottom of all these errors before we try and transfer all our staff's PST files.
I set the DWORD to Decimal 35000000 as you suggested. The Zimbra server still has 50mb as it's attachment size limit.
Any ideas on these? Code: 17-05-2007 14:41:50 [3200]: (MI): Executing batch request
17-05-2007 14:41:51 [3200]: (MI): Got response (1610 ms)
17-05-2007 14:41:54 [3200]: (MI): Batch Adding Message d(Tue, 27 Mar 2007 13:59:42 -0000) fid(005)
17-05-2007 14:44:01 [3200]: Zimbra Exception: message not added, No upload token returned
17-05-2007 14:44:01 [3200]: Unable to process message d(Tue, 27 Mar 2007 13:59:42 -0000) Folder Name - Sent Items
17-05-2007 14:44:05 [3200]: (MI): The MAPI message was logged to C:\DOCUME~1\Chris\LOCALS~1\Temp\ZCSImportWiz-4.5.5_GA_831\000000001c75546c554a774d8b93b35dcb0c5b94841b2400.msg:
17-05-2007 14:44:05 [3200]: (MI): Executing batch request
17-05-2007 14:44:26 [3200]: Clearing internal progress log entries
17-05-2007 14:44:26 [3200]: Entries cleared
17-05-2007 14:44:26 [3200]: RPC Error: Unable to connect.
17-05-2007 14:44:26 [3200]: Using default store
17-05-2007 14:44:26 [3200]: Logging on to zimbra server (mail.fdskb.com:80)
17-05-2007 14:44:27 [3200]: Replicating folder hierarchy
17-05-2007 14:44:27 [3200]: (FR): Entering folder: / Code: 17-05-2007 14:44:28 [3200]: Importing messages
17-05-2007 14:44:28 [3200]: Progress log is: C:\DOCUME~1\Chris\LOCALS~1\Temp\ZCSImportWiz-4.5.5_GA_831\620abaf6c2ad9d9b90530ae687956b76_Copy of FDSL.status
17-05-2007 14:44:28 [3200]: Zimbra::MAPI::MailboxScanner::Scan. calling NamedProps::Init() using the root store folder
17-05-2007 14:44:28 [3200]: Zimbra::Mapi::NamedProps::Init. NamedProps::Init() succeeded!
17-05-2007 14:44:28 [3200]: Starting mid scan
17-05-2007 14:44:30 [3200]: mid scan ended
17-05-2007 14:44:31 [3200]: (MI): Batch Adding Message d(Tue, 27 Mar 2007 13:59:42 -0000) fid(005)
17-05-2007 14:45:53 [3200]: Zimbra Exception: message not added, No upload token returned
17-05-2007 14:45:53 [3200]: Unable to process message d(Tue, 27 Mar 2007 13:59:42 -0000) Folder Name - Sent Items
17-05-2007 14:45:56 [3200]: (MI): The MAPI message was logged to C:\DOCUME~1\Chris\LOCALS~1\Temp\ZCSImportWiz-4.5.5_GA_831\000000001c75546c554a774d8b93b35dcb0c5b94841b2400.msg: | 
05-18-2007, 12:14 AM
| | Zimbra Employee | |
Posts: 33
| | Hi Chris,
HKCU\Software\ZSCMigWiz\MaxAttachSizeMB just tells the Migrator the maximum attachment size that is allowed during migration. It doesn't alter the attachment size settings at server. You will have to set the allowed attachment size at server explicitly. The server won't upload the message exceeding this limit and the migration will result in error for such messages.
Also the registry key specifies the messages size in MB so setting it to decimal value of 35000000 would make it 35000000 MB.
-Uday | 
07-01-2007, 06:55 PM
| | | Just thought people might want to know the above registry key has been moved as of the 4.5.6 release.
Quote below from the release notes. This stumped me for a while until I did a search on the forums. Also it is worth noting that the DWORD entry is straight under the Zimbra key. Quote:
17517 The registry key, MaxAttachSizeMB, which is common for migration and importing tools, has been moved to
HKEY_CURRENT_USER\Software\Zimbra.
| | 
03-14-2008, 01:59 PM
| | Trained Alumni | |
Posts: 123
| | Hi
I tried to change the registry without any luck. The only field in Zimbra registry i could find that could be the size is: MaxWriteSize. Tried changing this to both max value posseble and 0 (and rebootet windows each time) but it still fails. I will paste the errors here: (the max value have never changed). Code: 14-03-2008 21:49:10 [5656]: (MI): **Warning** Message skipped, too large d(Tue, 7 Nov 2006 13:27:32 -0000) fid(268) size(33246361) max(10485760)
14-03-2008 21:49:12 [5656]: (MI): **Warning** Message skipped, MIME representation too large d(Wed, 8 Nov 2006 08:13:21 -0000) fid(268) size(10792392) max(10485760)
14-03-2008 21:49:12 [5656]: (MI): **Warning** Message skipped, too large d(Sun, 12 Nov 2006 19:04:44 -0000) fid(268) size(24972445) max(10485760)
14-03-2008 21:49:13 [5656]: (MI): **Warning** Message skipped, MIME representation too large d(Tue, 21 Nov 2006 09:40:41 -0000) fid(264) size(10631756) max(10485760)
14-03-2008 21:49:13 [5656]: (MI): **Warning** Message skipped, too large d(Wed, 22 Nov 2006 14:17:24 -0000) fid(275) size(11882164) max(10485760)
14-03-2008 21:49:17 [5656]: (MI): **Warning** Message skipped, MIME representation too large d(Thu, 30 Nov 2006 15:03:50 -0000) fid(263) size(13823724) max(10485760)
14-03-2008 21:49:18 [5656]: (MI): **Warning** Message skipped, too large d(Tue, 13 Feb 2007 11:41:29 -0000) fid(275) size(19151268) max(10485760)
14-03-2008 21:49:21 [5656]: (MI): **Warning** Message skipped, MIME representation too large d(Mon, 12 Mar 2007 10:56:12 -0000) fid(005) size(13087397) max(10485760)
14-03-2008 21:49:21 [5656]: (MI): **Warning** Message skipped, too large d(Tue, 13 Mar 2007 09:49:03 -0000) fid(005) size(11627355) max(10485760)
14-03-2008 21:49:21 [5656]: (MI): **Warning** Message skipped, too large d(Tue, 10 Apr 2007 09:23:31 -0000) fid(005) size(12718548) max(10485760)
14-03-2008 21:49:24 [5656]: (MI): **Warning** Message skipped, MIME representation too large d(Wed, 18 Apr 2007 13:56:31 -0000) fid(284) size(11517269) max(10485760)
14-03-2008 21:49:24 [5656]: (MI): **Warning** Message skipped, too large d(Thu, 24 May 2007 08:01:39 -0000) fid(284) size(14745436) max(10485760)
14-03-2008 21:49:24 [5656]: (MI): **Warning** Message skipped, too large d(Thu, 31 May 2007 11:27:15 -0000) fid(005) size(14147155) max(10485760)
14-03-2008 21:49:26 [5656]: (MI): **Warning** Message skipped, MIME representation too large d(Thu, 31 May 2007 15:29:38 -0000) fid(284) size(11636079) max(10485760)
14-03-2008 21:49:26 [5656]: (MI): **Warning** Message skipped, too large d(Mon, 4 Jun 2007 08:15:03 -0000) fid(005) size(10522546) max(10485760)
14-03-2008 21:49:28 [5656]: (MI): **Warning** Message skipped, MIME representation too large d(Thu, 20 Sep 2007 07:33:05 -0000) fid(275) size(12527161) max(10485760)
14-03-2008 21:49:28 [5656]: (MI): **Warning** Message skipped, too large d(Thu, 20 Sep 2007 10:11:06 -0000) fid(005) size(18433661) max(10485760)
14-03-2008 21:49:30 [5656]: (MI): **Warning** Message skipped, MIME representation too large d(Mon, 24 Sep 2007 12:29:30 -0000) fid(005) size(11491747) max(10485760)
14-03-2008 21:49:32 [5656]: (MI): **Warning** Message skipped, MIME representation too large d(Mon, 29 Oct 2007 11:52:36 -0000) fid(002) size(11179081) max(10485760) | 
03-20-2008, 01:25 PM
| | | Flums - I'm not sure but from reading earlier posts I believe you need to create the key and then set the value if you want greater then 10MB messages imported. You wont find the key because it needs to be created.
HKEY_CURRENT_USER\Software\Zimbra
Create DWORD - MaxAttachSizeMB
Give it the value (in MB) you want. | 
03-20-2008, 02:37 PM
| | Trained Alumni | |
Posts: 123
| | Hi
Will have to give this a try since Zimbra Support is not answering my ticket anymore.... | | Thread Tools | Search this Thread | | | | | Display Modes | Linear Mode | | Why Join? Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.  |