Action required: Let's Encrypt client problem - acmetool

[cpu]

@bago

I’m using Acme.sh, too, but I still have acmetool on legacy systems, so I’d like to understand how long I can “live” with acmetool and if/when I will be forced to switch to acme.sh the legacy deployments.

in its current state acmetool will be completely broken when ACME v1 is deprecated.

@bago

I’ve checked acmetool sourcecode and it sounds like it is declaring a complete user-agent:

I suspect users of acmetool were mistakenly included in this email batch. @ezekiel can you confirm this?