Hi,
You're my savior as I have double checked everything as you have
suggested and indeed the encryption algo was different in dovecot
config. Dovecot had sha512-crypt while SOGO tried to use ssha512. I'm
not sure how this is possible as I have checked everything billions of
times and I was 100% sure the same algo is in both configs. I have
changed ssha512 to sha512-crypt in dovecot config and voila: I'm able to
login into SOGO. Thanks again!
P.S. By any chance you know how to prevent plain text passwords from
appearing in the logs? It kinda makes all my efforts useless and defeats
the whole encrypted storage concept...
On 2022-10-07 11:07, Odhiambo Washington wrote:
On Thu, Oct 6, 2022 at 11:50 PM Serveria Support <users@sogo.nu>
wrote:
Here it is:
MariaDB [mailserver]> describe sogo_users;
+------------+--------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+------------+--------------+------+-----+---------+-------+
| c_uid | varchar(100) | NO | | NULL | |
| c_name | varchar(100) | NO | | NULL | |
| c_password | varchar(106) | NO | | NULL | |
| c_cn | varchar(100) | NO | | NULL | |
| mail | varchar(100) | NO | | NULL | |
| domain | varchar(100) | NO | | NULL | |
+------------+--------------+------+-----+---------+-------+
6 rows in set (0.006 sec)
But I think you're going the wrong way. Windows Mail and other
software
clients can log in and send/receive emails just fine using these
credentials.
I am not going the wrong way actually. I wanted to be sure that the
right table is in place because SOGo uses specific column names.
In my setup, I created a VIEW to use with SOGo. (BTW, I'm curious
about the HOWTO that you followed for your installation).
Now that we know the right table columns exist, we can focus on
debugging.
1. I am assuming that your dovecot-sql.conf.ext also has:
default_pass_scheme = ssha512, because this is what you have specified
in sogo.conf.
2. I am assuming that in sogo.conf, you have set MySQL4DebugEnabled =
YES; (I mean you've removed the // from the line) and restarted sogod.
3. I am assuming that in dovecot's 10-logging.conf, you have set the
following params:
log_path = /var/log/dovecot-error.log
# Log file to use for informational messages. Defaults to log_path.
info_log_path = /var/log/dovecot-info.log
# Log file to use for debug messages. Defaults to info_log_path.
debug_log_path = /var/log/dovecot-debug.log
auth_verbose = yes
auth_verbose_passwords = yes
auth_debug = yes #Shows SQL queries
auth_debug_passwords = yes #Logs the passwords and the used scheme so
the problem can be debugged
....and restarted dovecot!
Now just look at the logs and you will discover why sogo is
experiencing errors.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
