Handle undeliverable message

[tillprochaska]

Right now, we do not properly handle delivery issues in a consistent way across the supported communication channels, relying on Sentry notifications to identify issues like incorrect Threema IDs, unsubscribed users, blocked Telegram bots.

We should implement a generic solution that marks messages as undelivered in case any unexpected exceptions occur during sending. Additionally, we might want to automatically set contributors to inactive for certain types of errors (e.g. undeliverable messages due to unsubscribes, blocked bots, …).

For now, we could continue using Sentry to get notified about delivery issues, but I think we should set up a separate channel next to the generic monitoring channel for such issues, to make it easier for our support to take action. In the future, we could leverage a notification feature (#1287) to display notifications in 100eyes, so editors are informed about unsubscribes, delivery issues etc.

Related:

• Postmark offers a bounce webhook that we could use to be notified about email delivery issues: https://postmarkapp.com/developer/webhooks/bounce-webhook.
• We already do something similar for Telegram messages: https://github.com/tactilenews/100eyes/blob/master/app/adapters/telegram_adapter/outbound.rb#L6

[mattwr18]

Just seeing this issue now @tillprochaska ... Really cool that we were both thinking very similar things. We have already started working on this.

See

• Rescue Postmark::InactiveRecipientError and tag with support #1447
• Rescue RuntimeError and mark as support conditionally #1509
• Mark inactive contributors as inactive #1603