Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 252470@bnt-lap001 Assistant-Session: ad628c8f-4be2-4979-94c9-76c7ed6f8241
1.7 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | origin | origin_ref |
|---|---|---|---|---|---|---|---|---|---|---|---|
| MAS-WP-0004 | workplan | MAS Postfix integration profile | communication | mail-address-semantics | proposed | claude | coulomb-social | 2026-10-18 | 2026-10-18 | residual | MAS-WP-0003 |
MAS Postfix integration profile
Decision-gate outcome of MAS-WP-0002 (founder, 2026-10-18). MAS-WP-0003
showed that a default Postfix silently drops every P2 (!) address, and
that the correct relay configuration is not obvious
(docs/experiment-review.md, operational findings). Turn the working
setup in deploy/railiance/entrypoint.sh into a documented, tested
integration profile.
Extract the profile
id: MAS-WP-0004-T01
status: todo
priority: high
Write a standalone Postfix profile (main.cf/master.cf fragments plus the relay regexp) for a MAS receiving domain:
- explicit
@DOMAINrelay regexp, ending the restriction list inreject; allow_untrusted_routing=yes,swap_bangpath=noandallow_percent_hack=no;- pipe to
mas-gateway; - optional authenticated relay with a send cap;
- null-sender discard. Explain each setting and say why the stock config fails.
Probe the profile
id: MAS-WP-0004-T02
status: todo
priority: high
Extend experiments/postfix-probe/ to run the profile against the full
address corpus. Include the relay negatives (x@other, x!y@other,
a@other@DOMAIN, a@DOMAIN@other) and P2 forms. Make it part of the test
suite where Docker is available.
Exim notes
id: MAS-WP-0004-T03
status: todo
priority: low
Check whether Exim has equivalent pitfalls for !/% local-parts and
record the needed settings. Build an Exim profile only if there is
demand.