Hi Steve,

You are right - my suggestion does not involve openchange at all. Openchange 
would be certainly better option, but do you know anyone who has *working* 
openchange setup? In production?

Best Regards
Martin.

> On 10 Mar 2016, at 17:08, Steve Ankeny <[email protected]> wrote:
> 
> Martin . . .
> 
> Am I right in understanding your suggestion does not involve OpenChange?  
> Would that limit a user to Outlook 2013?  It appears to require a lot of 
> resources to implement, and even then, there appear to be limitations.
> 
> pg. 51-55, SOGo Installation and Configuration Guide
> 
> From my view, this is certainly preferable to using OpenChange
> 
> On 03/10/2016 10:44 AM, Martin Simovic wrote:
>> Hi,
>> 
>> I recommend you test your setup before the actual migration. ActiveSync can 
>> be very resource demanding, especially with large mailboxes. At the moment, 
>> every EAS connection requires a separate sogod process, which in your case 
>> means you need 32+ GB RAM - assuming your users use Outlook only (and not 
>> the phone, etc.) Add one more device per user (e.g. Android phone) and 
>> amount of required RAM duplicates.
>> 
>> Best Regards
>> Martin.
>> 
>>> On 10 Mar 2016, at 15:36, EFEKT PAWKI < 
>>> <mailto:[email protected]>[email protected] <mailto:[email protected]>> 
>>> wrote:
>>> 
>>> Hello.
>>> I have to migrate from Exchange 2003 to something else.
>>> My users will kill me if I force them to switch from MS Outlook to 
>>> something else.
>>> 
>>> How Sogo behave with account with a lot of data using Active Sync protocol?
>>> Especially owner of company - he have 5GB of OST and 45 in PST.
>>> 
>>> Calendar is full of meettings etc...
>>> Will Sogo be able to work fluently with such amount of data?
>>> There will be about 100 mailboxes.
>>> Best regards. Pawel
>>> -- 
>>> [email protected] <mailto:[email protected]>
>>> https://inverse.ca/sogo/lists <https://inverse.ca/sogo/lists>
> 
> -- 
> [email protected]
> https://inverse.ca/sogo/lists

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to