Peter Bieringer
Peter Bieringer
> nope 1.1.0 and up is okay. can you please update your PR?
workflow check triggered but not successful, please investigate, details see above.
still not happy, next issue found...
finally looks good, merged into new v3.2-devel branch
this can be somehow tricky regarding SPF and DKIM/DMARC, especially related to bounce handling
Support is now implemented by https://github.com/Kozea/Radicale/pull/1292, please try master branch and file comment on PR if still a problem
Note: https://github.com/Kozea/Radicale/pull/1276 can be easily extended to autodetect other scenarios where timestamp logging occurs currently twice.
You can use https://github.com/Kozea/Radicale/pull/1276 already out-of-the-box (no further extensions for various startup scenarios required): ``` INVOCATION_ID="dummy" /usr/bin/radicale ``` will log without timestamp to `stdout`
@kousu : can you confirm that your issue can be circumvented by using feature in https://github.com/Kozea/Radicale/pull/1276
Sorry, mixed up the PRs, yes https://github.com/Kozea/Radicale/pull/1290 was meant and the related environment variable is I was misleaded by my PR, which was superseeded by `RADICALE_LOG_FORMAT`. @Unrud decided to implement...