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,374
    • Issues 1,374
    • 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
  • #645

Closed
Open
Created Jan 07, 2019 by nishantB@nishantB

Use site email domain in place of bounce email domain for automated messages

Hello there!!

We encountered a scenario where we can whitelist only one email domain to send emails. We want to use email domain (eg: bouncedomain.com) for bounce processing and a different one (sitedomain.com) for rest of the emails which works fine except that do-not-reply emails use the email domain set for bounce processing (bouncedomain.com) because of which AWS SES prevent those emails to be sent.

Current behaviour:

  1. Regular emails: example@sitedomain.com
  2. Bounce emails: bounce@bouncedomain.com
  3. Do-not-reply emails: do-not-reply@bouncedomain.com

Expected behaviour:

  1. Regular emails: example@sitedomain.com
  2. Bounce emails: bounce@bouncedomain.com
  3. Do-not-reply emails: do-not-reply@sitedomain.com

Is there already a configuration to set that or would it be a good idea to add a field where we can set the email domain for do-not-reply emails ?

Thanks!

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