strarsis

@andryyy: The problem is that this happened about two months ago. I will have to retrieve these logs.

@andryyy: No it, hadn't happened again afterwards and I updated mailcow afterwards. OK, so this issue can be closed for now. If this issue happens again I will re-open it...

@andryyy: Have this issue again after the mailcow June update :( Forced a renewal, found this: ```` Found domains: mail.extra-domain1.com, mail.extra-domain2.com, mail.extra-domain3.com, mail.extra-domain4.com ```` The FQDN domain is not listed...

Although I use a set of domains for `ADDITIONAL_SAN` (no spaces, no quotes, just commas), `autodiscover` and `autoconfig` subdomains are still used.

I have to use `./update.sh` in order to make mailcow actually use the new `mailconf` settings. And tiny acme skips verification of some domains, although they should be verified as...

It works now - after lots of attempts with staging Let's Encrypt and rebooting and restarting. I was really afraid that the Let's Encrypt quota may run out. I really...

I really want to start signing/encrypting my email using something like PGP. Not everyone uses it, but it can help raising awareness, as the MUA may show a message about...

@mkuron: So this adds the SPF record to the subdomain (=hostname mentioned in the HELO banner)? I have added the SFP record only to the TLD. Spamassassin appears to be...

I added the `SPF` `TXT` record directly for the domain itself, but SpamAssassin is still not fully happy: `SPF_HELO_SOFTFAIL` mailcow HELO: ```` 220 mail.example.com ESMTP Postcow ```` For `mail` subdomain...

@peXed: Are you changing the CSS files with a specific editor for this test?