Magento2: Send friend sender email should be static not user defined

[juhanihaapala]

Preconditions (*)

1. Magento 2.3.2 with send friend email enabled

Steps to reproduce (*)

1. On product page select email friend
2. Fill the form

Expected result (*)

1. Email is sent from the email configured as sender in configuration

Actual result (*)

1. Email is sent from the email filled in form it won't work because server is not qualified sender and gmail for example set the email in spam with this huge warning
   

Proposed solution (*)

It makes more sense to put the email address from the Sender email form field in the Reply-To header instead of the From header. The From header should be one of the addresses configured in Magento's configuration under General > Store Email Addresses.

[m2-assistant[bot]]

Hi @juhanihaapala. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@juhanihaapala do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [ ] 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 6. Add label Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @engcom-Bravo, here is your Magento instance.
Admin access: https://i-23646-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[engcom-Bravo]

Hello @juhanihaapala. Thank you for your request. I'm not able to reproduce issue by steps you described on clean 2.3-develop

.

[juhanihaapala]

@engcom-Bravo I was abel to confirm it in that instance. The email never came to my gmail box even not in spam. But yes it will happily send it but it's for sure marked as spam because the sender is not qualified sender.

[juhanihaapala]

Oh, and I was using the form as guest. So enabled guest sending first on settings.

[engcom-Bravo]

On your hosting is configured mail server? If your sending email in spam Gmail maybe determines it as spam.

[juhanihaapala]

Of course. And to clarify the issue: the email shouldn't be sent as the email user has defined email address.

1. When settings are like this:
   

2. Then in send friend form user can select where is it send from:
   

3. And it will be sent with that email to the friend:
   

And because of that gmail, outlook or any decent email provider will flag it as spam.

[engcom-Bravo]

It is Thunderbird Mozilla. It is blocks your email. Change your settings and everything will be good.
https://support.mozilla.org/en-US/kb/how-change-thunderbird-layout

[hostep]

@engcom-Bravo: I'm able to reproduce on vanilla 2.3.2

It makes more sense to put the email address from the Sender email form field in the Reply-To header instead of the From header. The From header should be one of the addresses configured in Magento's configuration under General > Store Email Addresses.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-18139 were created

Issue Available: @engcom-Bravo, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[engcom-Bravo]

@hostep @juhanihaapala , thanks for the communication!

[amelaraby]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @araby93. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @araby93, here is your Magento instance.
Admin access: https://i-23646-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[m2-assistant[bot]]

Hi @edenduong. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [x] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [x] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [x] 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

Hi @juhanihaapala. Thank you for your report.
The issue has been fixed in magento/magento2#23684 by @edenduong in 2.3-develop branch
Related commit(s):

• 2048b40ce5dd3ea7c6344cb0a33dca6cc10954d9
• 6ae022367e1dd3a6e40d6b9d602f525f2bae900e

The fix will be available with the upcoming 2.3.4 release.