Skip to main content
Lucia Booking Engine contains an authenticated Postmark ingress contract. Source implementation does not prove that the Postmark provider is currently routed to it or that a fresh email was delivered.

​
Scope: employee-facing only

Postmark carries the employee-facing maintenance thread: the message an operator sends from the Maintenance Inbox to a Fieldwork employee, the employee’s reply, and inbound operational email into the Engine. It carries no guest-facing mail. Since 2026-09-09 the payment request rides the Resend guest-mail template with the booking magic link (LUCI-232); before that it borrowed this transport as a plain-text send. See Resend and Email Services. The Engine’s dev guest-mail sink never touches Postmark mail: employee-facing transports are outside the sink by design (LUCI-231).

​
Source-implemented behavior

Verified in Engine dev source at e2166b86ac6794a1423c7b2ce1b293a3dba505c4 on 2026-09-10:
  • The Engine accepts Postmark-originated email intake and related lifecycle events through the maintenance-ingress boundary.
  • Provider authenticity and minimum evidence are validated before any event is accepted; the generic branch of the same route requires the shared X-Fieldwork-Secret service credential (LUCI-169), so nothing writes to the inbox store unauthenticated.
  • Accepted inbound content is normalized into Engine-owned maintenance truth.
Exact callback URLs, event-classification parameters, authentication material, provider identifiers, and field mappings are private implementation details. The presence of the source contract is not evidence that Postmark currently targets any deployed environment.

​
Attachment handling in source

The reviewed Engine source can turn sufficient attachment evidence into a durable, renderable media record. When the provider evidence or storage outcome is insufficient, it records an explicit non-renderable fallback instead. This supersedes the old undated statement that Postmark attachment rendering was categorically deferred. It does not establish that a current provider delivery contains usable attachment evidence or reaches durable storage.

​
Provider and delivery boundary

Not reverified on 2026-09-10:
  • Postmark server/domain configuration;
  • the provider’s current webhook destination and environment;
  • server-side authentication configuration;
  • a fresh inbound, delivery, or bounce callback;
  • attachment payload shape from the live provider; and
  • resulting Maintenance Inbox or rendered-media output.
Do not label email body, metadata, or attachments “working” without a fresh provider receipt plus Engine-side outcome for the same message.

​
Dated evidence — 2026-04-27

The 2026-04-27 release record said Postmark inbound body handling was working. That observation is preserved as dated history only. It does not establish current routing or delivery health.

​
See also