Scheduled Job, fetch_bounces with is_create_activities=1 parameter. CiviCRM does not unsubscribe a Contact when receiving an email to the verb unsubscribe email address
Scheduled Job, fetch_bounces with is_create_activities=1 parameter. CiviCRM does not unsubscribe a Contact when receiving an email to the verb unsubscribe email address. As a result, Contacts are not being unsubscribed when this request is received via email. This contravenes Australian Anti-Spam Law (Spam ACT 2003).
The current behaviour is that the Scheduled Job, fetch_bounces with is_create_activities=1 parameter creates a new Contact ("Unsubscribe" Contact) using the verb unsubscribe email address which is incorrect. An Inbound Email Activity is then created and associated with this new Contact. The Activity is created and assigned to the emailed Contact that should be unsubscribed.
The emailed Contact is not unsubscribed from the mailing list and no unsubscribe event is recorded. So further emails will be sent to this Contact, despite their explicit unsubscribe request.
The expected behaviour is that:
- CiviCRM looks up the emailed Contact using the unsubscribe email address and then creates the Inbound Email Activity for that Contact. No new contact is required.
- The Contact that should be unsubscribed from the mailing list.
Related #2800 (closed)
Agileware Ref: CIVICRM-1826
CiviCRM 5.40.1