Title: BTS activities for Saturday, January 07 2023
BTS Activities
Home page: https://bugs.sogo.nu
Project: SOGo
For the period covering: Saturday, January 07 2023
idlast updatestatus (resolution)categorysummary
Am 07.01.2023 um 16:35:09 Uhr schrieb Fil:
> after upgrading from sogo 5.7.1 I cannot login anymore to the webmail
> portal even if I changed the viewURL's lines into the
> |/etc/sogo/sogo.conf file.|
Does your authentication source run properly?
What does the log say?
Hello to all,
after upgrading from sogo 5.7.1 I cannot login anymore to the webmail
portal even if I changed the viewURL's lines into the
|/etc/sogo/sogo.conf file.|
|Now my viewURL lines are: (I've shortened the DB url with the three dots)
|
|viewURL = "mysql://sogo:...@127.0.0.1:3306/vmail/
Hello,
Please try to change the folowing block:
location = / {
rewrite ^ http://$server_name/SOGo;
allow all;
}
for
location = / {
rewrite ^ http://$server_name/SOGo/;
allow all;
}
And restart your sogo, probably those wrong resources URLs are being cached
incorrectly.
Please alw
On Fri, Jan 6, 2023 at 5:04 PM Eben van Deventer wrote:
> Hi all
>
> I have found only one previous post in this regard and there was no
> resolution that I can see from the archive as this user was using iRedMail,
> which is not the case for me:
>
> When I connect to SOGo via the NginX reverse P
Hello all!
I am TJ and currently looking to move away from another groupware provider
which is used for < 5 users. It has come to a point where we must consider
another service such as SoGo due to lacking functionality on our existing
service.
Currently we use client(s):
Microsoft Outlook 2016,36
Interresting, when comparing the source to the source for the Debian Repo
version running behind Apache on one of my other servers I note this:
Not Working:
Working:
(This applies to all link href attributes)
I suspect my rewrite instruction is the issue...