Quote:
Originally Posted by SurrealSystems I can't seem to find too much info. |
-Have you gone through:
/docs/ne/latest/migration_wizard_for_groupwise_installation_guide/
username in the format cn=admin,ou=zimbra,o=z1 have any effect?
Quote:
Originally Posted by SurrealSystems I already have all the users entered into Zimbra. Now I need to move their calendar, email history, and contacts over from Groupwise.
I need to know that I can import from Groupwise into accounts on Zimbra that have already been created.. or do I have to do this from scratch? |
During the migration, the Groupwise migration wizard performs the following tasks:
• Creates the user account on the Zimbra server,
if it does not already exist
• Imports email messages, attachments, calendars, and contacts (possibly tasks/documents when we get to v5, so for now copy those to an email etc)
Quote:
Originally Posted by SurrealSystems I don't know what to put in the postoffice information file.
I also am unsure as to why it can't see the LDAP server. (a problem with groupwise?) |
see the doc (sorry I can't help you anymore than that-not a groupwise user)
Notes:
-With the 4.5 wizards Postoffice information usage is case-sensitive
-Also the 4.5 wizards rely on having a uid field:
Bug 18334 - The GroupWise Migration tool relies on the uid LDAP field which doesn't appear to always exist
-If you need gwtapp.dll see here
GroupWiseMigration - ZimbraWiki
-seriously don't forget about HKCU\Software\ZCSMigWiz\MaxAttachSizeMB which has a default of 10MB (just set it go 0)
Also, your still restricted by your zimbraFileUploadMaxSize & zimbraMtaMaxMessageSize (settable via the zcs admin console). Set zimbraMtaMaxMessageSize 10% larger than the zimbraFileUploadMaxSize.
Say both are set to 10MB (and you tell everyone they can send 10MB attachments):
An email with a 9MB attachment and 100KB message body text. The attachment may be less than the 10MB zimbraFileUploadMaxSize, and so it'll get accepted by the file upload system. But when it's converted into a MIME message it ends up base64-encoded. Then add 100K of regular body text, and the resulting message (say 10.3MB or so) is then handed off to postfix, which checks zimbraMtaMaxMessageSize and promptly rejects the message if it's over the limit of 10MB.
Of course set zimbraMtaMaxMessageSize even larger if you want to allow emails with multiple large attachments.
Also, there's a spamassassin setting to not scan/spend cpu resources on really large messages that are over x value in size - adjust accordingly.