B. Reino

I just noticed this today when updating to 3.4.1 (debian). I'll keep an eye on it in the next few days.

The common solution (AFAIK) to this is to use send your DMARC reports using an address with a subdomain having no DMARC reporting, e.g. in my case my DMARC reports...

I tried the above but the docker image is still amd64, even if you ```$ docker pull --platform linux/arm64/v8 ghcr.io/cogentapps/chat-with-gpt:release``` you still have ``` $ docker inspect ghcr.io/cogentapps/chat-with-gpt:release | grep...

Just wanted to say thank you for your CSS customizations above, which make everything cleaner and nicer (at least until Nextcloud provides for a proper squared theme). Would you happen...

ah, with this: ``` * { --default-clickable-area:10px; --border-radius-pill:10px; } ``` it looks really nice. Some elements are still round (like in Contacts), but I'll get there too :)

@CacheMinimal, The excluded_domains prevents DMARC reports to be sent when e-mails are received FROM one of the listed domains, i.e. you do not include "mailinblue.com" (unless you receive e-mails directly...

> Yes, this is not readily possible- but it could be easily implemented. Short of having it you might blackhole these addresses at the MTA. "_One could filter (DISCARD) e-mails...

It would probably be safer to first generate a temporary file, and then replace the existing one with the new one, in one go (using mv, which should be atomic).

I just had the same issue, and can confirm that what @bong1991 wrote worked also for me! :)

see https://github.com/overleaf/toolkit/blob/master/doc/quick-start-guide.md ```You can start them up again (without attaching to the log output) by running bin/start``` with bin/up you run overleaf in the foreground. With bin/start (or likely bin/up...