On Thu, 24 Oct 2024, at 00:51, Dan wrote: > Two simple stuff: > > 1. Did you create the mx record among your dns records?
No, but I don't think there's any need, it works under rtable 0 and should have access to the same DNS resolution if it remains in rdomain 0? So if I can shorten the steps: 1. Create rtable 1 with route -T1 add default $gateway 2 Move smtpd to rtable 1 with rcctl set smtpd rtable 1 and restart the daemon 3. route -T1 exec ping google.com works or as pinging the relay: route -T1 exec ping smtps-proxy.fastmail.com 4. route -T1 exec dig smtps-proxy.fastmail.com mx works too for that natter 5. smtpd logs smtp-out: Failed to resolve MX for [relay:smtps-proxy.fastmail.com,port=443,smtps,auth=secrets:label,mx]: Host not found > 2. DigitalOcean has qualified support engineers to ask for anything > technical regarding your vps, including networking. I'll reach out to them to unblock smtp (DO now defaults to blocking smtp to prevent spam), but I am not sure that they can help on the rest, as it's working (when using proxy smtp on port 443 for now), just not when using rtable 1 so I must be doing something wrong or perhaps unwind does not provide MX records to smtpd? > - You got the passtime to install successfully OpenBSD on DigitalOcean? > Let us know about it.. Yes! I have scripted my setup (though I will only test the script when I fully re-install, so it's not tested but should work or would show the main steps anyway...), see attached. That's from a Fedora droplet. In short download bsd.rd and set-up grub to show the option to boot bsd.rd. The most tricky was figuring out which serial to use to be able to access grub/bsd.rd from the Digital Ocean recovery console. Then follow the normal installer, the recovery console is kind enough to show the IP, subnet, and gateway at the bottom to set up vio0. Thomas
digitalocean-obsd-bootstrap
Description: Binary data
