Page MenuHomePhabricator

Outbound mail from Greenhouse is broken
Closed, ResolvedPublic


When sending email out of, it advises that "It's unlikely that this email will be delivered." The default From address is For this to work, the SPF record would have to include Greenhouse's SPF policy. The exact recommended SPF policy can apparently only be viewed by a Greenhouse admin, which I'm not, but according to a screenshot in the documentation it would be something like

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

This has been discussed in bigger requests a couple of times before (T103893, T84201) for Greenhouse specfically, plus a bunch of other times for other third-party services. The TL;DR is that we don't really like whitelisting in SPF/DKIM/DMARC for for all of the third-party services that we use, because that opens up attack vectors like email spoofing, CEO fraud to entities that we do not control nor are able to vet their security. The alternative we had proposed before was to use a separate subdomain ( It's still non-ideal, but it's better than allowing them and others like them to send emails us as <insert ED name> for instance.

Does that make sense? I'm going to leave the task open in case you disagree and we can discuss further :)

How about I change the task title so that it can stay open? Because the real problem here is that outbound email is broken, I don't care whether SPF or a subdomain is used to fix it. There's no MX record for

tstarling renamed this task from SPF for Greenhouse to Outbound mail from Greenhouse is broken.Mar 8 2018, 5:16 AM

Change 417350 had a related patch set uploaded (by Herron; owner: Herron):
[operations/dns@master] WIP: add spf/dkim/mx records

Here's a patch to get the ball rolling on a subdomain for this. It's WIP since we will need an admin on the greenhouse account to supply the correct dkim/spf/mx values.

So we need a Greenhouse admin to go to Configure > Email Settings, then enter "" for the domain and click "Register". Then click "Email your I.T. dept" and send it to

Change 417350 had a related patch set uploaded (by Herron; owner: Herron):
[operations/dns@master] WIP: add spf/dkim/mx records

Is there any reason we cannot merge this in advance of the settings change?

An email was sent to the recruitment team regarding this settings change over a week ago, and I'll send a followup email to them later today. It seems to be blocked on that, plus the patchset that I think is fine for us to merge now.

Is there any reason we cannot merge this in advance of the settings change?

The change is immature as-is, unfortunately. Before merging we will want confirmation that the SPF settings proposed via gerrit are correct, and to include the correct values for dkim and mx (after they are obtained by a greenhouse admin)

Tim emailed about this a couple of weeks ago, and I sent out another email to them regarding this. Hopefully it gets some movement soon.

RobH triaged this task as High priority.Apr 2 2018, 2:54 PM
herron changed the task status from Open to Stalled.Apr 10 2018, 5:26 PM
herron moved this task from Backlog to Up Next on the Mail board.

Hi All,

Has this subdomain been created? Either or Can it be re-iterated why the domain creation is stalled?

It looks like we need the domain setup before it's setup in greenhouse, otherwise mailflow in green house will probably not flow if we change the domain there.


Hey @bbogaert, there is an unmerged WIP patch to create the subdomain here It's stalled waiting for details/confirmation from a greenhouse admin about what MX, SPF, DMARC, etc. records need to be used.

The steps outlined in should do the trick.

If you'd like we could coordinate a time to apply the greenhouse and DNS changes together.

Hi @herron,

I have a meeting with Lisa in recruiting for 1 pm Pacific on Monday, May

  1. I'll be doing the green house changes with her then. Can we coordinate

for this time or we can reschedule?


1 pm Pacific on Monday, May 21. I'll be doing the green house changes with her then.

Sounds good! Added a reminder to my calendar.

Change 417350 merged by Herron:
[operations/dns@master] add ( spf/mx records

SPF and MX records for greenhouse have been configured using the subdomain and verified through the greenhouse web admin interface. was used because the greenhouse system automatically prepends gh-mail to the (sub)domain which prevented us from configuring

The new records are: descriptive text "v=spf1 ~all" mail is handled by 10 mail is handled by 10

Ideally we will use DKIM on this subdomain as well, however DKIM support for is not yet in place on the greenhouse system.

As I understand, greenhouse support is now being engaged to finalize the config for this subdomain. At which point DKIM details should become available and we can move forward with that portion of the config. @bbogaert please correct me if that's inaccurate.


Following up -- Will we be able to enable DKIM for

ArielGlenn added a subscriber: ArielGlenn.

At this point might it be useful to poke the greenhouse support folks again?

herron claimed this task.

Well, looks like no DKIM.