[MGNLMAIL-106] Add field *return-path* in the mail module Created: 05/Feb/20 Updated: 25/Mar/22 |
|
| Status: | Open |
| Project: | Magnolia Mail Module |
| Component/s: | None |
| Affects Version/s: | 5.5.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Tatjana Poscharizki | Assignee: | David Lopez |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | accepted | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| 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 |
|
Hi, at the moment there is no *return-path* field in the mail module. Our customer SwissRe may most likely have it (depends on estimates as well). Please see the linked ticket. Could you please provide an estimate, for developing it in mail module within Core? Return path |
| Comments |
| Comment by David Lopez [ 06/Feb/20 ] |
|
Hi viet.nguyen, The idea is that since this will not be tackled in the near feature (Not before Q1 due to 6.2), so depending on customer urgency, it will be need to be done with project team and once available as global feature it can be replaced. The request is accepted but not prioritized in the backlog |