Some users (not all which is weird) having issue with autosuggetion of senders not showing up #1807
Comments
|
Probably this helps to get more information: https://github.com/the-djmaze/snappymail/wiki/FAQ#how-do-i-enable-logging |
|
As I'm collecting more, I might add, this particular user has an account name that doesn't match the username or email address. In other words the account is like j.doe12345 while the user name is j.doe and the email address is [email protected]. Not sure if that matters to what the extension uses for lookup. |
|
I have attached a log file above. |
Why is your contacts database crashing? |
|
the j.evans account was originally set up as a local user long ago. When I setup an LDAP server and had the users use that for authentication, Nextcloud created new user accounts with an extended name since the other name already existed in the database. The login name of j.evans still works for this user and is his email address. So the uid in the LDAP server is j.evans but the user account in Nextcloud is labeled j.evans_4982.
October 15, 2024 at 3:19 PM, "Maarten" ***@***.*** ***@***.***?to=%22Maarten%22%20%3Cnotifications%40github.com%3E > wrote:
Nextcloud[DEBUG]: snappymail-nc-uid mismatch '' != 'j.evans_4982'
JSON[INFO]: Action: DoSuggestions
POST[INFO]: {"Query":"jv","Action":"Suggestions"}
SQL[ERROR]: PDOException: SQLSTATE[HY000] [1698] Access denied for user 'root'@'localhost' in /nextcloud/apps/snappymail/app/snappymail/v/2.38.1/app/libraries/RainLoop/Pdo/Base.php:83
Why is your contacts database crashing?
—
Reply to this email directly, view it on GitHub #1807 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGSHRWRHHM6LRGWWRSFWNDZ3VTCRAVCNFSM6AAAAABP5B2FHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJUHAZDENZRGI .
You are receiving this because you authored the thread.
**Matt Coulter**
**Director of Technology**
***@***.*** ***@***.*** **
**(o) 706-940-5113**
****
|
|
Ok, that explains the Nextcloud login issue. And the contacts DB error then? |
|
I'm not seeing what you mean. Is that what the SQL error is related to? I assumed that was because of the type mismatch. It is trying to use the Nextcloud account to match the user rather than the actual uid in the LDAP database. |
There isn't an issue I am aware of with the user logging into Nextcloud. The problem is that when this user starts to type an email address in the To field that is from their Inbox, it doesn't autopopulate where our other users do not have an issue. One know difference is the fact that the users Nextcloud database ID does not match their uid. The uid is correct and matches their email server account. So I do not know what prevents their ability to lookup the sender email addresses, unless somehow it is wanting to check against their Nextcloud ID instead of uid. |
|
The SQL auth is failing, that's why there are no contact suggestions. I will change the code a bit to make the log less cluttered and just bail out. |
|
Maybe help me with the flow here. The account authentication for Nextcloud and the dovecot server is LDAP, but it also it trying to make an authentication to the SQL server on the dovecot server at the same time, is this what you are saying?
October 22, 2024 at 8:41 AM, "Maarten" ***@***.*** ***@***.***?to=%22Maarten%22%20%3Cnotifications%40github.com%3E > wrote:
The SQL auth is failing, that's why there are no contact suggestions.
I will change the code a bit to make the log less cluttered and just bail out.
—
Reply to this email directly, view it on GitHub #1807 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGSHRWMM4JOOVQCV7K7UT3Z4ZBWXAVCNFSM6AAAAABP5B2FHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZGE3TOMZSGM .
You are receiving this because you authored the thread.
**Matt Coulter**
**Director of Technology**
***@***.*** ***@***.*** **
**(o) 706-940-5113**
****
|
To clarify, the issue is while using the Contacts Suggestions (IMAP Folder), correct? Shouldn't the authentication be universally working or not working? |
|
Suggestions are fetched from the contacts database. Then you can extend this using extensions like the imap-contacts-suggestions extension or Kolab. |
|
My issue is that is seems to resolve for everyone so far except this one user. Not sure why just him. The only thing I notice is that his Nextcloud username does not match his uid. I have a few other accounts like his but have not verified those yet. His uid in Nextcloud would be correct for his iRedMail and LDAP account. All LDAP and Nextcloud contacts autofill for him, just not IMAP.
…On October 27, 2024 6:53:37 AM EDT, Maarten ***@***.***> wrote:
Suggestions are fetched from the contacts database.
In the ?admin you can setup which SQL/PDO database will be used for contacts.
Then you can extend this using extensions like the imap-contacts-suggestions extension or Kolab.
--
Reply to this email directly or view it on GitHub:
#1807 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
log-2024-10-14.txt
Describe the bug
We have at least one user that when they begin to type names or addresses of users, the auto-population IMAP extension is not working. We have tried using different browsers, incognito modes, and even other systems that are working fine for other users. Seems like it only applies to this account, but there may be others. Not sure how to further troubleshoot this one.
EDIT:
As I'm collecting more, I might add, this particular user has an account name that doesn't match the username or email address. In other words the account is like j.doe12345 while the user name is j.doe and the email address is [email protected]. Not sure if that matters to what the extension uses for lookup.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Auto-populate options appearing for particular users.
Screenshots
If applicable, add screenshots to help explain your problem.
Please complete the following information:
The text was updated successfully, but these errors were encountered: