Page MenuHomePhorge

Phorge upstream mail should not use @secure.phorge.dev addresses
Open, Needs TriagePublic

Description

We decided to use we.phorge.it as the canonical address of this upstream instance, but mail sent from it is still using noreply@secure.phorge.dev and should be changed to use we.phorge.it.
Also, inbound email may be configured with Maniphest and Differential application emails (probably notifications@we.phorge.it).

Event Timeline

I see that this sender is still as was reported.

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:

$ host upstream.phorge.dev
Host upstream.phorge.dev not found: 3(NXDOMAIN)

So I guess it's not really important to send emails from we.phorge.it or from phorge.it (and in my opinion the last could be better) but surely it seems problematic from the current setup of upstream.phorge.dev

avivey subscribed.

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.

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

So, this turns out to be a lot harder than I thought.

  • We're using postfix directly, which I'm not sure how to configure.
  • We don't have DKIM, only SPF. I've updated the SPF record for phorge.it, but it will take some time to propagate and I'm not 100% sure I did it right.
  • Also turns out we don't expose ip6 address in the dns, despite having one. I might fix it while I'm there.

I tried to configure postfix to work, and failed.
I reverted it, and email should still be working now, still using the wrong domain.

aklapper renamed this task from Phorge upstream mail should not use @upstream.phorge.dev addresses to Phorge upstream mail should not use @secure.phorge.dev addresses.Sun, Mar 30, 20:23