Bug 1872358 - openssl error when sending email through a smtp server that does not use ssl
Summary: openssl error when sending email through a smtp server that does not use ssl
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.11.7
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.11.9
Assignee: Tina Fitzgerald
QA Contact: Tasos Papaioannou
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-25 14:38 UTC by Felix Dewaleyne
Modified: 2023-12-15 19:00 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-08 18:39:48 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:
fdewaley: needinfo-
fdewaley: needinfo-


Attachments (Terms of Use)
email_test.rb (121 bytes, application/x-ruby)
2020-09-04 15:58 UTC, Tina Fitzgerald
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5387591 0 None None None 2020-09-10 09:04:06 UTC

Description Felix Dewaleyne 2020-08-25 14:38:45 UTC
Description of problem:
When sending an email using a test button or automation, an ssl error is raised. The smtp service doesn't use ssl.

Version-Release number of selected component (if applicable):
5.11.7

How reproducible:
customer environment

Steps to Reproduce:
1. set up email to a smtp on port 25 with no ssl or tls
2. attempt to send an email
3.

Actual results:
error raised : automation_notification delivery-error: SSL_connect returned=1 errno=0 state=error: unsupported protocol attempting to resend


Expected results:
email is sent 

Additional info:
this problem was not observed on 4.7

Comment 7 William Fitzgerald 2020-08-26 20:58:54 UTC
Felix,

Sorry, I meant ask the customer to set tls (the enable_starttls_auto) setting to false.

Thanks

Billy

Comment 10 Felix Dewaleyne 2020-08-27 10:18:36 UTC
confirmed : the customer's using the same smtp with 4.7 with no issues.

Comment 19 Joe Rafaniello 2020-08-28 16:07:16 UTC
I diff'd the rpms and Gemfile.lock, limited it to just things "I think are relevant" and grouped related changes from their 5.10.14.0 to 5.11.7.3 setups:

$ git diff --minimal | grep -E "\b(cfme|mail|ruby|actionmailer|rails|openssl|smtp|postfix)\b"

-cfme-5.10.14.0-1.el7cf.x86_64
-cfme-appliance-5.10.14.0-2.el7cf.x86_64
-cfme-appliance-common-5.10.14.0-2.el7cf.x86_64
-cfme-appliance-tools-5.10.14.0-2.el7cf.x86_64
-cfme-gemset-5.10.14.0-1.el7cf.x86_64
+cfme-5.11.7.3-1.el8cf.x86_64
+cfme-appliance-5.11.7.3-1.el8cf.x86_64
+cfme-appliance-common-5.11.7.3-1.el8cf.x86_64
+cfme-appliance-tools-5.11.7.3-1.el8cf.x86_64
+cfme-gemset-5.11.7.3-1.el8cf.x86_64

-openssl-1.0.2k-19.el7.x86_64
-openssl-libs-1.0.2k-19.el7.x86_64
+openssl-1.1.1c-15.el8.x86_64
+openssl-libs-1.1.1c-15.el8.x86_64
+openssl-pkcs11-0.4.10-2.el8.x86_64

-postfix-2.10.1-7.el7.x86_64
+postfix-3.3.1-12.el8.x86_64

-rh-ruby23-ruby-2.3.8-70.el7.x86_64
-rh-ruby23-ruby-irb-2.3.8-70.el7.noarch
-rh-ruby23-ruby-libs-2.3.8-70.el7.x86_64

-ruby-2.4.9-93.el7cf.x86_64
-rubygem-openssl-2.0.9-93.el7cf.x86_64
-ruby-irb-2.4.9-93.el7cf.noarch
-ruby-libs-2.4.9-93.el7cf.x86_64
+ruby-2.5.5-105.module+el8.1.0+3656+f80bfa1d.x86_64
+rubygem-openssl-2.1.2-105.module+el8.1.0+3656+f80bfa1d.x86_64
+ruby-irb-2.5.5-105.module+el8.1.0+3656+f80bfa1d.noarch
+ruby-libs-2.5.5-105.module+el8.1.0+3656+f80bfa1d.x86_64

-xmlsec1-openssl-1.2.20-7.el7_4.x86_64
+xmlsec1-openssl-1.2.25-4.el8.x86_64

-    actionmailer (5.0.7.2)
+    actionmailer (5.1.7)

-    rails (5.0.7.2)
+    rails (5.1.7)

Comment 21 Joe Rafaniello 2020-08-28 16:11:34 UTC
Note, rhel changed from 7.7 to 8.2 so any docs that show changes to OS defaults for SSL or smtp could be in play too
-redhat-release-server-7.7-10.el7.x86_64
+redhat-release-8.2-1.0.el8.x86_64
+redhat-release-eula-8.2-1.0.el8.x86_64

Comment 36 Tina Fitzgerald 2020-09-04 15:58:57 UTC
Created attachment 1713799 [details]
email_test.rb

Comment 48 Tina Fitzgerald 2020-09-09 20:04:33 UTC
Hi Felix,

Could you replace Step 2 above with this?

2. Once the test email has failed, would you reach out to your mail server sysadmin for information logged by the server for the failed request, e.g. request data specifics, any server logged info on the rejection, etc.

Thanks,
Tina

Comment 61 Daniel Berger 2020-09-17 18:27:23 UTC
@mheppler, Can you enable port 587 as well on that host please? I want to see if enable_starttls_auto + port 587 will work.

Comment 62 mheppler 2020-09-18 08:20:12 UTC
@Daniel, done, and removed auth, so you can really send e-mail to cf@bug1872358.

Comment 66 mheppler 2020-09-22 07:55:26 UTC
465 port is opened and working...

Comment 72 dmetzger 2020-10-08 18:39:48 UTC
Given the instructions regarding setting the desired security level (in comment #70) have shown to allow email at the customer site and the associated BZ (https://bugzilla.redhat.com/show_bug.cgi?id=1881201) to ensure TLS is only started is SSL is specified, this BZ its being closed.

Comment 73 Red Hat Bugzilla 2023-09-14 06:07:46 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.