Files
infra/stacks/postfix/README.md
znetsixe 8ab9061983 scaffold: hub-and-spoke layout, 4-network topology, 13 stack stubs
Initial structure for R&D infrastructure:

- stacks/ — 13 reusable, runnable stack stubs (kebab-case)
  cloud-and-edge: node-red, influxdb, grafana, keycloak, portainer,
                  nginx-proxy, mqtt, postfix
  cloud-only:     wireguard-server, gitea, jenkins, sql (postgres stub)
  edge-only:      wireguard-client

- cloud/ — single central hub composition with 4 networks
           (edge, app, data internal, mgmt) and include: stubs
- sites/ — per-plant edge folders (template README only for now)
- docs/architecture.md — hub-and-spoke + ingress + segmentation rationale

Network model: only nginx-proxy (80/443/8883) and wireguard-server
(51820/udp) publish ports on the cloud host. Edge nginx publishes
80/443 on plant-LAN interface only. MQTT cloud-side via nginx stream
proxy; MQTT edge-side internal-only; Postfix outbound-only.

OT layer (OPCUA, PLCs) is out of scope for this repo.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-21 12:37:59 +02:00

423 B

postfix

Outbound-only SMTP relay. Used by grafana alerts, node-red flows, jenkins build notifications.

  • Network: app (internal services hit smtp://postfix:25)
  • Ingress: none — no port published, no listener facing internet
  • Egress: TCP/25 outbound to internet MX servers (or a smart-host relay)
  • TODO: SPF/DKIM/DMARC for ${POSTFIX_FROM_DOMAIN}, smart-host config if WBD provides a relay