New Order not sending if a comma is followed by a blank space in the 'Send Order Email Copy To' field

[jaxtheking]

Preconditions (*)

Magento 2.3.3
php7.1

Steps to reproduce (*)

1. In the BO, go to Stores >> Configuration >> Sales >> Sales Emails
2. Under Orders, in the 'Send Order Email Copy To' field, enter a list of emails in the following format: 'admin1@email.com, admin2@email.com' (note the blank space after the comma)

Expected result (*)

1. The New Order email should be sent to the customer and the two admins

Actual result (*)

1. No emails are sent out (not even the customer!), due to the following error:

main.ERROR: ' admin2' can not be matched against dot-atom format [] []

Obviously, Magento is not expecting a blank space before the email address: while not technically a bug, this could be easily avoided by trimming each email address after exploding the comma-separated string.

More importantly, this behaviour means that if an admin were to enter a list of emails containing one invalid email (e.g. correct@email.com,incorrect.com), the customer would not be receiving a new order email at all!
I think the error should be limited to the invalid email only.
I'm guessing this behaviour applies to all 'Send XXX Email Copy To' fields in the BO.

Regards,
Luca

[m2-assistant]

Hi @sudheers-kensium. 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: 👇

• 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. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[sakbari]

Centos 7
Magento CLI 2.3.3
PHP 7.2.23
nginx version: nginx/1.16.1
redis-cli 5.0.5

I have same issue we did not get a copy of order mail

[edenduong]

I am working to fix this issue

[m2-assistant]

Hi @edenduong. 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: 👇

• 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!

---

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

[magento-engcom-team]

✅ Confirmed by @sudheers-kensium
Thank you for verifying the issue. Based on the provided information internal tickets MC-21863 were created

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