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 contact form not sending emails( No log entry) #23645

Closed
YiffyToys opened this issue Jul 10, 2019 · 24 comments · Fixed by #32730
Closed

Magento 2.3 contact form not sending emails( No log entry) #23645

YiffyToys opened this issue Jul 10, 2019 · 24 comments · Fixed by #32730
Assignees
Labels
CD Issue recommended for the contribution day Component: Mail Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.

Comments

@YiffyToys
Copy link

YiffyToys commented Jul 10, 2019

Preconditions

Magento 2.4-develop

Steps to reproduce (*)

Expected result (*)

  1. Exception with stack trace is logged

Actual result (*)

  1. No log entry in any of the Magento, PHP or Apache logs that provides any insight

Original case:
Preconditions
Magento 2.3.0, 2.3.1 or 2.3.2 CE

  1. sendmail is installed and working (Courier-MTA on Debian 10)
  2. php mail() command working fine
  3. order status emails are being send fine

Steps to reproduce (*)

  1. enter the contact form
  2. send a message

Expected result (*)

  1. email is sent

Actual result (*)
1**. as a user get a generic error message that email could not be sent**
2. No log entry in any of the Magento, PHP or Apache logs that provides any insight

Since order status emails can be sent, Magento is clearly capable of sending emails to users.
At the very least, there must be a log entry THAT something happend and best even provide inside what needs fixing. Currently there is no log entry at all. Not even on DEBUG level.

@m2-assistant
Copy link

m2-assistant bot commented Jul 10, 2019

Hi @YiffyToys. 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.

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

  • yes
  • no

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jul 10, 2019
@engcom-Charlie engcom-Charlie self-assigned this Jul 10, 2019
@m2-assistant
Copy link

m2-assistant bot commented Jul 10, 2019

Hi @engcom-Charlie. 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.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-Charlie
Copy link
Contributor

Hello @YiffyToys ! Please provide more information about this issue

@YiffyToys
Copy link
Author

@magento give me 2.3-develop instance
@engcom-Charlie How to reproduct that no information is logged if the contact form fails to send an email? How to check logs on the automatically created instances used to reproduce an issue? Can these instances actually send email?

@magento-engcom-team
Copy link
Contributor

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

@magento-engcom-team
Copy link
Contributor

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

@engcom-Charlie engcom-Charlie added Component: Mail good first issue Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Jul 10, 2019
@ghost ghost unassigned engcom-Charlie Jul 10, 2019
@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jul 10, 2019
@magento-engcom-team
Copy link
Contributor

✅ Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-18023 were created

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

@engcom-Charlie engcom-Charlie changed the title Magento 2.3 contact form not sending emails Magento 2.3 contact form not sending emails( No log entry) Jul 10, 2019
@NishaJangid NishaJangid self-assigned this Jul 11, 2019
@m2-assistant
Copy link

m2-assistant bot commented Jul 11, 2019

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

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

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

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


@ghost ghost unassigned NishaJangid Sep 27, 2019
@BrentRobert
Copy link
Contributor

@magento give me 2.3-develop instance

@magento-engcom-team
Copy link
Contributor

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

@magento-engcom-team
Copy link
Contributor

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

@YiffyToys
Copy link
Author

I can confirm that it is fixed in Magento CE 2.3.3

If you are reading this, please note that #24902 may have been added in the process.

@elvinristi
Copy link
Contributor

elvinristi commented Oct 14, 2019

FYI @YiffyToys - it's not fixed in M2.3.3, but in M2.3-dev. Hopefully will be included in next M2.3.4 release.

@YiffyToys
Copy link
Author

I reported this issue and after the update to 2.3.3-CE my contact form works again.

@BrentRobert
Copy link
Contributor

@YiffyToys This issue is still valid as it states that there is not always logging available. Your underlying issue might have been fixed meanwhile.

@mateuszrusiecki
Copy link

seriously it's not fixed yet!? why am I surprised...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CD Issue recommended for the contribution day Component: Mail Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.