Hello,

This just for this specific appointment? How often the attendee received the 
notifications? Does the user use caldav?

 

SOGo don’t send event notifications on itself, a request must have been done.

If you know your user and this happens often, you could try to add those logs

SOGoDebugRequests = YES;    -> log http request received

SMTPDebugEnabled = YES;        -> log smtp communication

And then see if smtp is triggers after a request from this user (use the pid of 
the worker at the start of the log line to find which request it comes from)

Without knowing more, I would guess this is a caldav problem: the client sends 
a caldav request to sogo that somehow thinks the event has been changed.

Regards,

-- 

Quentin Hivert || Alinto || R&D Lead Developer 

19 Quai Perrache 69002 Lyon

 <http://www.alinto.com> www.alinto.com

 

From: [email protected] <[email protected]> On Behalf Of "Alexander 
Mischke"
Sent: mercredi 25 juin 2025 10:06
To: [email protected]
Subject: [SOGo] Strange calendar notifications

 

Hello all,

 

we have faced a strange issue with SOGos calendar notifications. A user 
reported attendees for one of his periodic appointments got notification mails 
for an appointment, claiming something has changed, but the reason for the 
change is empty. Something like:

 

Folgendes wurde am Termin “Test-Termin” geändert: 

Bitte akzeptieren Sie diese Änderungen oder lehnen Sie diese ab

 

(German for “The following has been changed for appointment ‘Test-Termin’:")

("Please accept these changes or decline them")

 

(There is nothing after the colon).

 

The attendees then have the options to “Decline”, “accept temporarily” or 
“delegate”.

Does anybody have a clue how to debug WHY SOGo is thinking there has been a 
change? According to the user “nothing” has been changed (which is also implied 
by the notification mail).

Also, said user deleted this appointmnet and all occurences, and created it 
anew - issue still persists.

 

Thanks and best regards,

 

Alex
 



-- 
 

 

Reply via email to