Bounces from Automated Sender Addresses
Detects non-delivery reports received by a "no-reply" address and flags them to the right teams in Google Chat.
Description
Automated sender addresses ("no-reply", service accounts) receive the non-delivery reports of everything they send, and nobody reads them. This spreadsheet-bound script reads them for you every hour.
- Each bounce analysed: failed address, failure category, status code, cleaned server message and original subject. The original message body is never read.
- Rule-based routing: a spreadsheet tab maps each team to its Google Chat space, which receives a summary linking to the details.
- Recurring bounces grouped: an interface that keeps writing to a dead address produces a first report, then a simple daily reminder while the series continues.
- No external infrastructure: everything runs inside Google Workspace. The only possible write to the mailbox is moving processed bounces to the trash, and only if enabled.
Use Cases & Features
Find out that an application is writing to a non-existent address, instead of letting bounces pile up in a mailbox nobody reads.
Infos dépôt
- Licence MIT
- Plateforme GitLab
- Auteur Fabrice Faucheux