which requires that every mail sender can also receive mail. For testing, it would be very convenient to have a server that can send mail, but that does not receive external mail yet. For this purpose, I created a new subdomain

mailsender.tools.wmflabs.org

which has an A record for both mail servers (208.80.155.162/mailrelay-02 and 208.80.155.188/mail). The SPF record can then be adjusted to

v=spf1 a:mailsender.tools.wmflabs.org -all

v=spf1 a:mailsender.tools.wmflabs.org mx -all

Testing with http://www.kitterman.com/spf/validate.html indicates this works correctly.

Related Objects

Mentioned In: T249237: Fix Cloud VPS and Toolforge mail servers to work with the modern internet
T249114: E-mails from noreply@pypi.org to tools.pywikibot@tools.wmflabs.org are not forwarded to certain recipients due to SPF
Mentioned Here: T96299: Move tools-mail to trusty
T97574: Provision and test tools-mailrelay-02

Event Timeline

valhallasw created this task.Jul 3 2015, 9:29 PM

valhallasw raised the priority of this task from to Needs Triage.

valhallasw updated the task description. (Show Details)

valhallasw added a project: Toolforge.

valhallasw subscribed.

Restricted Application added a project: Cloud-Services. · View Herald TranscriptJul 3 2015, 9:29 PM

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

valhallasw added a parent task: T97574: Provision and test tools-mailrelay-02.Jul 3 2015, 9:29 PM

valhallasw added subscribers: coren, scfc.Jul 3 2015, 9:34 PM

valhallasw moved this task from Backlog to Waiting for code review on the Toolforge board.Jul 4 2015, 5:44 PM

valhallasw triaged this task as Medium priority.Aug 2 2015, 1:12 PM

coren claimed this task.Aug 10 2015, 6:54 PM

valhallasw added a project: Labs-Team-Backlog.Oct 6 2015, 8:52 AM

This needs to be revisited once the LDAP backend has changed (since the opendj schema does not properly allow TXT records in domain entries)

What's the ETA for the LDAP backend change? I'm also confused why this is
blocking changing the current record -- that record got in there somehow?
Keep in mind this is a blocker for the backup mail server.

In T104733#1810829, @valhallasw wrote:

What's the ETA for the LDAP backend change? I'm also confused why this is
blocking changing the current record -- that record got in there somehow?
Keep in mind this is a blocker for the backup mail server.

The LDAP servers have been migrated to OpenLDAP and the dnsdomain2 schema is now supported. Let me know if anything needs to be changed on the OpenLDAP side of the new labs LDAP servers.

valhallasw added a project: Mail.Dec 22 2015, 9:32 PM

Note LDAP is now irrelevant here as we're using Designate instead.

Using Designate, projectadmins should be able to edit DNS records like this whenever they want.

• chasemp removed a parent task: T97574: Provision and test tools-mailrelay-02.Mar 20 2017, 12:34 PM

@valhallasw is there anything left to do here?

This was part of an implementation of T96299: Move tools-mail to trusty, T97574: Provision and test tools-mailrelay-02 et al., but the implementation got stalled for various reasons. I don't think I'm going to come back to it anytime soon, and a new implementation might choose a different approach -- so closing this for now.

• bd808 mentioned this in T249114: E-mails from noreply@pypi.org to tools.pywikibot@tools.wmflabs.org are not forwarded to certain recipients due to SPF.Apr 1 2020, 9:23 PM

• bd808 mentioned this in T249237: Fix Cloud VPS and Toolforge mail servers to work with the modern internet.Apr 2 2020, 4:36 PM

Set up A-based SPF for tools.wmflabs.orgClosed, DeclinedPublicActions

Description

Related Objects

Event Timeline

Set up A-based SPF for tools.wmflabs.org
Closed, DeclinedPublic
Actions