New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to connect other services to user Mailu user database #575

Closed
liquidat opened this Issue Aug 21, 2018 · 6 comments

Comments

@liquidat
Copy link

liquidat commented Aug 21, 2018

The current documentation does not show how users are managed inside Mailu. However, this information is crucial if Mailu is supposed to work together with other applications. For example, I would love to connect apps like Gitea and Nextcloud to Mailu, so that users of Mailu can login to Nextcloud as well.

@rakshith-ravi

This comment has been minimized.

Copy link

rakshith-ravi commented Aug 28, 2018

What's wrong with using mail authentication for those services?
Eg: Gitea has SMTP auth built in, and Nextcloud has a plugin for IMAP authentication

@liquidat

This comment has been minimized.

Copy link
Author

liquidat commented Aug 29, 2018

@rakshith-ravi Nothing is wrong with that - those are very valid options!
Howeverm not all tools might support those, Gitea and Nextcloud were just examples. So I do wonder how the user database in Mailu works, and if it makes sense to connect to it or sync it to other databases. I would be happy to provide a documentation PR if someone sheds some light on how the user db works.

@rakshith-ravi

This comment has been minimized.

Copy link

rakshith-ravi commented Aug 29, 2018

Simple. Look into the main.db file that gets generated. It's an sqlite file that has the hash of the password based on the hashing algorithm selected in the .env file

@benyanke

This comment has been minimized.

Copy link

benyanke commented Sep 15, 2018

I'm following this one.

Also just linking to #420, #83, and #302, which are related.

@muhlemmer

This comment has been minimized.

Copy link
Member

muhlemmer commented Oct 12, 2018

Best would be to use some kind of SMTP or IMAP plugin. The structure of the database does change from time to time, which is managed by migration scripts on the Mailu side. If you'd develop directly against the DB, you will need to keep track of these changes on your side.

The other way around might also be an option, since PR #612 is implemented it should become more easy to connect Mailu to an alternative database.

@liquidat

This comment has been minimized.

Copy link
Author

liquidat commented Oct 12, 2018

@muhlemmer Thanks for the insightful comment. You are right that it might be more troublesome to follow the changes in the database then to access one of the existing ways to do so.
Also #612 is quite interesting in this regard. Not sure right now how to properly add this to the documentation or faq...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment