[MGNLFORM-56] Support CC and BCC addresses in the SendContactEMailProcessor Created: 05/Aug/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Form Module
Component/s: mail
Affects Version/s: 1.1.1
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Will Scheidegger Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: bcc, cc, form
Remaining Estimate: 0.25h
Time Spent: Not Specified
Original Estimate: 0.25h

Attachments: Text File cc_bcc.patch    
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

With a few lines of code one could support CC and BCC fields in the SendContactEMailProcessor. This might be useful when contact mails should be stored in a second account for statistics or backup reasons etc.

The attached patch enables CC and BCC fields named "contactMailCc" and "contactMailBcc". It also includes proposals for labels and descriptions:

dialog.form.tabContactEmail.contactMailCc.label = CC
dialog.form.tabContactEmail.contactMailCc.description = Copy of the mail will be sent to these addresses which will be visible to the other recipients. You can use form field names with freemarker tags i.e. ${mail}
dialog.form.tabContactEmail.contactMailBcc.label = BCC
dialog.form.tabContactEmail.contactMailBcc.description = A copy of the mail will be sent to these addresses which will not be visible to the other recipients. You can use form field names with freemarker tags i.e. ${mail}

However the form dialog itself has not been altered, this with the intention that each integrator can decide himself/herself if the cc and/or bcc field should be shown in the dialog.

NOTE: The patch applies to version 1.1.1 code, hoping that it will still be applicable to the latest version.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 05:36:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.