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

Custom SMTP #26104

Closed
Zyles opened this issue Dec 18, 2019 · 3 comments · Fixed by #32241
Closed

Custom SMTP #26104

Zyles opened this issue Dec 18, 2019 · 3 comments · Fixed by #32241
Assignees
Labels
Area: Framework feature request improvement Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: ready for confirmation 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

@Zyles
Copy link

Zyles commented Dec 18, 2019

Description (*)

Add custom SMTP option in core.

It is RIDICULOUS that we can't configure an external e-mail service provider in 2020.

Instead I have to resort to installing some custom SMTP extension that breaks on updates and no longer maintained, and our customers can't get any order e-mails.

So we have to ask ourselves:

  1. Do we update Magento because of this latest security issue, and stop sending order and shipping confirmations to our customers?
    or
  2. Do we live with the security issue and hope nobody hacks us, but have the ability to send order e-mails to your customers?

Expected behavior (*)

Have the ability to customize a custom external SMTP provider.

Benefits

  1. A working store.
  2. Ability to send order information and other store e-mails to customers
  3. Ability to update to latest security releases without having to remove mission critical functionality of an ecommerce store in 2020
  4. Not having to configure a MTA on every single web server in the cluster
@m2-assistant
Copy link

m2-assistant bot commented Dec 18, 2019

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

@Zyles 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 not valid Gate 1 Failed. Automatic verification of issue format is failed label Dec 18, 2019
@korostii korostii added feature request improvement Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed and removed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Dec 24, 2019
@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Dec 24, 2019
@magento-engcom-team magento-engcom-team added this to Ready for QA in Community Backlog Mar 24, 2020
@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 24, 2020
@sidolov sidolov added this to Ready for Confirmation in Issue Confirmation and Triage Board Oct 21, 2020
@ghost ghost removed this from Ready for QA in Community Backlog Oct 21, 2020
@ghost ghost removed this from Ready for Grooming in Low Priority Backlog Oct 21, 2020
@ghost ghost added Issue: ready for confirmation and removed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Oct 21, 2020
@sivaschenko sivaschenko added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Nov 6, 2020
@m2-community-project m2-community-project bot added this to Ready for Grooming in Feature Requests Backlog Nov 6, 2020
@m2-community-project m2-community-project bot removed this from Ready for Confirmation in Issue Confirmation and Triage Board Nov 6, 2020
@m2-community-project m2-community-project bot moved this from Ready for Grooming to Pull Request in Progress in Feature Requests Backlog Feb 22, 2021
@engcom-Alfa engcom-Alfa added Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jun 28, 2022
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.magento.com/browse/AC-3758 is successfully created for this GitHub issue.

@m2-assistant
Copy link

m2-assistant bot commented Jun 28, 2022

✅ Confirmed by @engcom-Alfa. Thank you for verifying the issue.
Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Framework feature request improvement Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: ready for confirmation 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
Development

Successfully merging a pull request may close this issue.

8 participants