Hey Jürgen, we are using mailcow as well, but it clearly says in my (perhaps some kind of outdated) backend that this app password is not part of logo so that I cannot use it. Does this not stand in your Mailcow instance?
Have a nice evening, Bastian > Am 28.10.2022 um 18:37 schrieb Juergen Bruckner > ([email protected]) <[email protected]>: > > Hello Bastian, > > well, I don't know your setup, and I also don't know to what extent you could > migrate or maybe set up from scratch (or willing to do so). > > I've been using "mailcow" [1] for a few years, and there's the option of > assigning app passwords for individual services. > Maybe this would be a solution for you. > > For me, this server suite is the ideal solution for communication etc. You > don't necessarily have to like dockerized solutions, but I've always been > fascinated and impressed by the simplicity of this product, even if it's not > always absolutely state-of-the-art/up-to-date. > > And just for the sake of completeness: I am NOT associated with mailcow in > any way ;) > > best regards > Juergen > > [1] https://mailcow.email > > > Am 28.10.22 um 17:52 schrieb "Bastian Bringenberg" > ([email protected]): >> Hey there, >> we are currently planning on using using a system like calendly to connect to >> our sogo calendar via caldav. It would be totally awesome if there would be >> some kind of key based access only for a calendar or its availability. Or >> some >> sort to not have them store our passwords in plain text and being able to >> access to our mails. >> Does someone have an idea how we could solve this? Is this a feature request >> or is a solution already available? >> Have a nice halloween weekend =), >> Bastian > > -- > /¯\ No | > \ / HTML | Juergen Bruckner > X in | [email protected] > / \ Mail |
