Hi,
Yes, you're totally right my friend! I was just desperate because I
needed help and the other thread was getting replies while mine wasn't.
Sorry about that.
Anyway, 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:09, Odhiambo Washington wrote:
@Serveria - I think it's a bad idea to address the same problem in two
separate threads. Can you please stick to the one you created instead
of the one you hijacked?
On Thu, Oct 6, 2022 at 11:50 PM Serveria Support <[email protected]>
wrote:
MySQL4DebugEnabled = YES; line is enabled in my sogo.conf
I'm not using any hashing atm, it's a test install, but if you mean
password algorithm I'm using ssha512 (used it as my Dovecot was
using it
already and I was too lazy to change it). It seems to be supported:
Possible values are: none, plain, crypt, md5, md5-crypt,
sha256-crypt
and sha512-crypt, smd5, cram-md5 and sha, sha256, sha512 and its
ssha
(e.g. ssha or ssha256) variants
Any ideas?
On 2022-10-06 16:35, Christian Mack wrote:
Hi
Enable debugging for mysql in sogo.conf:
MySQL4DebugEnabled = YES;
Also which password hashing are you using?
See "userPasswordAlgorithm" in "Installation and Konfiguration
Guide".
Kind regards,
Christian Mack
Am 06.10.22 um 10:44 schrieb Serveria Support
([email protected]):
Hi,
Thanks for responding. I did enable all possible logging in
Dovecot
and I can see Windows Mail clients logging in successfully. But
for
some reason my SOGo connection attempts are not showing up in
logs at
all. SOGo log still shows the same error message I already
posted.
SOGo website is giving me this error: Wrong username or password.
On 2022-10-04 18:54, Odhiambo Washington wrote:
On Thu, Sep 29, 2022 at 4:01 PM Serveria Support <[email protected]>
wrote:
Hi,
After weeks of trying to configure iredmail package for my
needs
(and
failing miserably) I decided to start everything from scratch:
I
took a
vanilla Debian 11 server and installed Dovecot + Postfix +
MariaDB +
Apache. Mailserver works like a charm - emails are getting
sent/delivered/stored perfectly. Users are able to log
in/authenticate.
Then I decided to add SOGo to the config and installed it, also
configured using the basic howto from sogo website. All done,
web
frontend comes up. So far so good.... unfortunately I'm unable
to
authenticate using my Dovecot users db. Here I have to add that
I
didn't
create a separate table for SOGo but instead tried to reuse my
Dovecot
user credentials by creating a VIEW in my DB. However, this
doesn't
seem
to work, here's my sogo.log:
Sep 29 06:30:17 sogod [151286]: XXXIPADDRESSXXX "POST
/SOGo/connect
HTTP/1.1" 403 34/89 0.003 - - 0 - 12
Sep 29 06:30:25 sogod [151286]: |SOGo| starting method 'POST'
on uri
'/SOGo/connect'
2022-09-29 06:30:25.510 sogod[151286:151286]
<MySQL4Channel[0x0x557d1232c5c0] connection=0x0x557d12597cd0>
SQL:
SELECT c_password FROM sogo_users WHERE c_uid =
'[email protected]';
2022-09-29 06:30:25.510 sogod[151286:151286]
<MySQL4Channel[0x0x557d1232c5c0] connection=0x0x557d12597cd0>
query
has results, entering fetch-mode.
Sep 29 06:30:25 sogod [151286]: SOGoRootPage Login from
'XXXIPADDRESSXXX' for user '[email protected]' might not have
worked
-
password policy: 65535 grace: -1 expire: -1 bound: 0
Sep 29 06:30:25 sogod [151286]: |SOGo| request took 0.001784
seconds
to
execute
Unfortunately, I'm not too good at reading SOGo logs and the
error
message seems to be not very self-explanatory. What exactly
does
this
mean? Unable to fetch password? Password didn't work? Wrong
encryption
protocol? Any suggestions?
Look at the dovecot logging configuration and bump the debugging
up
and you'll get it right.
-- Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
