esackbauer Sorry for the late reply, but I just found the community notification in the spam folder (of the still old email system aka Gmail…)! The main advantage of Cloudflare caching is to save system resources. Even though the setup email server is currently exclusively dedicated to Mailcow, there’s more and more artificial traffic these days, even to servers not meant for the public.
So far, everything is working perfectly (also IMAP connection via mobile Thunderbird etc.), even with Cloudflare cache switched on (unless for the backend pages excepted from caching, as they’re not accessible by the public anyway).
[unknown] What happened was that with Cloudflare cache (and Cache Reserve) turned on, the Mailcow backend got cached and setting changes weren’t visible in the backend, so seemingly there’s no “don’t cache” header or so in the Mailcow and potentially SOGo backends that tells Cloudflare to not cache these areas (or maybe my caching settings are too strict, but they work very well in favor of fast and well-functioning websites).
If most users won’t be affected even with Cloudflare caching on - great! Just some users might be affected and thus grateful for being informed about a potential conflict with caching.
[unknown] What happened was that with Cloudflare cache (and Cache Reserve) turned on, the Mailcow backend got cached and setting changes weren’t visible in the backend, so seemingly there’s no “don’t cache” header or so in the Mailcow and potentially SOGo backends that tells Cloudflare to not cache these areas (or maybe my caching settings are too strict, but they work very well in favor of fast and well-functioning websites).
If most users won’t be affected even with Cloudflare caching on - great! Just some users might be affected and thus grateful for being informed about a potential conflict with caching.
[unknown] What happened was that with Cloudflare cache (and Cache Reserve) turned on, the Mailcow backend got cached and setting changes weren’t visible in the backend, so seemingly there’s no “don’t cache” header or so in the Mailcow and potentially SOGo backends that tells Cloudflare to not cache these areas (or maybe my caching settings are too strict, but they work very well in favor of fast and well-functioning websites).
If most users won’t be affected even with Cloudflare caching on - great! Just some users might be affected and thus grateful for being informed about a potential conflict with caching.