Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • CiviCRM Core CiviCRM Core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
  • Issues 1,250
    • Issues 1,250
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • DevelopmentDevelopment
  • CiviCRM CoreCiviCRM Core
  • Issues
  • #1999
Closed
Open
Issue created Sep 04, 2020 by justinfreeman (Agileware)@justinfreeman🌟Developer

Contribution pages - When email addresses are defined for the Receipt, CC Receipt To / BCC Receipt To fields and emails to those recipients bounce then that bounce is counted against the Contribution Contact and not the actual bounced recipient

If you set the Receipt email addresses on a Contribution page and ANY of those email addresses bounce then that bounce is recorded against the CiviCRM Contact that the receipt was sent too. So if you have 3 or more CC/BCC email addresses defined and they ALL bounce. Then that CiviCRM Contact's email is immediately put ON HOLD.

This is because the receipt email has the bounce return path of the CiviCRM contact and a single email is sent with the CC/BCC defined.

A possible workaround would be to send individual emails for each of the email addresses defined in the CC Receipt To / BCC Receipt To fields.

A symptom of this problem occurring is that new members, event participants and donors have their email addresses immediately marked as on hold after contributing or registering for an event.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking