Page MenuHomeDevCentral

Set SPF record to new CARP IP
Open, HighPublic

Description

I've created a new mailbox to manage potential partnerships.

I've noticed mail is considered as SOFTFAIL because we changed two different ways the routing:

  • before OSPF, Hervil used a DIRECT connection for SMTP traffic
  • default router was router-001 (51.255.124.8), it's now router-002/-003 (51.68.252.230)

In roles/dns/knot/files/zones/nasqueron.org.zone we've:

nasqueron.org. 86400 IN SPF "v=spf1 +mx +ip4:51.255.124.8 +ip6:2001:41d0:303:d971:0:0:517e:c0de ?ptr ~all"

  • 51.255.124.8 is the router-001 IP
  • 51.68.252.230 is the VIP of router-002/router-003

Mail current SPF status: SOFTFAIL with IP 51.68.252.230

We should either:

  • Allow mail traffic to directly be sent by Hervil (+mx block already in SPF record)
  • Update record to also include the new VIP address

Related Objects

Event Timeline

dereckson triaged this task as Normal priority.Sat, Aug 22, 13:05
dereckson created this task.
dereckson raised the priority of this task from Normal to High.Sat, Aug 22, 13:30
dereckson updated the task description. (Show Details)

Best short-term solution, to allow mail from Docker services too, is to allow the new router IP.

We also need to document what to do when we create a new router.

In addition to this change, we also need to reuse our dedicated IP address for e-mails:

  • Hervil IP address is trusted by Outlook servers
  • CARP address belong to a blocked range

@yousra if we define a block like this at node level:

network:
  routing:
    mode: direct    

Could we then configure frr to declare 3 routes:

  • a route to GW -iface <public interface device> (public_ipv4_interface from node.resolve_network, then the device key)
  • a default gateway to regular GW (ipv4_gateway from node.resolve_network)
  • normal dynamic route to 002/003, but for 172.27.27.0/24

e.g. for Hervil

(1) route add 51.210.99.254 -iface vmx1
(2) route add default 51.210.99.254
(3) route add 172.27.27.0/24 172.27.27.<active one>