Bug 1996080

Summary:	Sendmail 8.17.1 for Fedora 35
Product:	[Fedora] Fedora	Reporter:	Morten Stevens <mstevens>
Component:	sendmail	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	35	CC:	anon.amish, jskarvad, olysonek-foss, redhat-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sendmail-8.17.1-1.fc35	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-24 20:07:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Morten Stevens 2021-08-20 13:25:41 UTC

Description of problem:

Sendmail 8.17.1 has been released some days ago and provides some interesting new features like experimental support for SMTPUTF8 and SMTP MTA Strict Transport Security. See: https://ftp.sendmail.org/RELEASE_NOTES

It would be great to get this ready for the upcoming Fedora 35 release.

Comment 1 Fedora Update System 2021-08-24 23:03:18 UTC

FEDORA-2021-74629d58f3 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-74629d58f3

Comment 2 Fedora Update System 2021-08-25 18:36:37 UTC

FEDORA-2021-74629d58f3 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-74629d58f3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-74629d58f3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2021-09-24 20:07:46 UTC

FEDORA-2021-74629d58f3 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.