# Summary

This module allows Drupal to bypass the PHP mail() function and send email directly to an SMTP server. The module supports SMTP authentication and can even connect to servers using SSL if supported by PHP.

# Project URL

https://www.drupal.org/project/smtp

# Where is the code?

#1949430: Drupal 8 version of the SMTP module?

# Estimated completion date

Unknown

# Dependencies

Unknown

# Who's doing the port?

bradjones1

# What help do they need?

#2651976: Enabling module does not set itself as default mail system
#2622678: Cannot send email without a "reply-to" set, maybe missing mail system setting.
#2627432: Clean up name and email address handling

# D8 roadmap

Unknown

# Background and reference information

#1949430: Drupal 8 version of the SMTP module?

Comments

legaudinier created an issue. See original summary.

Kristen Pol’s picture

Issue summary: View changes
Kristen Pol’s picture

Issue summary: View changes
ptmkenny’s picture

Issue summary: View changes
geidin’s picture

When I turn to configuration-SMTP, it appears with the following words:Disabled fields are overridden in site-specific configuration file
How can I fix this in drupal-8.1.6

lshao999’s picture

geidin,

Have you fixed the issue. It appears that SMTP works fine with drupal-8.1.3. But after updating to 8.1.8, I can no longer config two fields (port and SSL). See the same message: Disabled fields are overridden in site-specific configuration file.
Thanks

timKruijsen’s picture

Just had an issue where an exception wasn't shown correctly ('!from' wasn't replaced with the actual email address).
On line 720 in PHPMailer.php I changed:
throw new phpmailerException(t('The following From address failed: !from', array('!from' => $smtp_from)), self::STOP_CRITICAL);
To:
throw new phpmailerException(t('The following From address failed: @from', array('@from' => $smtp_from)), self::STOP_CRITICAL);

Now it does show the exception correctly.
Don't know if this was a known issue, but I couldn't find it just now.

rodrigoaguilera’s picture

Is there a list of issues or plan to get this module out of beta?

estoyausente’s picture

What can we do to release an stable version? Anny plan or something? thanks!

ramonma1989’s picture

Category: Plan » Support request

This module is used by a lot of people, it needs to be in a stable version for d8. How can we help?

mmjvb’s picture

Category: Support request » Plan

You can help by not changing the category of this issue. Suggest to use the issue queue of the project you want tp provide help on.
To help with this issue you can monitor that project and bring back the information requested in this issue.

koryp’s picture

Forgive me - I don't do much Drupal development, so maybe these questions are answered in the community guidelines or something...

By "information requested in this issue" do you mean the "D8 roadmap", "Estimated completion date", "Dependencies", "What help do they need?", etc.? Those look like a bunch of "unknowns" and I'm not sure what to "monitor" on the project page to get those answers - is it just a matter of someone needing to grab the bull by the horns?

The (currently) three listed tickets in the help-needed section are all closed ... I'd update those with current critical issues from the project's issue queue, but it appears the the queue is not being maintained ... It has critical feature requests and there's not even a stable 8.x version released yet.

https://www.drupal.org/project/issues/smtp?text=&status=Open&priorities=...

... looks like the issue about the phpmailer version might be a valid critical issue, but the description links to a (seemingly duplicate) normal-priority issue that has a comment saying D8 uses a stripped-down version that doesn't suffer from the security vulnerabilities... so maybe not a critical issue after all.

Anyway, who determines which issues are showstoppers before this module can get a stable release and get covered by the security advisory policy? Is it "bradjones1" or is "Chuva Inc." (listed as the maintainer on the project page) calling the shots?

Thanks.

mmjvb’s picture

Check out the description of this project (D8CPT). Yes, it is that kind of information to be collected from the project smtp and mentioned here. It would provide the information in a convenient format and save others to hunt it down in the projects itself.

This issue has Status: Needs review, which means there is an alpha or beta release. Upon release of Stable it would be set to Fixed. The issues mentioned in the help needed section are done. That section should mention what kind of help is needed to get it to Stable. It is not meant to be a list of tickets, it should say what kind of help the people working on the port need. It appears the work was abandoned. Unless you are going to work on the port it sounds useless to update it with other issues.

The person doing the port would not have anything to say about releases. Normally that would be the owner or co-maintainer. It is the owner that opts into security coverage. The project smtp opted in, upon release of Stable it will get the shield, just as the D7 version.

No idea how to identify the owner. Normally, the author of the project page or the person with the most commits lead to the owner. Guess wundo is the owner.

marafee1243’s picture

Issue summary: View changes

How to set STMP configurations in settings.php (Drupal 8) ?

mmjvb’s picture

@marafee1243 Please refrain from hijacking this issue. For support request use the issue queue of SMTP Authentication Support itself, not this issue in D8CPT. Reverted!

mmjvb’s picture

Status: Needs review » Fixed
apaderno’s picture

apaderno’s picture

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.