Project

General

Profile

Actions

Feature #7444

closed

Add support for login and encryption to the email client

Added by Henri Hyyryläinen over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Start date:
02/06/2020
Due date:
% Done:

0%

Estimated time:

Description

Hi,

I hope this is the right place to ask about this. Sorry if this is a duplicate, I tried searching for issues with "email" in them but did not find one that asks for the same thing as this.

It seems that Wt email component doesn't work the way I'd optimally want it to work for production.

I would like to use SMTP over SSL or with TLS as well as with a username and password for sending emails.

I looked through the Wt code and it seems like login with SMTP is not supported, and the documentation said that the encryption options are not supported.

So I would like to ask that, at some point the Wt email component could be updated to support these features.

Actions #1

Updated by Roel Standaert over 4 years ago

This is definitely the right place to ask. I know that Wim at some point made an implementation, or at least part of an implementation, that never ended up being included. I can't guarantee that this feature will get in, though.

Our typical deployment scenario involves an SMTP server running on localhost that then relays emails through some other SMTP server, possibly using TLS. The Wt::Mail implementation was also kept very simple and is blocking, the idea being that it is usually handed to a local SMTP server that then makes sure it is properly transmitted (possibly reattempting transmission if necessary, etc.).

Actions #2

Updated by Henri Hyyryläinen over 4 years ago

Roel Standaert wrote:

This is definitely the right place to ask. I know that Wim at some point made an implementation, or at least part of an implementation, that never ended up being included. I can't guarantee that this feature will get in, though.

Our typical deployment scenario involves an SMTP server running on localhost that then relays emails through some other SMTP server, possibly using TLS. The Wt::Mail implementation was also kept very simple and is blocking, the idea being that it is usually handed to a local SMTP server that then makes sure it is properly transmitted (possibly reattempting transmission if necessary, etc.).

I also have a local SMTP server, but I would like to run Wt in docker meaning that I would need to do some special setup with the current email client. I have other stuff running in docker that connects to the host's SMTP server with the host's public domain name and authenticates with an username and password, for simplicity's sake.

Actions #3

Updated by Roel Standaert over 4 years ago

I would like to run Wt in docker

I was wondering about that as I was typing up the response. I don't know what the best way to do it with Docker would be either.

Actions #4

Updated by Wim Dumon over 4 years ago

My work only added TLS, no authentication. Although I think that after implementing TLS, adding username&password auth is not too much work. The thing is that many authentication mechanisms are supported, I was unsure how to design the API. I forwarded my experimental code to Roel so he can consider to include it in Wt.

BR,

Wim.

Actions #5

Updated by Roel Standaert over 4 years ago

  • Status changed from New to Resolved

I just pushed a commit to master that should make this work. I still have to decide on what the final API for it should be before the Wt 4.3.0 release, but all of the functionality should be there.

Supported:

  • Immediately using TLS (no STARTTLS)

  • STARTTLS

  • Authentication using the PLAIN and LOGIN methods

Actions #6

Updated by Roel Standaert over 4 years ago

  • Target version set to 4.3.0
Actions #7

Updated by Roel Standaert about 4 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF