Mailstore compatibility

cibex
We use Mailstore at all our Grommunio customers without any problem

rg
Christian

GOOD TO KNOW

How are you setting up Mailstore with grommunio?
Are you using a central LDAP, or without LDAP?

<--LDAP.
Not that it currently helps a lot like in an exhange environment where you usually use journalusers which the mailstore makes use of. and the synced users are synced before each archive task so the mails will end in their archives.

And it all depends of course on how you use the archive and which 'user' permissions are there.
Some people just archive w/o user-access.
Other delete/archive to keep the mailbox lean so users NEED access to the archive..

Stril
yes with ldap sync (only mailstore user group) so each user logs in with its domain credetials

the archiving is done per journal mailbox and additional each singel mailbox to delete mails older than 2 years from mailboxes

rg
Christian

externa1 the archiving is done per journal mailbox and additional each singel mailbox to delete mails older than 2 years from mailboxes

yeah, i have basically the same in most setups

mwilliams
btw, i wouldn't yet call it fully as EWS is still not working :-(

And yeah, i already sent in some debug logs of a test

Hi all, we just tried to archive several mailboxes using mailstore and the "Exchange" method. Archiving a single mailbox works, also when I try to use the "Multiple Mailboxes" method, I can login and archive the Mailbox for which I entered the credentials. Archiving any other mailbox (selected from the list of users presented) results in an error 500 on the URL ending with EWS/Exchange.asmx . The permissions for the archiving user to access other mailboxes are set (all three types). Does that mean that this part (accessing a different mailbox) is not implemented? If yes, it would be a great enhancement as it would ease archiving a lot. Or is that some other error?
Regards, Jakob

isol

Which version of mailstore are you running? Last time i checked with the recent update (which had those update notices) it didn't work. seems like version=25.1 from my check-mk-overview.

We are currently running 24.4.0.22517. I had to enter the servername manually, not sure why, but ther rest worked. Ok, no impersonation, I would then make a separate comment for a feature request.