Hi Quentin, great! Thank you very much! Best regards Patrick
Am Dienstag, April 15, 2025 14:06 CEST, schrieb "qhivert" ([email protected]) <[email protected]>: The fix will be in the next nightly tomorrow -- Quentin Hivert || Alinto || R&D Lead Developer 19 Quai Perrache 69002 Lyon www.alinto.com From: [email protected] <[email protected]> On Behalf Of qhivert Sent: mardi 15 avril 2025 14:04 To: [email protected] Subject: RE: [SOGo] Notification to external address not working when setup SOGoForwardConstraints Ah yes, I remember your problem. This was not intended. I will remove the check for Notification. And if later someone request to be able to blacklist/whitelist Notifications emails, I will see as the time if we implement new parameters for that. -- Quentin Hivert || Alinto || R&D Lead Developer 19 Quai Perrache 69002 Lyon www.alinto.com From: [email protected] <[email protected]> On Behalf Of [email protected] Sent: mardi 15 avril 2025 12:42 To: [email protected] Subject: RE: [SOGo] Notification to external address not working when setup SOGoForwardConstraints Hello, unfortunately we can't use a predefined list of external domains, because the users should be able to use whatever they want as notification address. So in my eyes it has to be SOGoForwardConstraints = 1, but SOGoNotificationEnabled should not be affected by that setting. Perhaps a setting has to be created like SOGoNotificationConstraints = 1 to follow SOGoForwardConstraints and SOGoNotificationConstraints = 0 to make it possible to use whatever external/internal address the user wants to use as notification address… ? So in that case it would be an enhancement? Or, if you are looking from another perspective: why should a notification follow the setting SOGoForwardConstraints? The cause for the setting SOGoForwardConstraints is to restrict forwardings of potentially confident data to external domains, for example to fulfill regulatory. But just sending a message like “Hey Dude, you have a message in your inbox at domain.local"…I don't know any regulatory that would disallow that, but who knows… So in that case, I would say it's more likely a bug? Best regards Patrick Am Dienstag, April 15, 2025 12:03 CEST, schrieb "qhivert" ([email protected]) <[email protected]>: Hello, Are you sure the mode ‘3’ won’t work in your case ? SOGoForwardConstraints Parameter used to set constraints on possible addresses used when automatically forwarding mails. When set to 0 (default), no constraint is enforced. When set to 1, only internal domains can be used. When set to 2, only external domains defined in SOGoForwardConstraintsDomains can be used. When set to 3, internal domains and other domains defined in SOGoForwardConstraintsDomains can be used. 3 is a mixed of 1 (only internal domain) and 2 (only external domain defined SOGoForwardConstraintsDomains) -- Quentin Hivert || Alinto || R&D Lead Developer 19 Quai Perrache 69002 Lyon www.alinto.com From: [email protected] <[email protected]> On Behalf Of [email protected] Sent: mardi 15 avril 2025 10:33 To: [email protected] Subject: Re: [SOGo] Notification to external address not working when setup SOGoForwardConstraints Hi, another try to get an answer… :-( Problem: if configuring SOGoForwardConstraints = 1 it is not possible to setup a notification to an external domain. The error box shows, that it is not allowed to forward messages to external domains. (SOGo-Verswion: 5.11.2) Our setup needs to send notifications to a few users which do not login periodically to look for new mails. But to fulfill the requirements regarding GDPR, we want to disable mail forwardings to external domains. I don't know, if this is a bug or an enhancement. But it would be important for us to be able to set up notifications to external domains while disallowing mail forwarding to external domains. Any ideas or information? Thank you! Best regards Patrick Am Dienstag, Februar 25, 2025 10:07 CET, schrieb "Testpatrick" ([email protected]) <[email protected]>: Hello. We want to be quite restrictive regarding automativ forwarding of mails to external addresses. So we set up SOGoForwardConstraints = 1 and that works. But then it isn´t possible to send out a notification to an external address. If we try to set up the notification we are getting the same error dialog as if we would try to do a forward to an external address. If we don´t setup SOGoForwardConstraints, notifications to external addresses are working. Is that behaviour intended? What we want to achieve is, that users aren´t able to do automatic forwards to external addresses but, as it isn´t their "daily/primary mailbox", they should be able to send a notification if there are arriving new mails. Is that possible? Thank you! Best regards Patrick -- -- Test Patrick TransMIT GmbH IT-Solutions Kerkrader Str. 3 35394 Gießen
