Title: BTS activities for Thursday, October 06 2022
BTS Activities
Home page: https://bugs.sogo.nu
Project: SOGo
For the period covering: Thursday, October 06 2022
idlast updatestatus (resolution)categorysummary
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|
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:
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
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 (supp...@serveria.com):
Hi,
Hello
Usually attribute cn (common name) is used for that.
Some (like us) use that field for login name instead.
You can specify in sogo.conf the fieldname (e.g. "displayName") for the
full name with:
[...]
SOGoUserSources = (
{
CNFieldName = "displayName";
[cut]
Kind regards,
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
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
Hello
That is how the standard demands it.
Why or when do you need that?
If there are no attendees, then the owner of the calendar is always the
organizer.
Kind regards,
Christian Mack
Am 26.09.22 um 09:29 schrieb Claudio Brocco - Peer Srl (c.bro...@peer.biz):
Hi,
I kindly ask if there
Hello
Am 24.09.22 um 22:54 schrieb Nick Wiltshire (n...@customdesigns.ca):
Hi everyone,
After following the guides to set this up, I must have gotten something wrong
that I can't find. SOGo seems to be not returning a header Outlook expects.
Using the MS test tool I get this error:
Testing
14 matches
Mail list logo
