The email fallback for groups without Discord reaches nobody #840

New issue

Closed

opened 2026-09-26 14:33:40 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-09-26 14:33:40 +00:00

Collaborator

Found by the lane 10 survey (#736).

send_confirmation and send_reminder take no recipient, so they mail the server's own from-address (app/notifications/email.py:45-93, 236). J2 passes only because it checks the subject line.
Reminder emails go out only through a webhook (reminder_tasks.py:2085-2092), and D67 removes the instance webhook.
Email notifications default to off.

So a group that schedules by email hears nothing, which puts the brief's "schedule by email" promise at risk.

The owner's decision is pending (O6 on the morning list). The recommendation: for a campaign with no Discord channel, session news goes by email to every member with an address, unless they've turned Sessions email off. Reminders become notifications. It lands in lane 10's PR 2.

Refs #736.

Found by the lane 10 survey (#736). - `send_confirmation` and `send_reminder` take no recipient, so they mail the server's own from-address (`app/notifications/email.py:45-93, 236`). J2 passes only because it checks the subject line. - Reminder emails go out only through a webhook (`reminder_tasks.py:2085-2092`), and D67 removes the instance webhook. - Email notifications default to off. So a group that schedules by email hears nothing, which puts the brief's "schedule by email" promise at risk. **The owner's decision is pending** (O6 on the morning list). The recommendation: for a campaign with no Discord channel, session news goes by email to every member with an address, unless they've turned Sessions email off. Reminders become notifications. It lands in lane 10's PR 2. Refs #736.