-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Log ClientExceptions to logfile #705
Comments
Would this help? snappymail/snappymail/v/0.0.0/app/libraries/RainLoop/ActionsAdmin.php Lines 256 to 270 in 2634edd
|
sorry, i don't get it... 🙂. The idea behind my request is to give the developer / admin the possibility to see if a user (or a plugin) tries to login with a mail address that is not in the list if configured domains. |
What i mean is: Should your plugin check if Domain is available BEFORE trying to login with NewInstanceFromCredentials ? My code above does three things for that:
Step 1 is currently a private/protected function but you get the idea to:
|
Ok thanks for the explanation! I will add a check to my plugin 🙂👍 |
If you want access to resolveLoginCredentials() i can change the scope. |
I'm actually writing a plugin for SnappyMail to add additional mailboxes by a ldap query. There I had a problem with the domain check that is done in
snappymail/snappymail/v/0.0.0/app/libraries/RainLoop/Model/Account.php
Line 132 in 2634edd
If the domain found in ldap does not exist in the domain configuration of SnappyMail in theory this function would throw a
ClientException
to inform the user that the domain is not allowed / unknown.As this interaction is not possible when a plugin is trying to register a new mail address to SnappyMail the user (and developer) of the plugin can't get informed about this problem.
Describe the solution you'd like
I would like to propose a change to snappymail/v/0.0.0/app/libraries/RainLoop/Exceptions/ClientException.php so that a thrown error is also logged in the log file.
This way the admin / developer is informed what happened and why a login is not possible.
The text was updated successfully, but these errors were encountered: