Per-event sender identity for ticket emails (organizer name, reply-to, copy to organizer) — deferred #49

New issue

Open

opened 2026-09-13 16:40:15 +00:00 by padreug · 0 comments

padreug commented

2026-09-13 16:40:15 +00:00

Owner

Deferred on 2026-09-13 to keep the production run simple; the work exists on branches and can be revived.

What was built (branches kept on origin)

feat/organizer-sender-identity (was #44): extra.organizer_name → From display name "Organizer via <site title>" (address stays the instance mailbox, DKIM untouched); extra.reply_to_email → Reply-To, falling back to the email on the LNbits account that owns the event wallet; body gains "Organizer: " and "Questions? Reply to this email…" when a reply-to exists. 41 tests.
feat/ticket-email-sent-copy (was #47): extra.copy_to_organizer → envelope-only BCC of every ticket email to that reply-to (no header, skipped when the buyer is that address). The "Email sent" column from the same branch shipped separately.
Webapp counterpart: aiolabs/webapp feat/events-organizer-sender (was #148): the three fields in the event editor.

Open design question (user's preference when deferring)

Drop the explicit reply_to_email field and always use the organizer's LNbits account email for Reply-To and copies. Cases that would lose: a shared team inbox that differs from the account email; accounts created with placeholder emails (demo @demo.local); Nostr-login accounts with no email (→ no Reply-To / no copy — UI should say so). Decide before reviving.

Notes

Feature PRs no longer bump config.json; the version is set by a release commit on main after merge.
Related deliverability context: #42, #43, aiolabs/lnbits#71.

Deferred on 2026-09-13 to keep the production run simple; the work exists on branches and can be revived. ## What was built (branches kept on origin) - `feat/organizer-sender-identity` (was #44): `extra.organizer_name` → From display name `"Organizer via <site title>"` (address stays the instance mailbox, DKIM untouched); `extra.reply_to_email` → `Reply-To`, falling back to the email on the LNbits account that owns the event wallet; body gains "Organizer: <name>" and "Questions? Reply to this email…" when a reply-to exists. 41 tests. - `feat/ticket-email-sent-copy` (was #47): `extra.copy_to_organizer` → envelope-only BCC of every ticket email to that reply-to (no header, skipped when the buyer is that address). The "Email sent" column from the same branch shipped separately. - Webapp counterpart: aiolabs/webapp `feat/events-organizer-sender` (was #148): the three fields in the event editor. ## Open design question (user's preference when deferring) Drop the explicit `reply_to_email` field and **always use the organizer's LNbits account email** for Reply-To and copies. Cases that would lose: a shared team inbox that differs from the account email; accounts created with placeholder emails (demo `@demo.local`); Nostr-login accounts with no email (→ no Reply-To / no copy — UI should say so). Decide before reviving. ## Notes - Feature PRs no longer bump `config.json`; the version is set by a release commit on `main` after merge. - Related deliverability context: #42, #43, aiolabs/lnbits#71.

padreug changed title from ~~Per-event sender identity for ticket emails (organizer name, reply-to, copy to organizer) — deferred</title>~~ to Per-event sender identity for ticket emails (organizer name, reply-to, copy to organizer) — deferred

2026-09-13 16:40:53 +00:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

aiolabs/events#49

No description provided.

Rows
Columns