harbor: Unable to send emails using Office 356 smtp server

Expected behavior and actual behavior: Unable to send emails using Office 356 smtp server with STARTTLS encryption.

Steps to reproduce the problem:

  • Email Server: smtp.office365.com
  • Email Server Port: 587
  • Email Username: username
  • Email Password: password
  • Email From: admin <noreply@domain.com>
  • Email SSL: True
  • Verify Certificate: True

Reference: https://support.microsoft.com/en-us/office/pop-imap-and-stmp-settings-8361e398-8af4-4e97-b147-6c6c4ac95353

Versions:

  • harbor version: v2.2.0-ec0ba116
  • docker engine version: -
  • docker-compose version: -

Additional context:

  • Log Files
2021-03-19T21:19:19Z [ERROR] [/core/api/email.go:113]: failed to ping email server: tls: first record does not look like a TLS handshake
2021-03-19T21:19:21Z [ERROR] [/core/api/email.go:113]: failed to ping email server: tls: first record does not look like a TLS handshake
2021-03-19T21:22:34Z [ERROR] [/core/api/email.go:113]: failed to ping email server: tls: first record does not look like a TLS handshake

#5757

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 23 (2 by maintainers)

Commits related to this issue

Most upvoted comments

would also love an update if there is anybody currently working on this.

I think this issue is really important because many companies use Exchange.

Issue is not stale.

/no-stale

Hi. You can repoduce it as well, setting Port 25 and check/uncheck Email SSL. If you disable it will Try TLS but cor.log throws: core[684]: 2021-04-20T11:47:44Z [ERROR] [/core/api/email.go:113]: failed to ping email server: 535 5.7.8 Error: authentication failed: no mechanism available

if you enable ssl on Port 25 it throws known reported error…

This issue needs attention as it makes it impossible to use any exchange smtp… and I don’t want to workaround lokal smtp-relays everywhere.

This issue is not stale. We just don’t have more to say. What do you need to fix that? 😅