Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

magento 2.3 when you click 'send email' you get a message 'You sent the order email.' #32148

Closed
f1-outsourcing opened this issue Feb 12, 2021 · 5 comments
Labels
Issue: ready for confirmation not-confirmed Use for Issue that was closed during confirmation

Comments

@f1-outsourcing
Copy link

When you click 'Send Email' on this page adminuo/sales/order/view/order_id/140/key/xxx/

This is an incorrect message. The message is not send, the sending is scheduled not?

@m2-assistant
Copy link

m2-assistant bot commented Feb 12, 2021

Hi @f1-outsourcing. 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.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this


⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@f1-outsourcing
Copy link
Author

this[1] works for me, and here[2] they write that magento 2.3 is still using the php mail function. So I do not know why these mails are not going out. I have even reverted back to original/default templates of magento, but still no luck.

Thus, I do not know how you can generate a message with a green check mark, when in fact the message is not send.

php -r "mail('test@example.com','theme','body');"

[1]
#20033 (comment)

[2]
#20033 (comment)

[3]
[2021-02-12 18:14:02] main.ERROR: Unable to send mail: Unknown error [] []
[2021-02-12 18:14:28] main.ERROR: Unable to send mail: Unknown error [] []

@engcom-Delta engcom-Delta self-assigned this Feb 15, 2021
@m2-assistant
Copy link

m2-assistant bot commented Feb 15, 2021

Hi @engcom-Delta. 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).

    DetailsIf 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.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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.

@engcom-Delta engcom-Delta added the not-confirmed Use for Issue that was closed during confirmation label Feb 15, 2021
@engcom-Delta
Copy link
Contributor

Hi @f1-outsourcing thank you for your report, I'm not able to reproduce issue by steps you described on clean 2.4-develop
Manual testing scenario:

  • Create simple product
  • Create custome
  • Place order as customer
  • Go to Sales->Orders
  • Click View link for order
  • Click Send Email

Result:
✔️ Success message "You sent the order email." is shown
image
✔️ Customer receive order confirmation email
image

Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines
if you are still facing this issue on the latest 2.4-develop branch.

@engcom-Delta engcom-Delta removed their assignment Feb 15, 2021
@f1-outsourcing
Copy link
Author

Hi @f1-outsourcing thank you for your report, I'm not able to reproduce issue by steps you described on clean 2.4-develop
Manual testing scenario:

* Create simple product

* Create custome

* Place order as customer

* Go to Sales->Orders

* Click View link for order

* Click **Send Email**

Result:
heavy_check_mark Success message "You sent the order email." is shown
image
heavy_check_mark Customer receive order confirmation email
image

Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines
if you are still facing this issue on the latest 2.4-develop branch.

Did you have this in your log file "main.ERROR: Unable to send mail: Unknown error "?

I guess not, thus you have tested totally different situation. And since I did not mention what I did to get this message, you can maybe conclude that I have no idea what config setting it could have been. That means you have to ask a developer under what circumstances this message is being generated, so you can apply these to your test.
Then I am confident that you will be able to reproduce it.

Besides you should never use 'sent' but 'scheduled', because it goes in your queue and if the cron does not run, the message is simply not sent. You can only use sent when the MTA reports back the message has correctly been received (obviously).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: ready for confirmation not-confirmed Use for Issue that was closed during confirmation
Projects
None yet
Development

No branches or pull requests

2 participants