Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C CiviCRM Core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,372
    • Issues 1,372
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • CiviCRM Core
  • Issues
  • #2800
Closed
Open
Created Aug 30, 2021 by justinfreeman (Agileware)@justinfreeman🌟Developer

Scheduled Job, fetch_bounces with is_create_activities=1 parameter creates a new Contact using the Return-path email address which is incorrect

Scheduled Job, fetch_bounces with is_create_activities=1 parameter creates a new Contact ("Return-path" Contact) using the Return-path email address which is incorrect. An Inbound Email Activity is then created and associated with this new Contact.

The expected behaviour is that CiviCRM looks up the emailed Contact using the Return-path address and then creates the Inbound Email Activity for that Contact. No new contact is required.

The impact of problem is that:

  1. a lot of "Return-path" Contacts are created which confuses CiviCRM users, "who are these contacts? how did they get here? have we been hacked?"
  2. a CiviCRM admin needs to manually read each Inbound Email Activity to figure out what contact it actually relates too
  3. the "Return-path" Contacts need to be deleted as they serve no real purpose
  4. this is a performance hit when sending out large mailings, as CiviCRM is also creating Contacts and Activities as bounce emails are processed.

It does appear that the emailed Contact is being correctly detected as bounced, as it appears in the bounced contacts report for the Mailing.

Possibly related to this documentation issue, documentation/docs/sysadmin#217

Agileware Ref: CIVICRM-1778

CiviCRM 5.40.1

Edited Aug 31, 2021 by justinfreeman (Agileware)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking