1

Topic: Migration of Database causes SOGo issues

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.7.4
- Deployed with iRedMail Easy or the downloadable installer? Download
- Linux/BSD distribution name and version:  Centos 7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I had to migrate my database and unfortunately didn't follow recommendation about the DNS though I'm not sure that would help.

I've updated the sogo.conf with the new db and after a few failings recreated the VIEW for the user login. I can now login to SOGo however some parts like shared calendars don't work. In the logs the first request always responds with a 401 and then the following same request in logs (not sure about payload as it isn't logged) results in a 207. Like:

x.x.x.x "REPORT /SOGo/dav/email@com/ HTTP/1.1" 401
x.x.x.x "REPORT /SOGo/dav/email@com/ HTTP/1.1" 207

Functions were working before the migration, I've deleted the old database unfortunately so can't see if there is a view or something missing.What would be missing in the migration to fix this issue?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Migration of Database causes SOGo issues

Please turn on debug mode in SOGo and check its log file to figure out what the problem is.