-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Adding hostNET Password Driver #5786
Conversation
New driver file to support hostNET Managed-Root Servers.
What software is hostNET using? Is this available for other hosting providers or hostNET only? I wouldn't want to merge provider-specific code. |
I guess every server using the dovecot 2 mailuser file format can use this. This is why I added the password_hostnet_mailuserfile option, but I can't guarantee that it's working for everyone. We have roundcube preinstalled for our customers since years and they are using in on >500.000 Mailboxes here, so the patch would be great for many people as they do there roundcube updates on their own on our managed-root systems. As you have other provider-specific code, I thought that is no general problem. We are happy to do some donation if this is of help, as this would help us and our customers. |
We have indeed one (domainFactory), I don't know how that happened. We'll consider this. You can make a donation anyway ;). |
I did. And many thanks for considering that. I'm sure it will help many roundcube users! |
Donation thankfully received :-) If this is generic for dovecot it should probably be named something like "dovecot_mailuser" or at least be described in the README file. |
I think the plugin name should be dovecot_passwdfile (to match with dovecot's naming, https://wiki.dovecot.org/BasicConfiguration). Also, instead of using doveadm directly you could use
|
renamed the driver, removed hostnet specific config option and changed the code to be easily adopted for vanilla dovecot 2 passwd-file environments.
I rewrote and renamed the plugin, respecting your concerns. One remark might be allowed for me: If you have even ONE provider specific module - thus supporting non opensource - you should allow this to everyone else. Otherwise, you should remove all provider specific code. An excuse like 'This module was always here...' is not fair. :) By now, I have the code that way, that it could be used in any vanilla dovecot 2 environment using the dovecot passwd-file format, files and methods given in dovecot/conf.d/auth-passwdfile.conf.ext On the other hand - and please keep at least this for us - I put in a little piece of code which is checking, if this roundcube instance is running on our own BSD derivate (hostBSD) to set some other defaults. That way it can be used nearly out of the box for our customers and tweaked for everyone else using the dovecot 2 passwd-file driver for user and passwort authentication. One remark: the Only these (existing) plugins/password/config.inc.php options are needed: $config['password_driver'] = 'dovecot_passwdfile' Please let me know if this is fine for you this way. |
ouch - my mistake. This one is new: $config['password_dovecot_passwdfile_path']: The path of your dovecot passwd-file '/path/to/filename' as set in dovecot/conf.d/auth-passwdfile.conf.ext |
Fine, thanks a lot! Now if you could squash your 3 commits into one, it'd be perfect for merging into master. |
One thing to note though: with |
Also, are you sure about escapeshellcmd() use? |
sorry guys - completely filled up with other jobs at my company atm. I will come back asap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting for the fixes to the last couple of comments.
dovecot_passwdfile already exists. |
New driver file to support hostNET Managed-Root Servers.