Postby kanderson » Mon Feb 12, 2007 2:25 pm
I'll make an educated guess. This won't necessarily be 100% correct.
When a message is receive by Scalix, it is stored in the message store and each recipient is given something similar to a symlink to it. This means that if a message with a 10 meg attachment was sent to 5 users, it would take 10 megs of data in the message store. This is obviously very space efficient, and I would assume Zimbra does something similar.
During your migration, it pulls out a message for each user, and migrates it to the Scalix server. That migration will not be aware of other copies, so if I continue with the previous example, each user will pull a 10 meg message from Zimbra, and push it into Scalix. Since Scalix is NOT looking for a duplicate of the message, this will result in Scalix showing a message store using 50 megs of space, where Zimbra had used only 10. If the message had initially been delivered to Scalix, it also would have used only 10 megs. So the issue is a temporary one related to the migration. Over time your Scalix box will become more efficient, as those 5 users delete their old messages, and they are replaced with new ones.
Hope that helps.
Kev.