First of all, Exchange is a complete solution. Dovecot is a imap/pop3
server ( a good one, sure... )
So replacing exchange means to find an integrated solution.
about the questions: public folder was removed in exchange. IMHO they
made the right choice :)
There is a different thing, need different tools and different client
app. You can create shared mailboxes ( i think it's a little demand for
that, but yes)
Sieve rules should work ( never tried actually)
I can see a need for an integration with folders only when you work with
webmail (like roundcube) . In this scenario ( a liitle bit like gmail)
is good to see the folders and attach them ( or save)
I use the kolab plugins for roundcube and there is a sort of integration
between the chwala ( files plugin) and any webdav capable file server (
I use owncloud/nextcloud). So you can share files, edit etc using
owncloud but also attach them and save them from webmail. You can find a
lot of plugins in owncloud to deal with files, even editing with
onlyoffice . IMHO, that's the way, there is no need to create a client
app to deal with all; maybe other people will not agree but...
On 5/9/20 1:07 PM, Marc Roos wrote:
My, my, did not expect this discussion. It is our own fault we are stuck
with google and microsoft monopolies. If small companies would combine
effort (resources and cash) and would not reinvent/create the wheel
constantly on our own little islands, we would have much better
products. So respect for the dovecot team.
The reason I am asking is that, the public folder solution is not as it
was in 2000. Exchange 2016+ do not support CDO etc. Nobody transitioned
between the two?
1. public folder can be implemented with a public mailbox?
2. authorize users via groups access to mailboxes/folders of the public
folder/mailbox. I think I saw ACL's with dovecot, does this compare to
'folder permissions'
3. is it possible with sieve to apply a rule on any mailbox/folder?
Thus if I 'drag' a message to a folder, the sieve rule is activated?
