We should get civi to handle its own bounces
Our torproject.org newsletter goes out from the address info@torproject.org which doesn't really exists. This means that when an address bounces we don't get to know that it has in fact bounced. This unless CiviCRM has a way to handle bounces? How do we know is the address we send emails via Civi are still valid? Update: we seem to agree we need Civi to handle bounces. Those are the next steps: 1. [x] get approval from @isa to fund GiantRabbit to work on this - approved informally by email 2. [x] figure out the best way to implement this (forward email? forward email + dovecot on the crm server?) - @giantrabbit - they want an IMAP mailbox somewhere 3. [x] @tpo/tpa configure an IMAP server on crm-int-01.torproject.org 4. [x] @giantrabbit make CiviCRM talk to the IMAP server 5. [x] one of those: * forward info@torproject.org to civicrm@crm.torproject.org or giving@torproject.org * make outgoing email come from civicrm@crm.torproject.org or giving@torproject.org <- this was done. 6. [x] monitor the mailing * [Grafana dashboard watching the two main mailservers](https://grafana.torproject.org/d/Ds5BxBYGk/postfix-mtail?orgId=1&from=now-24h&to=now&var-node=eugeni.torproject.org&var-node=crm-int-01.torproject.org) * [Place to enable/disable mailing](https://crm.torproject.org/civicrm/admin/job?reset=1&action=browse) (grep for `Send sched`...) * [Where the batches are defined](https://crm.torproject.org/civicrm/admin/mail?reset=1) * [Progress report](https://crm.torproject.org/civicrm/mailing/report?mid=790&reset=1) as of 2021-02-04 16:43UTC, before bumping to 500/batch * Success: 72632 (25.59%) * Bounces: 3867 (1.36%) * Unsubscribed: 46 (0.02%) * Opt-out: 29 (0.01%) * Final report: * Success: 269303 (94.88%) * Bounces: 14515 (5.11%) * Unsubscribed: 250 (0.09%) * Opt-out: 203 (0.07%)
issue