migration plan: port 25 inbound confirmed open; outbound 25 not needed

Nathan confirmed in the Infomaniak portal that inbound 25 is open, which settles the half that matters most: receiving cannot be replaced by a relay, whereas sending can and will be. So the mail architecture is now: receive on the box, send through Scaleway Transactional Email. That makes an outbound-25 request unnecessary — the plan previously left both halves open, which would have cost a support ticket for nothing. Remaining ports listed as still to confirm rather than assumed.

cloudron-server-migration.md

@@ -85,7 +85,9 @@ needed to restore are inside the thing being restored.
       Cloudron, not part of the platform. For server-side diagnostics use the documented tool,
       `sudo cloudron-support --troubleshoot`. The version needs no guessing: a fresh install pulls the
       current release, which is 10.1.5 or newer, and anything ≥ 10.1.5 restores this backup.
-      **Ports still to open on the new box (checked 2026-10-30): 25, 465, 587, 993, 995, 4190.** Only
+      **Ports on the new box: 25 inbound CONFIRMED OPEN** (operator, via the Infomaniak portal, 2026-11-01 — this is the receive path, and it is the half that cannot be replaced by a relay).
+      Still to confirm: 465, 587, 993, 995, 4190. Outbound 25 is **not needed**: RFC-wise, a smarthost relay carries our sending, and Scaleway Transactional Email is being set up for exactly that. Do not spend a support ticket on outbound 25.
+      (Previous note, kept for the date: "Ports still to open on the new box (checked 2026-10-30): 25, 465, 587, 993, 995, 4190.")
 
       **Provider tier — confirmed 2026-11-01: Infomaniak VPS Cloud** (not Lite; the two differ
       in ways that matter here). What the tier provides, per Infomaniak's own product pages: