[SOGo] BTS activities for Friday, March 01 2024

2024-03-01 Thread SOGo reporter 
Title: BTS activities for Friday, March 01 2024





  
BTS Activities

  Home page: https://bugs.sogo.nu
  Project: SOGo
  For the period covering: Friday, March 01 2024

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
5934
	2024-03-01 11:07:08
	updated (open)
	GUI
	SoGo Adressbook do not show members of address group when there is 20 items
	
	  
	
5920
	2024-03-01 15:09:11
	feedback (open)
	Web Mail
	[EDIT] Update CKEditor version ~~CKEditor version check warning message~~
	
	  
	
5921
	2024-03-01 14:29:52
	assigned (open)
	ActiveSync
	Oulook 2021 (365) stoped syncing via EAS with latest SoGo
	
	  
	
5933
	2024-03-01 12:44:04
	assigned (open)
	SOPE
	Some SOPE components was not upgraded during upgrade SOGo to new release
	
	  
	
5935
	2024-03-01 14:52:54
	resolved (fixed)
	sogo-tool
	build failure in SOGoToolUpdateSecret.m

[SOGo] Forwarding to internal domains only

2024-03-01 Thread Kees van Vloten 

Hi,

I want to allow users to set forwarding to internal mail accounts, so 
mail sogo.conf contains:


    SOGoForwardEnabled = YES;
    SOGoForwardConstraints = 1;

The fact is that there are multiple internal domains and not all users 
can send mails in all domains.


Now it looks like sogo looks at the user's mail identities to determine 
what internal domains are for that user. Because what sogo deems an 
internal domain differs per user.


So if you have identities in example.com and example.org you can forward 
within both, but if you just have an identity in example.com you can 
only forward to example.com addresses. What I want is that all users can 
forward to both because both are in internal domains.


Is it possible to specify a list of internal domains in sogo.conf?
Or perhaps configure a LDAP query to fetch internal domains there?

- Kees.

Re: [SOGo] First timer questions

2024-03-01 Thread Marco Moock 
Am 27.02.2024 schrieb "Philipp Weber - IT Pahl Pflege GmbH"
(p.we...@pflege-pahl.de) :

> 1) So i have found a few articles about LDAP but primary about the
> LDAP which is included in Iredmail.
> 
> What is the way to connect it seamlessly to UCS LDAP?

LDAP is a protocol. Many server implementations exist, you can use them.
 
> 2) Can i use the actual external mail server as a relayhost and use 
> fetchmail to test Iredmail with a few users in parallel?

You can use an external smtp host for outgoing mail directly in the
sogo.conf, so no local MTA is needed, but possible.

You can use fetchmail to retrieve mail via IMAP, completely independent
of SOGo.

Re: [SOGo] How many table

2024-03-01 Thread Christian Mack 

Hello


Am 28.02.24 um 23:29 schrieb "Rouven Seifert" (rouven.seif...@ifsr.de):




Sogo has two modes for database.

The current one, with only 11 tables

The legacy one with several tables per user
Both are ok and once a mode has been chosen, you can’t switch between them.

If you’re setting up a new sogo server, we encourage to use the new mode (by 
setting OCSStoreURL, OCSAclURL and OCSCacheFolderURL).



I was reading this and wondering if this recommendation is actually documented 
somewhere?
The current installation guide (found at [0]) still seems to recommend the old 
scheme per default
and just references the 3 new options alongside others in that one big table.



Documentation can always get improved.


Another question:
We currently run our SOGo instance in legacy mode. What would happen if we 
would set the three options (OCSStoreURL, OCSAclURL and OCSCacheFolderURL) now?
The Docs mention no breaking behaviour at this point.



Your setup will break!!!

The only way in order to change the database mode is by creating a new one.

1) Stop reverse proxy and SOGo
sudo apache2ctl graceful-stop
sudo systemctl stop sogo

2) Backup all Data from the old one with:
sudo /usr/sbin/sogo-tool backup /Path/To/Backup ALL

3) Drop old database and create new one

4) Change settings in /etc/sogo/sogo.conf for the Mode you want to use.

5) Start SOGo, this will create tables
sudo systemctl start sogo

6) Restore all Data
for RESTORE_USER in $(ls /Path/To/Backup)
do
sudo /usr/sbin/sogo-tool restore -f ALL /Path/To/Backup ${RESTORE_USER}
	sudo /usr/sbin/sogo-tool restore -p -c /etc/sogo/sieve.creds 
/Path/To/Backup ${RESTORE_USER}

done

7) Start reverse proxy
sudo apache2ctl start


Hints:
* Not sure, 5) is still necessary, but it doesn't hurt either.
* We had problems with shared privileges. We fixed that by running the 
restore with -p again



Kind regards,
Christian Mack

--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung IT-Dienste Forschung, Lehre, Infrastruktur
78457 Konstanz
+49 7531 88-4416


smime.p7s
Description: Kryptografische S/MIME-Signatur