This seems to impact mail deliverability to @icloud.com addresses too.

Please "remind" me about this ticket as often as possible, so I will fix it. I have everything I need to actually fix this, except the willpower.

We should maybe rewrite a bit the proposed solution, since ideally it's possible to use upstream.phorge.dev but it should be at least reachable to pass some anti-spam checkers I guess. At the moment it isn't:

And my spam filter says:

Maybe relevant, from my Postfix logs:

I agree that an additional status is needed for closing when creating a task. Current statuses are not obvious. "Closed, Graduated" is good to fast decision.

I've created R10 PhorgeIt Extension for this, with a little bit of content. I'll load it to the server shortly.

I sincerely thought that "Obsolete" was the good one semantically.

Seems like it is solvable via

While Deploy Keys do not appear to be the tool, I just configured a new Personal Access Token that's tied to the PhorgeIt organization. If there are any issues, please open a new task and assign it to me, I'll take a look.

It's an infra issue, but it's our infra :(

Yeah. Maybe also test plans etc.

What is being referred to as "Public Contents"? Wiki documentation? Diviner documentation? Ponder questions/answers? Other than those I'm not sure that should apply.

Issue on my end, will try to get the Mysql credentials set up for running tests

Ah! That makes sense!

(Unless there's some PHP 8.2 bug in my arc invocation... )

Pretty sure, here's the full --trace output, you can see it's trying to talk to we.phorge.it (also, I see we.phorge.it in my ~/.arcrc)

I say this, since we are receiving Diffs from many other people without issues it seems:

Are you 100% sure that you are communicating with this upstream?

(there used to be a "feature flags" application in Phabricator,

I can no longer reproduce this, so I'm guessing it was something bad in my setup.