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
On Thu, Oct 6, 2022 at 11:50 PM Serveria Support wrote:
> Here it is:
>
> MariaDB [mailserver]> describe sogo_users;
> ++--+--+-+-+---+
> | Field | Type | Null | Key | Default | Extra |
>
I'm not using LDAP, just regular mysql db.
On 2022-10-06 22:10, Serveria Support wrote:
Here it is:
MariaDB [mailserver]> describe sogo_users;
++--+--+-+-+---+
| Field | Type | Null | Key | Default | Extra |
Here it is:
MariaDB [mailserver]> describe sogo_users;
++--+--+-+-+---+
| Field | Type | Null | Key | Default | Extra |
++--+--+-+-+---+
| c_uid | varchar(100) | NO | | NULL|
I am expecting a table equivalent to this.
[image: sogo.jpg]
On Thu, Oct 6, 2022 at 8:50 PM Odhiambo Washington
wrote:
>
>
> On Thu, Oct 6, 2022 at 8:33 PM Serveria Support wrote:
>
>> Sure, here you go. It's very basic actually, I didn't make any heavy
>> tweaking:
>>
>
> [snip]
>
>
>
>
On Thu, Oct 6, 2022 at 8:33 PM Serveria Support wrote:
> Sure, here you go. It's very basic actually, I didn't make any heavy
> tweaking:
>
[snip]
SOGoUserSources =
(
{
type = sql;
id = users;
viewURL =
Sure, here you go. It's very basic actually, I didn't make any heavy
tweaking:
{
/* * Main SOGo configuration file
**
*
*
* Since the content of this file is a dictionary
On Thu, Oct 6, 2022 at 3:12 PM Serveria Support wrote:
> Hi,
>
> Thanks for your reply. Yes, I realized that after posting this. I made a
> mistake I meant SOGo on port 80 and 443 not Dovecot obviously.
>
> I did enable all possible logging in Dovecot and I can see Windows Mail
> clients logging
Hi,
Thanks for your reply. Yes, I realized that after posting this. I made a
mistake I meant SOGo on port 80 and 443 not Dovecot obviously.
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
On Wed, Oct 5, 2022 at 4:37 PM Serveria Support wrote:
> Thanks, you're really helpful, I appreciate.
>
> After turning Dovecot debugging on (SOGO had been enabled already) I'm
> seeing these in the log:
>
> 09:22:01 debian postfix/smtps/smtpd[267384]: SSL_accept error from
>
Thanks, you're really helpful, I appreciate.
After turning Dovecot debugging on (SOGO had been enabled already) I'm
seeing these in the log:
09:22:01 debian postfix/smtps/smtpd[267384]: SSL_accept error from
unknown[xx.xx.xx.xx]: Connection timed out
09:22:01 debian
On Mon, Oct 3, 2022 at 8:48 AM Serveria Support wrote:
> Hi,
>
> Sorry to hijack this thread, but I'm having exactly same issue. Here's
> my conf file user sources part:
>
> SOGoUserSources =
> (
>{
> type = sql;
> id = users;
> viewURL =
>
Hi,
Sorry to hijack this thread, but I'm having exactly same issue. Here's
my conf file user sources part:
SOGoUserSources =
(
{
type = sql;
id = users;
viewURL =
"mysql://mailuser:password@localhost:3306/mailserver/sogo_users";
canAuthenticate =
This looks like a LDAP authentication issue. Do you have any other
service that authenticates with LDAP? If so, try to authenticate with
the same login/password an check what happens.
Thanks,
Andrei
On 30/09/2022 12:34, "WilliamB" (will...@jmrit.co.uk) wrote:
Hi I run an Ubuntu 20.04 with
Hi,
Could have to do with encrytion used.
I got my setup working with the following (where "tablename" is actually a
view generated from the postfixadmin user table):
SOGoUserSources =
(
{ type =
sql;
Hi I run an Ubuntu 20.04 with postfix/dovecot and postfix admin
I am trying to get SOGo working but it will not authenticate
might not have worked - password policy: 65535 grace: -1 expire: -1 bound:
0
Any clues please
16 matches
Mail list logo
