openclawd/config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Session 48: BUG-050 CRITICAL MX DNS, support ticket #370, state update

Browse source
This commit is contained in:
Hoid 2026-02-17 08:08:54 +00:00
parent 00348babe7
commit cbae35975c
3 changed files with 65 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

14
projects/business/memory/bugs.md
View file

@ -119,6 +119,20 @@ The three reported bugs (BUG-032, BUG-035, BUG-037) are verified fixed (032, 035
---
## BUG-050: Broken MX Record Causes Email Delivery Failures — CRITICAL
- **Severity:** CRITICAL
- **Issue:** MX record for docfast.dev resolves to `mail.cloonar.com.docfast.dev` (non-existent) instead of a valid mail server. This is a relative hostname in DNS that got appended to the zone.
- **Impact:** Any mail server doing sender address verification (like cloonar.com) rejects our emails. Customer #370 cannot receive verification codes. This likely affects other recipients too.
- **Root cause:** MX DNS record was entered as `mail.cloonar.com` without trailing dot, so Hetzner DNS appended `.docfast.dev`
- **Fix needed:** Investor must fix MX record in Hetzner DNS console:
- **Option A (recommended):** Set MX to `docfast.dev.` (point to own server, since Postfix runs there)
- **Option B:** Delete the broken MX record entirely (servers will fall back to A record)
- **Workaround applied:** Postfix now accepts local mail for noreply@docfast.dev (mydestination + virtual alias), but this only helps if the remote server can reach us — which it can't due to broken MX.
- **Status:** OPEN — requires investor DNS action
- **Discovered:** 2026-02-17 Session 48
---
## Test Results Summary
| Test Category | Status | Details |