David Bennington

IBM does suggest 552, but most of the world will be talking to gmail/exchange rather than IBM servers I feel... [https://www.ibm.com/docs/en/zos/2.2.0?topic=messages-552-too-many-recipients](https://www.ibm.com/docs/en/zos/2.2.0?topic=messages-552-too-many-recipients)

I've fixed this in our fork, open to a PR for it? I've had to copy the stdlib parser to fix it, and some other fixes in there for malformed...

Hey, I was working on a personal feature to be able to generate an allow list of networks from an SPF record for later use rather than execute a check...

Just ran into this after updating! Ideally we would be able to not send the first `EHLO localhost` either, perfering to use at least a fully qualified hostname. It's ok...

Running 26.1.4 now, and tailing the file & running docker stats no longer logs anything, lgtm!

This happens to me as well, gets unpaused after about 5s. Enabling debug logging shows the following: log enabled with these settings: ```json { "debug":true, "log-level": "debug" } ``` ```...

Yours looks a little different to mine @UriZafrir, you have filters like: ``` GET /v1.44/images/json?filters={"reference":{"eclipse-temurin":true}} GET /v1.44/images/json?filters={"reference":{"tomcat":true}} GET /v1.44/images/json?filters={"reference":{"gradle":true}} GET /v1.44/images/json?filters={"reference":{"maven":true}} GET /v1.44/images/json?filters={"reference":{"postgres":true}} GET /v1.44/images/json?filters={"reference":{"nginx":true}} ``` So, something looking for...

I've done a little bit of process watching. With the Activity Monitor update frequency increased to 1s, I can see a process `com.docker.cli` appearing after pausing docker. The parent process?...

So, anyone else with this problem (docker desktop being unapused every 5-10s) I would suggest trying: * Unstalling the Resource Usage extension * Restarting Docker Desktop If that works for...

@UriZafrir your logs now look *exactly* like mine did! Can you try what I suggested and remove all docker desktop extensions and _restart docker completely_. I think there's a zombie...